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

[release notes] 3.2.0 Torronsuo [released]

asked 2019-10-03 11:29:03 +0300

jovirkku gravatar image

updated 2019-11-22 10:25:21 +0300

Many thanks to you our active contributors for your feedback and proposals.

Table of content

Update version history

  • 2019-10-29: 3.2.0.12 was released to Early Access subscribers
  • 2019-11-06: 3.2.0.12 was released to all subscribers
  • 2019-11-19: 3.2.0.14 was released for Sony Xperia 10 and 10 Plus.

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 1 from 3.1.0 to 3.2.0: about 380 MB
- Jolla C from 3.1.0 to 3.2.0: about 410 MB
- Xperia XA2 from 3.1.0 to 3.2.0: about 630 MB
- Xperia X from 3.1.0 to 3.2.0: about 480 MB

Device models supported by Sailfish X

The instructions for installing Sailfish OS to Sony Xperia X, Xperia XA2 and Xperia 10 devices are here - covering Windows, Linux, and macOS.

The supported Sony Xperia 10 models are:

  • 10 single-SIM: I3113 and I3123
  • 10 dual-SIM: I4113 and I4193
  • 10 Plus single-SIM: I3213 and I3223
  • 10 Plus dual-SIM: I4213 and I4293

The supported Sony Xperia XA2 models are:

  • XA2 single SIM H3113 (also H3123, H3133)
  • XA2 dual SIM H4113 (also H4133)
  • XA2 Ultra single SIM H3213 (also H3223)
  • XA2 Ultra dual SIM H4213 (also H4233)
  • XA2 Plus single SIM H3413
  • XA2 Plus dual SIM H4413 (also H4493)

The supported Sony Xperia X models are X single SIM F5121 and X dual SIM F5122

The supported Gemini PDA models are x25 and x27.

Contributions from Sailfish Mobile OS RUS (Aurora)

Several of the key improvements in this release were developed for Sailfish Mobile OS RUS (OS Aurora) and contributed by OMP to the Sailfish OS.

Here are some of the key contributions and features developed with OMP's support

  • Phone redesigns and improvements: Call reminder feature introduced, Incoming call showing country for foreign calls, Call ending dialogue redesigned
  • Support for Active Sync out of office reminders
  • File Manager shows the folder size, and an error message was added for file and folder name conflicts
  • Ability to customize OS name and use customized name for example used in the default email signature
  • More enterprise EAP options are supported for WLAN connections
  • OpenVPN encrypted certificate password fixes
  • User data encryption developed further and SELinux prepared for deployment
  • Security fixes (CVEs) for dbus, expat, lua, openssh, patch, QualPwd, systemd
  • Added support for different types of Bluetooth Low Energy (BLE) devices
  • Battery notifications improved to reduce unnecessary notifications

Jolla appreciates collaborative efforts of its partners and community to make Sailfish OS even better.

Release Highlights

This list below contains examples of new features (and some bug fixes) added to Sailfish OS, compared to the previous public release 3.1.0. The release notes of 3.1.0 can be found here.

Xperia XA2

  • Kernel updated to 4.4.189
  • Sailfish OS 3.2.0 can be installed on Android 9 now (no need to downgrade to Android 8.1)

Accounts

  • Dropbox: Migrated away from deprecated media info API
  • If no accounts installed on a device that supports Presence, then Settings > Presence item is not shown
  • Hardcoded /home/nemo/ removed from sailfishkeyprovider; home path read from $HOME environment variable now

Android™ App Support

  • Android™ App Support for Xperia XA2 devices improved
    • Android Support (a.k.a. aliendalvik) updated to android-8.1.0_r65
    • Using the android.hardware.power service allowed. Makes different performance and low power modes possible
    • Using the android.hardware.memtrack service allowed. Helps in getting information about used hardware resources
    • Missing file browser added to make it possible for Android apps to share files by default
    • Mobile data works now also when one of the SIM cards (dual SIM devices) is disabled
    • Opening Android apps work better now
    • Period/comma characters added to Android keyboard; Enter key recognised now
    • Copying contacts from Sailfish to Android apps work smoothly now. Out-of-memory loop eliminated.
    • Android keyboard pops up reliably

