We have moved to a new Sailfish OS Forum. Please start new discussions there.
84

[release notes] 2.1.4 / Lapuanjoki [released]

asked 2018-02-15 13:59:39 +0300

jovirkku gravatar image

updated 2018-06-05 15:50:44 +0300

Update version history

  • 2018-02-20: 2.1.4.13 was released to Early Access subscribers. Japanese and Korean removed from the list of new languages (not yet quite ready).
  • 2018-02-28: 2.1.4.14 was released to Early Access subscribers. BT audio issue on Jolla1 fixed.
  • 2018-03-06: 2.1.4.14 was released to all Jolla users (Jolla1, Jolla Tablet, Xperia X). Aqua Fish and Inoi R7 are pending customer acceptance.
  • 2018-03-13: 2.1.4.14 was released to all Aqua Fish and to all Jolla C users.

Size of update

The download size of the update depends on the device type and on the OS version currently in the device. Some typical values below:
- Jolla C from 2.1.3.7 to 2.1.4.13: 380 MB
- Jolla 1 from 2.1.3.7 to 2.1.4.13: 340 MB
- Xperia X from 2.1.3.7 to 2.1.4.13: 390 MB

Release Highlights

This list contains examples of new features (and some bug fixes) added to SailfishOS since the 2.1.3 release. The release notes of upgrade 2.1.3 can be found here: https://together.jolla.com/question/172002/release-notes-213-kymijoki/

Instructions for installing Sailfish OS to Sony Xperia X devices are here - covering Windows, Linux and Mac computers.

Accounts

  • CalDav syncing getting stuck fixed
  • CalDav reminders no longer trigger twice after sync
  • Dropbox account creation failure fixed (recent regression)
  • Active Sync settings UI polished
  • Weather service in Events View now tracks network connectivity status, and automatically refreshes when connectivity is regained.

Aliendalvik

  • Updated Android Support of Xperia X from version 1.0.79-1 to 1.0.85-1 (no update for Jolla devices), fixing:
  • Add support for camera HAL introduced in Android 7.
  • Prepare for notification improvements.
  • Update device configurations.
  • Improve camera startup speed on Android 7 based devices.
  • Solved an issue where certain apps (i.e. Wechat) were unable to record voice messages.

Bluetooth

  • SyncML support dropped.

Browser

  • Browser cover no longer flickers during device orientation change.

Camera

  • Camera app is launched if shutter key is long-pressed (does not work on lock screen yet)
  • Photo details fixed for Camera photos stored in SD card.

Connectivity

  • WLAN: support for IEEE802.11r enabled. This brings the Fast Transition feature. It is meant to allow faster handoffs for a mobile station between two or more Access Points, a sort of handover for WLAN.
  • Homescreen crash fixed that sometimes happened when connecting to WLAN.

Device management (MDM)

  • Activation displays a disclaimer to user
  • Date and time API extended to support all time zones.

Email

  • Fix a crash when an attachment is opened second time
  • Fix search losing focus after backstepping from Email viewer
  • Downloaded attachments can now be picked as attachments for new emails.

Facebook

HW adaptation

  • Xperia: support of BTRFS filesystem for SD cards added
  • Xperia: low memory killer enabled.

Keyboard

  • Hungarian and Slovenian layouts added.

Languages

  • New system languages: Chinese (Taiwan), Czech, Dutch, Estonian, Greek, Hungarian, Portuguese (Brazil), Slovenian, Spanish (Bolivia), Turkish.
    Many thanks to you our valued community people for the translations!

Media

  • Show the correct playback state when the playlist playback stops
  • Order music albums by date released, instead of alphabetically.

Messages

  • Send button in Messages app touch area enlarged for easier use.

Middleware

  • Qt framework updated 5.6.3, including hundreds of bug fixes
  • Tracker updated to the latest V1 version to possibly fix some metadata extraction failures.

Notes

  • Search is now supported.

Notifications

  • Notification banners can now be swiped away with horizontal flick.

OS updates

  • PackageKit framework upgraded to newer version
  • OS updates are now a privileged operation run as proper system-side service
  • OS update process rewritten to reduce dependencies and thus potential causes of failures
  • OS update descriptions now support links.

SDK

  • Enable (hint) showing apps in fullscreen on emulator
  • Resize mode set for created views to resize root object conveniently.
  • App icon size variant 172x172px introduced for Full HD displays
  • 3rd party app icons finally scale properly to different display resolutions.