Backup & Restore

  • Backup service can now get the information on the available storage reliably. An API added to the PartitionModel to tell when external storages are populated.
  • Legacy git-tree vault code and libraries removed as the more recent implementation does not use them

Battery & Charging

  • Battery notification logic was rewritten to reduce the number of disturbing notifications

Bluetooth

  • Support for different types of Bluetooth Low Energy (BLE) devices added, i.e. pairing and connections from Sailfish do work. However, using the devices requires a BLE application which we do not have. Android apps are lacking access to Sailfish Bluetooth service, still.

Browser

  • Problems in accessing Twitter with Sailfish Browser fixed
  • WebGL support fixed

Calendar

  • Avoided forcing all calendars to be synced when making changes to one

Camera

  • Showing the SD card as the target for saving pictures fixed

Clock

  • Snooze interval is configurable now - see Settings > Apps > Clock
  • Timers finally allow choosing seconds
  • Pulley menu action added for reseting the saved timers to the beginning

Connectivity

  • Edit view of WLAN connection extended with more enterprise EAP options
  • Adding a WLAN network: Save button fixed
  • Counters of mobile data fixed
  • After turning flight mode off, the device can connect back to mobile data
  • Swapping of SIM cards between the two slots does not disturb the subsequent connections.
  • Polling interface statistics when all interfaces are down stopped
  • OpenVPN encrypted certificate password dialogues and password use is fixed. VPNAgent is used for credential retrieval, an encrypted certificate password is not saved by VPNAgent.

Email

  • OS name used instead of "Jolla" in default email signature

Documents

  • Writing comments (annotations) to PDF files sometimes crashing Documents app fixed
  • Calligra backend updated to the latest upstream, bringing in many bug fixes to displaying of office formats - Community contribution from Damien Caliste - thank you!

Messages

  • We hope that the recent SMS problem got eliminated (at least alleviated) with this OS update

People

  • Performance regression in contact search fixed
  • Avoid duplicate empty fields in contact editor, one empty field is enough at a time

Phone

  • Call reminder feature introduced
    • You can set reminder to call back when receiving an incoming call, or from call history
  • Call ending dialog redesigned
    • If you end the call only non-blocking notification is shown
    • If the remote side disconnects a new system dialogue is shown with actions to call back, send message or add a reminder
  • Incoming call now displays country of the caller if coming from abroad
  • More than two emergency calls possible in a row, now
  • An attempt was made to prevent calls from being accidentally held [Xperia X devices]. Proximity sensor utilization was tweaked to improve the reliability of in-call blanking behaviour. Unfortunately, this change also affects the Sneak Peek feature. Those users who have not experienced problems with in-call proximity blanking and wish to continue using Sneak Peek can revert back to the previous behaviour by executing mcetool --set-ps-on-demand=disabled from the command line.
  • Call UX improvements are ongoing work with further improvements planned

Security

  • User data encryption (a.k.a. encryption of Home partition, disk encryption) was developed further. However, on 3.2.0, this feature is mainly included in freshly flashed corporate devices and in one consumer device only: Xperia 10. User data encryption can be left out from a device configuration by not setting the security code during the initial startup of a device. However, if encryption is enabled during the startup then it cannot be disabled any more (other than by reflashing the device).
  • Security framework SELinux being developed in the background, not yet ready. Enabled in permissive mode on Xperia 10 Vulnerabilities fixed:
  • dbus 1.13.12: CVE-2019-12749, CVE-2015-0245
  • expat 2.2.7: CVE-2015-1283, CVE-2016-0718, CVE-2016-4472, CVE-2016-5300, CVE-2012-6702, CVE-2017-9233, CVE-2016-9063
  • kernel/sony/msm-4.4/kernel: CVE-2019-10538, CVE-2019-11477, CVE-2019-11478, CVE-2019-11479
  • lua 5.3.5: CVE-2014-5461, CVE-2019-6706
  • openssh 8.0p1: CVE-2019-6111
  • patch 2.7.6: CVE-2019-13638, CVE-2019-13636, CVE-2018-1000156
  • QualPwn CVE-2019-10538
  • systemd 225+git19: CVE-2013-4391, CVE-2018-16865, CVE-2018-16866, CVE-2016-7795, CVE-2019-3842

Settings

  • If no accounts installed on a device that supports Presence, then "Settings > Presence" item is not shown
  • Snooze interval is configurable now - see "Settings > Apps > Clock"

SIM

  • Swapping of SIM cards between the two slots does not disturb the subsequent connections

Storage

  • File Manager shows the folder size now in details page
  • "Cannot copy into itself" error message was added for file and folder name conflicts

Sync

  • Prevent extra spurious sync action during off-peak hours. Verify that sync schedule is compatible with a wake-up time

UX

  • Content deletion use cases redesigned to reduce confusion new users face. Further improvements are coming in the next release
  • Brightness of pulley menu indicator increased, users sometimes miss the indicator and are unable to access the functionality in the pulley

WLAN

  • Edit view of WLAN connection extended with more enterprise EAP options
  • Adding a WLAN network: Save button fixed

T.J.C: Issues reported by the community and fixed in this update

All of the links below may not open up for everyone, sorry.

Technical changes

Changelog

Detailed changelog is kept here

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 the case of "Jolla Phone" 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, read our help article in Zendesk.

OS release 3.2.0.12 is a so-called Stop Release. There are several Stop Releases in the Sailfish OS update path. They are mandatory intermediate steps in the update path through which the update process must traverse if a device is updated starting from an early OS release. The previous Stop Release was 3.0.0.8.

NOTE: Sailfish OS does not support downgrading. Never try to downgrade the OS as this would break your device.

Notification concerning apps from Open Repos

  • 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

  • Encrypted cards must be unlocked by the user to make them available for Sailfish applications.
  • Non-encrypted cards are mounted automatically when the device is turned on.
  • Encrypted cards can be formatted only when they are locked. Formatting removes the encryption in this case (the card becomes unencrypted and unmounted). You can then format it again with the option to encrypt, if needed.

Known issues - generic

  • VPN does not work in case of Android apps
  • Sailfish can connect Bluetooth Low Energy devices now. However, Android apps cannot use peripheral devices via Bluetooth - other than for playback of the sound. Therefore smartwatches, for instance, cannot be controlled from Android apps
  • Bluetooth pairing and audio connections may still fail in some circumstances
  • The chacha20-poly1305 cipher is not currently working, which is often chosen for SSH. It has been disabled in the sshd configuration file, but if you have manually modified it then it will not automatically update. You can ssh into your device using ssh -c aes128-ctr and check the /etc/ssh/sshd_config file against its rpmnew version if present.

Known issues specific to Xperia X

  • Not implemented features: NFC, FM radio, double-tap, step counter
  • Issues with mobile data persist on some SIM cards. Turn the Flight mode on and off to reset the network setup. Reverting the device to Android and re-installing Sailfish X has often helped. See our support article.
  • Manual network/carrier search lists all networks by the same name (the name of the SIM provider). Use an automatic search. If not possible, you need to try several items in the manual search results, unfortunately. The topmost item is not necessarily the one that can serve you (still valid with most SIM cards)
  • [camera] Force autofocus mode for photos, and continuous for video. After this, camera focus is still not ideal - as the camera stays out of focus when it starts until you either tap or try to take a shot - but the pictures seem to be better focused now
  • If a device is powered off alarms are not functional
  • Bluetooth: problems with some car equipment, some audio devices and computers may appear
  • The loudspeaker volume level cannot be adjusted very high
  • Not all SD cards are recognized and mounted.