Security

  • kernel: CVE-2014-9785, CVE-2014-9787, CVE-2014-9864, CVE-2014-9865, CVE-2014-9884, CVE-2014-9887, CVE-2014-9894, CVE-2017-9077, CVE-2016-5340, CVE-2017-1000364, CVE-2015-7872, CVE-2013-7446, CVE-2016-6786, CVE-2016-6787, CVE-2017-5970, CVE-2016-8480, CVE-2015-7550, CVE-2017-7618, CVE-2015-8767 (not yet fixed in jolla1 aka sbj)
  • kernel: CVE-2017-8890, CVE-2017-11176. (fixed in all kernels: jolla1 is patched)
  • display driver: CVE-2014-4323 (not yet fixed in jolla1 aka sbj)
  • bluez: CVE-2016-7837
  • libav: CVE-2015-8365, CVE-2017-9992, CVE-2017-7862, CVE-2015-8365.

Startup and shutdown

  • Patch for systemd (provided by our community) integrated to reduce logging.

System

  • Low memory killer enabled on Xperia. This should help preserving an adequate amount of free RAM.

Utilities

  • relocated in development repositories to make the app resistant against API changes.

UX

  • Android device hardware keys mapped to Silica actions of Sailfish OS on Jala Accione devices.

WLAN

  • automatic reconnection to saved hidden WLAN network
  • WLAN hotspot a.k.a. internet sharing fixed (Xperia).

Issues reported by the community at together.jolla.com and fixed in this update

Changelog

For detailed changelog, see https://together.jolla.com/question/179224/changelog-214-lapuanjoki/ .

Updating your device

Your device must be connected to the Internet and signed into your Jolla account. If your Jolla account is registered for Early Access releases you should receive an OS update notification when an update is available. If you have decided not to take the Early Access registration then you will get the OS update typically one week later.

We warmly recommend making some 3-4 GB of free space to the internal storage of your device before starting the update. Move your pictures and videos to the SD card (or to your PC or cloud service). After the upgrade turn on the option to save pictures and videos directly from the camera to the memory card (Settings > Apps > Camera). This is important particularly in case of "Jolla 1" devices (product name "Jolla" in Settings > About product).

This is the usual drill before attempting to update your devices:

Take a backup of your data before attempting to update your device and save the backup to an SD card or to some other off-device location (PC, your cloud service). Note that videos and images are not included in cloud-based backups. Do not reboot the device while the update is in progress. Do keep the phone connected to a battery charger during the whole process. Device screen may blank out during the update process; you may waken the display by a short press on the power key to monitor the progress.

For detailed instructions on updating software, visit Zendesk: https://jolla.zendesk.com/hc/en-us/articles/201836347

PLEASE NOTE:

If you installed 2.1.4.12 update manually from command line you need to do the following fix to get the repositories working:

[nemo@Sailfish ~]$ devel-su 
Password: 
[root@Sailfish nemo]# sed -ie 's/releases-internal.jolla.com/releases.jolla.com/' /usr/share/ssu/repos.ini 
[root@Sailfish nemo]# ssu ur

NOTIFICATIONS CONCERNING APPS FROM OPEN REPOS:

Installing OS update 2.1.4 automatically removes **Warehouse** (versions <= 0.3) and **Storeman** (versions <= 0.0.15) applications.

This is necessary because 2.1.4 brings in the new PackageKit that has changed its API. Warehouse and Storeman are locked against the older version of the library. If they are not removed during the update, they block the upgrade of PackageKit-Qt5, which then breaks all further updates (Settings page would get stuck on 'Preparing update' and version --dup would fail with an InvalidArgs error).

Warehouse and Storeman can only be installed again after they switch to the new PackageKit API.

In addition, take the following advice into account:

  • If you use Phonehook or Callrecorder from OpenRepos, uninstall it before upgrading.
  • If you use oFono from OpenRepos, revert to the official oFono before upgrading.
  • If you use Patchmanager, revert all applied patches before upgrading.

About SD cards

Please read our help article on SD cards supported by Sailfish OS: https://jolla.zendesk.com/hc/en-us/articles/201997993