Known issues specific to Xperia XA2

  • Not implemented features: FM radio, double-tap
  • Bluetooth: there are problems in connecting to some peripheral devices
  • XA2 does not power up when alarm time has elapsed
  • Flashing Sailfish X to XA2 might still fail (so far seen to happen on Ubuntu 18.04 when using USB3 port). Please read this article.
  • With v17B Sony vendor image we observed a decrease in the perceived signal strength of the 5GHz WLAN access points (investigations ongoing). Version v16 may work better in this respect. Therefore we would not recommend flashing v17B for the time being if you use WLAN networks in the 5GHz band. You can reflash the vendor image of your choice by following the instructions in here.
  • Voice calls with Whatsapp are not usable as the voice volume level is minimal (if can be heard at all). This is expected to get fixed in the next OS update (3.2.1). (This should get fixed with OS release 3.2.1 "Nuuksio")
  • Video playback in Whatsapp requires special actions: 1) Tap on video 2) Tap the share button (top right) 3) Tap back arrow 4) Tap Play on the video. Now it starts playing...
  • A locked-up device with display dimmed does not indicate an incoming Whatsapp call in any way
  • Pictures/videos on SD card are not visible to Android apps.

Known issues specific to Xperia 10

  • Fingerprint recognition may sometimes fail to work. In such a case, restart the device and it works again.
  • Rarely, audio playback and sensors (display rotation) may stop working. If this happens, please restart the device
  • No support for FM radio
  • No support for the dual-lens camera
  • Whatsapp video call, incoming calls and video playback might have issues - but often caused by the lack of settings and permissions. Please see our Whatsapp help article
  • In some cases, the acceptance of SIM/PIN may take up to 12 seconds
  • During the decryption of user data in device start-up, there is a period of 10-20 seconds such that the display is black

Known issues specific to Gemini PDA

  • Gemini Screenshot Button Fn + X does not work
  • Not possible to answer calls when Gemini is closed with side button
  • Some 3rd party apps have issues in Landscape mode.
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2019-12-28 22:19:21.591228

Comments

14

First try:

It downloads too quickly, it goes through the install procedure far too quickly, the white loading bar zips across the screen and the reboot is extremely quick as well, but upon checking the OS has not been updated.

Second try:

Same as above, when restarted, the device is NOT updated

Third try:

Same as above.

Fourth try:

No, I'm going out, fresh air and sunshine

Spam Hunter ( 2019-10-29 14:01:48 +0300 )edit
4

Haha, same here at first try on an XA2 ;-p

The download ends at ~10% and says ready to install.

One should try using the command line.

Maximilian1st ( 2019-10-29 14:15:49 +0300 )edit
4

experiencing the same with XA2. Two times tried.

peakki ( 2019-10-29 14:16:42 +0300 )edit
9

On my Xperia X (3.1.0.11), the size of the update is indicated as 70 MB which seems rather small.

And, to be honest, the list of improvements appears disappointingly short given the three months since the last update. At least for Xperia X, where some of us expected an update to Android app support.

ziellos ( 2019-10-29 14:18:08 +0300 )edit
6

Will try later in the evening when I am next to my device. Seems that the majority of work is coming externally from Aurora. Not necessarily a bad thing since there is progress and someone is driving the development forward but still a bit of a concern with regards to the future.

cquence ( 2019-10-29 14:25:12 +0300 )edit

18 Answers

Sort by » oldest newest most voted
« previous12
1

answered 2019-11-09 11:22:07 +0300

kriziak gravatar image

So first, in upgrade notes for Torronsuo didn't be mentioned some problems, that I have on two sailfish OS phones we use. I wrote it here to jolla together as bugs, but nothing happens. After rebooting sometimes the mobile network isn't reachable, GPS localization is too slow (sometimes 5 minutes and more), status bar is disappearing under 10 % of battery after restart, phones are too slow and unusable under 10 % of battery (I have XA2 plus with 6GB RAM!!!). This morning I upgrade to Torronsuo and later I'll test what changes are in these problems I have. But almost now I can say that there two more problems with Torronsuo. 1. After restart the mobile network isn't automatically reachable, so I must go tu SIM slot setting, turn on empty slot 2, turn off slot 1, then turn on slot 1 and turn off slot 2. This makes mobile network working. But after upgrade, in every android app, when I made this procedure with turning on/off slots, the android app restarts itself because of new SIM detected. It takes time to launch it. So one bug (unreachable mobile network) remains, other one appeared. 2. I use hide-word-suggestions patch for remove preddicative text proposition from the keyboard. There is more space for reading messages, webpages and so on. But after upgrade to Torronsuo this patch doesn't work. It is able to remove this row with proposition of input text directly in Sailfish settings?

edit flag offensive delete publish link more

Comments

  1. After upgrade display stays still on instead of 30-seconds timer to turn off. WTF (I wrote no.3 in beginning of this comment and it shows no. 1, wtf)
kriziak ( 2019-11-09 16:16:37 +0300 )edit

After few days of use: display stays sometimes still on; under 10% phone is unusable, slow, this website load takes 10 minutes, writing this comment is tragedy (phone is actually under 10 % and response for writing is over second)

kriziak ( 2019-11-12 12:55:08 +0300 )edit
1

answered 2019-11-09 16:32:34 +0300

xbt123ufo gravatar image

Good job, jolla! The battery life of xa2 has improved a lot. Please keep working hard to make it last longer than Android.

edit flag offensive delete publish link more
1

answered 2019-11-11 10:39:10 +0300

pearly dragon gravatar image

Snooze interval is configurable now - see Settings > Apps > Clock

Great news! Half functionality of usual alarm N900 we have!

edit flag offensive delete publish link more
0

answered 2019-10-30 13:44:52 +0300

yomark gravatar image

updated 2019-10-30 13:46:12 +0300

So, after the update bricked my phone yesterday, I did a factory reset from recovery, and let it update itself to 3.2.0 again. Now I have the issue that my time/timezone is one hour wrong when using network time(for example 11:43 in stead of the correct time 12:43). I'm living in the Netherlands. However, a website like https://browserspy.dk/date.php diplays the correct time(uses webborwser exposed time).

When I set it to the correct time manually(selecting the right timezone) apps like SailOTP do not work anymore. https://browserspy.dk/date.php gives a 3600 second offset.

Any ideas?

edit flag offensive delete publish link more

Comments

Just for reference, it works fine on my Jolla 1. Updated from 3.1 to 3.2 and time is correct. Can you disable NTP, reboot, and enable NTP? Just an idea, it might need some manual help :)

Marcel Pol ( 2019-10-30 19:06:32 +0300 )edit

Hej, I'm still evaluating the browser which has been a constant source of disappointment for the last FIVE years!

My issue with thermal shutodwn when using the browser on the tablet seems resolved (but still testing). However an issue that somebody else reported is still there, duolingo.com just loads as an empty white page.

Does 3.2.0.x give any substantial browser improvements or is the current shitty solution being perpetuated? The release notes on this topic are still very thin.

cfgardiner ( 2019-10-30 19:06:36 +0300 )edit

To be fair, the "shitty solution" was improved massively in the previous (?) release. As a passing curiosity, what issues do you see on a regular basis in general use?

DrDweeb ( 2019-10-31 11:34:04 +0300 )edit

I suppose the absolutely most annoying thing with the browser is that many pages load to about 92% (according to the progress bar) but absolutely nothing is displayed for several minutes. I get this regularly (i.e. almost always) with pages like the German newsticker http://spiegel.de/schlagzeilen. I am using J1 or tablet. There is not even access to the reload icon which might be helpful in kicking the browser out of whatever indefinite loop it seems to be hanging in. Why is it so difficult to start rendering as soon as enough content has been fetched or just cut down the maximum waits to something more useful like 1s max? After all, Jolla claims to do true multi-tasking

Even a badly rendered page is better than nothing at all, as long as it can be read somehow. If the presentation of various fancy advertising gimmicks is screwed up, who cares? I definitely don't.

The second most annoying thing is of course pages that don't display at all, such as duolingo.com which has been reported by somebody else recently and which I can confirm.

The third most annoying thing would be random crashes. But this has been hard for me to quantify. Some days Jolla is indeed not any worse than PC browsers in this aspect.

cfgardiner ( 2019-10-31 13:08:47 +0300 )edit