Known issues

  • NEW: Jolla1 cannot route audio signal to Bluetooth accessories. => Fixed in 2.1.4.14.
  • Bluetooth pairing and audio connections may still fail in some circumstances
  • Utility "Clear tracker database" ("Refresh media database") is failing - will be fixed in update 2.2.0 (the next one)
  • VPN is still at beta level.

Known issues specific to Xperia X

  • Screenshots are placed to the end of the thumbnails list if Gallery app is open while taking the screenshot.
  • Issues with mobile data persist on some SIM cards
  • Xperia X does not power up due to an alarm
  • Manual network/carrier search lists all networks by the same name (the name of the SIM provider). Use automatic search. If not possible, you need to try several items in the manual search results, unfortunately. The top most item is not necessarily the one that can serve you. (still valid with most SIM cards)
  • VPN does not work.
  • Bluetooth: still problems with car equipment, some audio devices and computers.
  • Waking up the device by double-tap does not work
  • Loudspeaker volume level cannot be adjusted high enough (but echo cancellation was added to the audio path in 2.1.4)
  • Sensors:
    • not working: fingerprint, barometer, step counter.
    • compass (or gyro?) working in Google Maps, not yet natively.
  • Issues with video playback and video recording (less than before).
  • FM radio missing.
  • Even though all CPU cores get eventually enabled, foreground apps do not always run on the big cores.
edit retag flag offensive close delete

Comments

4

Hmmm... Bluetooth nightmare still not fixed or at least improved for Xperia X? I thought I could read it somewhere that this topic was on the list. Hopefully the X can be used now finally.

Anyway many thanks for this large new update package ;)

vision ( 2018-02-20 11:13:31 +0300 )edit

swap memory not enable?

TMavica ( 2018-02-20 11:40:34 +0300 )edit
4

For me on Xperia X, great update. Thanks for fixing internet sharing.

lispy ( 2018-02-20 16:09:02 +0300 )edit
1

Hungarian keyboard! Finally - thank you!

zlutor ( 2018-02-20 17:04:28 +0300 )edit
2

I have been waiting to see Sailfish in my own language for 4 years and 2 months! Thank you, Jolla! Too bad, my The First One does not live to see it.

Anyways, thank you! Köszönöm, LVPVS

LVPVS ( 2018-02-20 19:08:02 +0300 )edit

30 Answers

Sort by » oldest newest most voted
« previous123
1

answered 2018-02-21 05:02:27 +0300

DarkTuring gravatar image

updated 2018-02-24 04:27:40 +0300

Only minimally better mostly still not working:

  1. Xperia still laggy and slow, actually got worse since the update;
  2. Webview in email and other apps still slow and stutters on swipe;
  3. No cashing of email content or preload going on anywhere as far as i can tell;
  4. Connectivity improved for WIFI but for Android apps when switching between mobile to WIFI data reconnection or switch over doesnt occur always, but Mobile data connectivity hasnt improved;
  5. Searching and connecting to WIFI in range takes way too long;
  6. Display brightness auto adjust, is finicky and fluctuates when on medium brightness on auto and when light at <45deg angle hits the display;
  7. So far SFOS Apps and Android apps have crashed more often then before;
  8. Using an Android app and saving a file on the SDCard external, results in a user permission that i cannot even overwrite as nemo unless in the terminal under devel-su, so if i downloaded a virus app or file in Android, it would be impossible to remove- with usual user privileges which might be a security problem,
  9. Why is it sooo slow?
edit flag offensive delete publish link more

Comments

3

I've used Sailfish X 2.1.3.7 on an Xperia X 5121 daily since day one and can state for the record I have never experienced point 1, 2, 4, 7, & 9. I don't feel 5 is a problem, 6 I have never used, and as for 8 I don't have android support installed. Either the latter is your problem, or you have something else seriously wrong going on with your phone, but it doesn't apply to everyone.

bocephus ( 2018-02-21 08:31:50 +0300 )edit

Can camera button be improved so that it would open camera even when screen locked?

Also would like that Nordea mobile bank android app would work again. Newest version 2.6.1 FI 100987 doesn't work with 2.1.3.7 or 2.1.4.2.

What about USB OTG on Xperia X? Would really need this for one Android app.

peakki ( 2018-02-21 08:45:44 +0300 )edit
1

Webview stuttering and email client freezing are because of big.LITTLE architecture not being taken.into consideration when allocating corea to processes. It is a very hard task to implement in in kernel 3.x, but for Xperia X there is Android 7 AOSP release based on kernel 4.4, which would improve that quite a bit. Let's hope Sailfish 3 is built on top of that (I have no idea whether it is or not).