Nicely resolved by @yomark in "Factory reset, several upgrades->3.2.0 : Timezone issues [solution]".

olf ( 2019-11-01 02:57:05 +0300 )edit
0

answered 2019-11-07 12:39:32 +0300

NGC-Ollie gravatar image

I had some trouble with my encrypted SD card on my XA2+, the message was: "you don't have the permission" or similar. But my upgrade was smooth, everything booted. I did a backup to rhis SD card before installing, worked. After reboot to 3.2 no permission, other reboots without change. I switched off my phone, removed the card and put it into a linux PC. After installing libblockdev-crypto2 on my debian10 i had access and backuped the card. Back into the phone access was granted....

So if anyone got problems with the encrypted cards, always have a Linux on your side.... oh wait... always have a Linux!

edit flag offensive delete publish link more
0

answered 2019-11-08 10:19:29 +0300

Wizor gravatar image

Installed the update last evening (Xperia X F5121) and so far so good EXCEPT that the time is now lagging two hours behind if i keep the time updating at Automatic. Selecting a different timezone doesn't help. I really thought that i woke up at 5am in the morning but noticed soon outside that it was well over 7am :)

Doubletap stopped working also and i re-enabled it with mcetool. So gotten used to it and it works ok most of the time. Well, after a reboot (thought that would fix the time problem. It didn't.) it seems i have to use mcetool again.

Top menu had found it's way back to pestering in the middle of the top of the display. Had to again remove it from Compositor.qml. I hate that thing. Always in the way of important closing of things.

my 5 cents.

edit flag offensive delete publish link more

Comments

Why not use @cornerman's no home carousel? Close your stuff wht a side sweep and top menu can stay. Doubletap is badly missing here too, perplexing @Jolla can't bring that to work properly.

danfin ( 2019-11-08 10:39:31 +0300 )edit

Oh i like the home screen as it is. And frankly it's in my spine nowadays to close the app from the top. I could ofcourse go the easy way and keep Toeterm always open and just kill them there :)

Time problem escalated too. I've switched to manual mode since this morning and clock now shows normal time and i hope alarms work as they should. But when i receive a text message the UI shows that it came TWO hours ago. Then i noticed that when checking bus timetables with Jollaopas it shows the route probably ok, but it shows how the buses went TWO hours ago. Although i'm pretty sure the timetable is correct, but the timecalculations for the GUI are not. Likewise in the Message view. date-command in shell seems to act normally.

Wizor ( 2019-11-08 17:10:39 +0300 )edit

I missed the fix by @yomark Now the time problem is solved.

Wizor ( 2019-11-08 17:21:59 +0300 )edit
0

answered 2019-11-09 23:09:30 +0300

bongo gravatar image

Still not seeing the update on my phone settings->update. (xa2 3.1.0.11)

Are they still in the process of rolling it out?

edit flag offensive delete publish link more

Comments

@bongo: No, 3.2.0 became available for all users on November 6th. I wonder if this article helps you at all?
https://jolla.zendesk.com/hc/en-us/articles/201836347

jovirkku ( 2019-11-12 16:25:58 +0300 )edit
0

answered 2019-11-23 11:16:04 +0300

AlexOm gravatar image

Nice to to see further great development! Thank you Guys! ...by the way still exists issue with disappearing volume top bar from time to time. Don't know what's responsible for that. Fixed only by UI restart (Settings --> Utilities). And I see one more issue with some Android support: the 'stop application' button from Settings App menu doesn't unavoidably stops all apps components. For example Pavel's Durov Telegramm App still continues work at memory probably as service without UI. And moreover it can't be killed by nemo user because of changed application owner (its just numbered as 10041, no readable name). So I can stop that app by kill signal only as superuser either by stopping the whole android app subsystem.. So nasty and hazardous droid app behaviour should be prevented I think :) Could it be done somehow gracefully??

edit flag offensive delete publish link more
« previous12

Question tools

Follow
13 followers

subscribe to rss feed

Stats

Asked: 2019-10-03 11:29:03 +0300

Seen: 25,445 times

Last updated: Nov 23 '19

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