Direc ( 2018-02-21 23:41:18 +0300 )edit

@bocephus Webview slowness is a known issue and you will encounter it if you open an email containing html or use an app based on QtWebkit

Sthocs ( 2018-02-22 01:24:12 +0300 )edit
  1. I should say camera launch speed and reliability in Android Apps actually has improved.
DarkTuring ( 2018-02-22 23:01:34 +0300 )edit
2

answered 2018-02-20 19:55:29 +0300

LVPVS gravatar image

Hei,

Thank you for the Hungarian language and vkb layout!

There is one minor glitch I noticed: after pressing the '?123' key, the first key in the top row should be '0' and not '1'.

Nothing I could not fix but still.

Kiitos,

LVPVS over.

edit flag offensive delete publish link more
0

answered 2018-02-20 18:17:38 +0300

Lutwolf gravatar image

Dammit, updating bricked my Jolla 1.

I couldn't update via GUI ("Please try again later"), so I did that in Terminal (everything as Jolla itself suggests, and I didn't have any typos). The phone tried to update 10 times before it aborted - there was a brief message that a certain rpm couldn't be found. There was a "restart on your own risk" message, and after restarting there's only a slowly flickering white screen. The /var/log folder was empty, and there was no /home/ folder in Recovery Putty Telnet mode (maybe relevant, maybe not). What can I do? Is factory reset my only option?

edit flag offensive delete publish link more

Comments

recovery mode does not mount home or system as far as I know

idnovic ( 2018-02-20 18:27:27 +0300 )edit

Is there a way to mount /home/ to either a) fix the system or b) recover and save user data not saved on SD?

Lutwolf ( 2018-02-20 20:36:41 +0300 )edit
2

yes but I do not remember top of my head. How familiar are you with linux? home and system are one lvm device. Here is what I did (as far as I remember); mount lvm (home + system); chroot into system; reroute network to have internet over usb; at this stage you can even install/uninstall apps over terminal;

here is a partly useable guide: https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode and https://together.jolla.com/question/114716/what-is-the-tablets-fs-and-partition-scheme/?answer=114743#post-id-114743

idnovic ( 2018-02-20 20:57:34 +0300 )edit

Thank you, I already did that short while after writing above text ^^ Next time I'll read before I write, resp. torture the internet more purposefully :)

Lutwolf ( 2018-02-20 21:29:41 +0300 )edit
0

answered 2018-02-20 18:09:51 +0300

p1rat gravatar image

hello,

tried to update, but the "Preparing Update" runs endless.

How long does it normaly take?

then I tried to force the update via terminal as root:

"# version --verify

"# ssu release 2.1.4.13

Changing release from 2.1.4.13 to 2.1.4.13

Your device is now in release mode!

"# version --dup

REFRESHING CACHE AND DOWNLOADING PACKAGES [W] PackageKit::Transaction::parseError:803 - Transaction::parseError: unknown error "org.freedesktop.DBus.Error.InvalidArgs"

and my phone came to following error.

Does anyone know what this error mean and how to fix it?

regards christian

edit flag offensive delete publish link more

Comments

Usually invalidArgs is mismatch between old and new packagekit vs packagekit-qt packages. For example system otherwise updated but something like those warehouse and storeman openrepos things forcing old packagekit-qt version. Can also be system updated with version --dup and not being rebooted so old packagekitd is still running.

Pekka Vuorela ( 2018-02-20 19:21:44 +0300 )edit

I think you have to remove Warehouse and Storeman. It's in the release notes actually.

Direc ( 2018-02-21 23:35:16 +0300 )edit

@Direc: they're automatically removed if they're incompatible.

nthn ( 2018-02-22 13:43:13 +0300 )edit
0

answered 2018-02-20 17:39:57 +0300

idnovic gravatar image

updated 2018-02-21 03:51:24 +0300

FIXED

I downgraded from 2.1.4.12 to 2.1.3.7 and was able to update to 2.1.4.13

Update log still empty....

I am not able to update (XperiaX) from 2.1.4.12. I deactivated all patches. Update log is empty. I already fixed the "internal" repos.

Already tried ssu release 2.1.4.13 and version --dup. Updated about 12 packages.

ssu release 2.1.4.13 && version --dup

ssu tells me I am on 2.1.4.13 but the rest of the system thinks I am on 2.1.4.12 (About Device, Update Notification) - If I update over the gui I get: 

Unable to update Sailfish OS. Please try again later

The update notification is still remembering me to update to 2.1.4.13

edit flag offensive delete publish link more

Comments

1

Jolla never intended for any regular user or early access subscriber to update to 2.1.4.12. Let this be a lesson to you. Maybe next time you'll stay away from the command line and do what all children eventually have to learn to do: WAIT.

bocephus ( 2018-02-22 03:59:24 +0300 )edit
5

answered 2018-02-20 16:56:17 +0300

kenya888 gravatar image

Hi, I'm kenya888, the coordinator of Japanese community translation team.

Thank you all Jolla and community folks for great continuous effort of evolving Sailfish OS long time :) We team members are very happy seeing announce of Japanese system language support on SFOS 2.1.4.

I tried v2.1.4.13 early access on Sailfish X now and found that Japanese language support is dropped due to a lack of the file /usr/share/jolla-supported-languages/ja.conf. I can't see the Japanese "日本語" choice on the Language menu of jola-settings.

Here is my investigation.

  • I've confirmed many of *-ja.qm translation files exist in the system.

  • I've also confirmed seeing lang menu entry of Japanese and switching lang setting to Japanese by adding ja.conf file by hand and reboot.

Could you let me know is it what you intended or just a mistake? The Jolla blog entry doesn't mention about Japanese support despite exist in this release note.

We Japanese team will be happy if this issue is resolved.

Regards.

kenya888

edit flag offensive delete publish link more

Comments

You can obtain ja.conf file from openrepos

kenya888 ( 2018-02-20 17:04:47 +0300 )edit
4

Hi. Sorry for the mistake (of listing Japanese and Korean in these notes). We have the Japanese strings but not the enablers as the input methods are missing. Getting/making them will require a substantial amount of more work. However, support for Japanese and Korean is in our plan. We will keep working.

jovirkku ( 2018-02-20 17:42:51 +0300 )edit
1

@jovirkku Thank you for your respose. I understand that you don't intend to list Japanese (and Korean) support on this note. Could you let me know a little more about the plan of IM for Japanese and Korean? We Japanese community team would like to put some pre-making feedback( in the other words "Request") to improve user experience with Japanese IM. Could you consider to give us a chance to inform our request to you before deep development of it? Will you feel bad if I open new question about this topic on together.jolla.com?

Regards.

kenya888

kenya888 ( 2018-02-21 02:27:54 +0300 )edit
3

answered 2018-02-20 15:47:20 +0300

R.G. Sidler gravatar image

Hi. I can''t find any reference to the Jolla Tablet - will it receive this update, too?

Sincerely

Roland

edit flag offensive delete publish link more

Comments

1

At least my tablet did!

vige ( 2018-02-20 17:52:54 +0300 )edit
3

yes, and the volume issue is resolved!

AkiBerlin ( 2018-02-20 18:24:13 +0300 )edit
0

answered 2018-02-20 12:20:45 +0300

thisisme gravatar image

Joilla C, tried to update from 2.1.3.7, after downloading I chose to install update and the process seems stuck. I looked at /var/log/systemupdate.log and the same thing seems to be repeating over and over - maliit service fails to start up, then osupdate service restarts: systemupdate.log

Should I reboot at this point? Or will the procedure time out eventually?

edit flag offensive delete publish link more

Comments

1

Hi, reboot and try again. It would be good to get all of the following logs and printout from the commands. Please file a help request then at https://jolla.zendesk.com/hc/en-us/requests/new. Attach the logs there.

/var/log/systemupdate.log
/var/log/systemboot.log
/var/log/zypp/history
rpm -qa
ssu lr
export COLUMNS=400; journalctl -a -n10000
jovirkku ( 2018-02-20 14:01:29 +0300 )edit

Hi, thank you for your guidance . I already tried rebooting but the same thing happens. I will try one more time to gather the requested logs when I get home!

thisisme ( 2018-02-20 15:07:31 +0300 )edit

Hi, I got the same issue with mij Jolla C

BoertjE ( 2018-02-20 15:12:31 +0300 )edit

Hi, issue opened:

https://jolla.zendesk.com/hc/en-us/requests/32674

thisisme ( 2018-02-20 19:21:18 +0300 )edit

Did a retry at home on the Jolla C again, update worked now. My Xperia X was succesfull updated at work the first time.

BoertjE ( 2018-02-20 22:18:18 +0300 )edit
3

answered 2018-02-20 11:53:25 +0300

mcencora gravatar image

updated 2018-02-20 12:23:01 +0300

I tried updating, but once OS update download was completed and device (Xperia X) has restarted, I got "Unable to update Sailfish OS. Please try again later". Device has frozen on this screen - I cannot reboot it (UI is not responding, and hardware power button has no effect).

FWIW I had 2.1.4.12 manually installed before, and applied the sed replacement as specified above.

[SOLVED] "Power + Volume Up" button combination did the trick

edit flag offensive delete publish link more

Comments

My xperia booted fine from recovery console.

teve ( 2018-02-20 12:08:32 +0300 )edit
2

Holding power + volume seems to do a hard power-off

Mazoon ( 2018-02-20 12:22:04 +0300 )edit
5

Disabled yeoldegrove repository from openrepos.net, did a pkconf refresh and now update is installing. That repo has a gpupg2 which seems to conflict with this update.

Feb 20 12:00:48 Sailfish store-client[6522]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotPackage(PackageKit::Transaction::Info, const QString&, const QString&) 10 "gnupg2;1:2.0.4-1.1.2;armv7hl;jolla" "Utility for secure communication and data storage" Feb 20 12:00:48 Sailfish store-client[6522]: [D] unknown:0 - void Package::DistUpgradeTransactionPkgKit::slotTransactionError(PackageKit::Transaction::Error, const QString&) 37 "Download (curl) error for 'https://releases.jolla.com/releases/2.1.4.13/jolla/armv7hl/core/armv7hl/gnupg2-2.0.4-1.1.2.armv7hl.rpm':\nError code: Connection failed\nError message: Couldn't resolve host 'releases.jolla.com'\n"

teve ( 2018-02-20 12:42:27 +0300 )edit

how did you get the update log? Mine is empty. I did like to find out what the problem with my device is.

idnovic ( 2018-02-21 03:05:26 +0300 )edit

I've got the same error message during the update process, after a due update for "File Browser" and a "pkcon refresh" the installation went smoothly. Thanks @teve for giving me the valuable hint above!

MeegoUser ( 2018-03-09 01:49:29 +0300 )edit
29

answered 2018-02-20 11:05:25 +0300

ghling gravatar image

Regarding the OpenRepos clients (warehouse and storeman): There is a new version of storeman available already which works with 2.1.4.13: https://openrepos.net/content/osetr/storeman

edit flag offensive delete publish link more

Comments

The openrepos apps like patches are still present after updating to 2.1.4.13. I wonder if they are still working without Warehouse. I though every openrepos apps will disappear with Warehouse.

N9Sailfish ( 2018-02-20 16:11:57 +0300 )edit
3

All apps installed prior to the update should still work (unless changes in the SFOS update itself breaks them) as they are normally installed packages. All warehouse or storeman are doing is providing a GUI to browse openrepos.net, enabling / disabling repositories and handling packages (install, remove, update). They provide convenience for all the inexperienced and/or lazy users, you can actually do all those things yourself on the command line.

ghling ( 2018-02-20 16:36:49 +0300 )edit
« previous123
Login/Signup to Answer

Question tools

Follow
20 followers

subscribe to rss feed

Stats

Asked: 2018-02-15 13:59:39 +0300

Seen: 31,842 times

Last updated: Jun 05 '18

Related questions

[Release notes] Opt-in upgrade to software version 1.1.0.38 / Uitukka [released]

[release notes] 1.1.6 / Aaslakkajärvi [released]

[release notes] 2.0.2 / Aurajoki [released]

[Release Notes] Software version 1.0.4.20, Ohijärvi [released]

[Release notes] Software version 1.0.5.16, Paarlampi [released]

[changelog] 1.1.6 / Aaslakkajärvi [released]

[changelog] 1.1.9 / Eineheminlampi [released]

[changelog] 2.0.1 / Taalojärvi [released]

[changelog] 2.0.2 / Aurajoki [released]

[changelog] 2.0.4 / Fiskarsinjoki [released]

Copyright © Jolla Ltd. 2013-2019. All rights reserved.
about | faq | help | privacy policy | terms of service | give feedback
Powered by Askbot version 0.7.49