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

[release notes] 2.2.1 Nurmonjoki [released]

asked 2018-07-13 16:46:28 +0200

jovirkku gravatar image

updated 2018-10-20 20:47:00 +0200

walkingzen gravatar image

In Nurmonjoki release Email app has seen multiple improvements like support for ActiveSync meeting invitations, read receipt support and various improvements to attachments handling. Sailfish OS (Jolla account, settings) has been updated to comply with GDPR requirements. VPN connections now work more robustly when switching between networks. In addition several security issues, account creation issues and a number of other bugs were fixed.

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

Table of content

Update version history

  • 2018-09-04: was released to Early Access subscribers (Jolla devices and Xperia).
  • 2018-09-12: was released to all Jolla customers having the following devices: Jolla1, Jolla C, Jolla Tablet, Xperia X (f5121 and f5122). Installable images for Xperia X devices are available at https://shop.jolla.com/downloads/ .

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 to 2.2.1: about 340 MB
- Jolla C from to 2.2.1: about 380 MB
- Xperia X from to 2.2.1: about 340 MB

NOTE: The OS download progress indication in Settings > Sailfish OS updates (the "light wave" from left to right across the scenery picture) is very hard to see from 0% to 29%. It then becomes brighter. Please wait patiently.

Release Highlights

This list contains examples of new features (and some bug fixes) added to SailfishOS, compared to the previous release 2.2.0. The release notes of 2.2.0 can be found here: https://together.jolla.com/question/184471/release-notes-220-mouhijoki-released/

Renewed instructions for installing Sailfish OS to Sony Xperia X devices are here - covering Windows, Linux and Mac computers. The same instructions are valid for F5121 and F5122, however, there is a dedicated flashable image for both device models.


  • Updated Android Support of Jolla Tablet from version 1.0.69-1 to 1.0.89-1, including (but not limited to) the following fixes:
  • Memory leak fixed -- Android apps shouldn't run out of memory that often anymore
  • Enhanced window handling and crash dialogs
  • Application scaling in cases where Android runtime is preinstalled to the image
  • User is notified, if an Android application requires newer Android API than currently supported in Sailfish OS
  • Progress and vibration are now honored on Android notifications
  • Solved an issue where certain apps (i.e. Wechat) were unable to record voice messages
  • "Waiting for connection" issue fixed in case of Facebook Messenger
  • Restarting of Android Support fixed
  • Aptoide app icon should now appear in the app grid after installation of it
  • Android apps can recover mobile data connection
  • Camera keeps working now also after using it in some Android apps
  • Android market place installations again in Startup Wizard
  • Fixed the issue of autocaps stop working after typing ca. 100 characters
  • Fixed the issue of installing apps with apkd-install immediately after device boot up
  • Fixed the issue of installing apps with apkd-install immediately after installing Android Support
  • Video files sorted under correct date now, making it easier to find them for sharing
  • Two issues with QQ aopp fixed
  • Some inprovements to show document files (.pdf, .doc, etc.) in Android apps. This may still require using an Android file manager app
  • GPS service for Android apps is more robust now
  • Vibration fixed on Android messaging apps
  • Co-operation of Tracker and Android Support at boot up improved
  • Spotify music stream is now paused on unplugging headphones
  • Android applications on Tablet follow the system language now

    No updates for other devices this time.


  • Jolla account: modified due to GDPR: age of user checked; user is directed to account.jolla.com if account disabled
  • Username is now prefilled when entering to the "Update sign-in credentials"
  • Dropbox: 2.2.0 regression in creating the account fixed
  • Facebook: 2.2.0 regression in creating the account fixed


  • Creating Ambience opens a dialog with explicit save and cancel actions


  • Fixed zoomed images not being reset when exiting camera roll
  • Viewfinder rotation fixed in inverted portrait orientation (tablet)


  • Accepting (or declining) meeting invitations on Exchange accounts now possible. See "Email" below.


  • Alarm routed to loudspeaker now (Jolla1)


  • Optimization to handle a big number of WLAN access points in Settings

CSD (built-in test tool)

  • Gyroscope test result is now shown correctly
  • Hall sensor test failure on Xperia X fixed
  • Headset detection test fixed for T8 and T10 tablets
  • Accelerometer test data is now shown in real-time

Device flashing

  • Flashing script of Sailfish X improved to handle the changed syntax of the new version of fastboot command

Device management

  • Call policy API
  • Fixes to Applications API


  • Support added for RTF text documents
  • Share option added to the main view context menu in Documents app


  • You can now request Read receipts for your the emails you send
  • Exchange ActiveSync invitations can now be accepted or declined by using related buttons in the email message
  • Don't show keyboard until search page is opened
  • Trying to send attachments too large is prevented. A warning will follow
  • Attachment file size is now also shown after download
  • Notification sounds for Exchange ActiveSync emails fixed


  • SIM switch toggle now also available for Dual SIM tablets
  • Now handles opening of BMP pictures


  • Recipient field now updates also on backspace press


  • Label clipping in missed call item menu fixed


  • Improved the way how dbus monitor handles passwords
  • Vulnerabilities fixed: CVE-2018-14526, CVE-2016-5696, CVE-2014-4323 (Jolla1, remote), CVE-2012-0815, CVE-2012-0061, CVE-2012-0060, CVE-2014-8118, CVE-2013-6435 and CVE-2017-10790.


  • End-User License Agreement (EULA) can now be accessed from Settings > About product
  • Mime type is now shown on "Unsupported file" notification


  • VPN connection now stays between connection changes
  • VPN more robust when switchingbetween WLAN and mobile data networks. Automatic reconnection improved.
  • Fixed an issue with DNS requests on a recently added VPN configuration.

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


For detailed changelog, see https://together.jolla.com/question/187243/changelog-221-nurmonjoki/

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 Phone" devices (product name "Jolla" in Settings > About product).

If you have a Sony Xperia X dual SIM device(model F5122) running Sailfish version is, you can download this 2.2.1 update over the air. However, if its OS version is earlier than, then please install the official F5122 image by "flashing" the device - see chapter 6 in https://jolla.com/sailfishxinstall/. You can download this F5122 image from https://shop.jolla.com/downloads/ . Sign in with your Jolla account you used for purchasing the Sailfish X license.

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

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.
  • If you use glibc 2.23, downgrade to glibc 2.19, upgrade to SFOS 2.2.1 and after that, update to glibc 2.23 again

About SD cards

New path to SD card was introduce in Symbolic link /media/sdcard/<uuid>/, actual path /run/media/nemo/<uuid>/
Please read our help article on SD cards supported by Sailfish OS: https://jolla.zendesk.com/hc/en-us/articles/201997993.
Please update your File Browser app to version 1.7.2 or later (Jolla Store).

Known issues

  • The OS download progress indication in Settings > Sailfish OS updates (the "light wave" from left to right across the scenery picture) is very hard to see from 0% to 29%. It then becomes brighter. Please wait patiently.
  • Bluetooth pairing and audio connections may still fail in some circumstances
  • Events View has been reported to remain empty in some cases
  • When using VPN, the icon showing the connection type (WLAN/mobile) at Home screen may sometimes be "mobile" even if WLAN is connected. Toggling the connection should help. To be fixed to OS update.
  • Some Facebook services (syncing FB events to calendar; uploading pictures to FB from gallery) do not work (independent of your OS release) due to some changes at the FB end. We will figure out how to fix this.

Known issues specific to Xperia X

  • There are few observations (being investigated) where mobile data cannot be easily turned on after device restart. In such a case force the device to Flight Mode momentarily and back to normal mode. This will reset the modem.
  • [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
  • 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: https://jolla.zendesk.com/hc/en-us/articles/115004283713
  • Xperia X does not power up when alarm time has elapsed
  • 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)
  • 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: barometer, step counter
  • Issues with video playback and video recording (less than before)
  • FM radio missing
  • Not all SD cards are recognised and mounted (some improvements expected in update)
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-08-23 23:00:24.199417



I get a "Cannot update, try again later" message when trying to install it...

tmy ( 2018-09-04 20:18:27 +0200 )edit

I got the update, it went fine. Downloading was slooow though, took like half an hour.

olli ( 2018-09-04 20:29:09 +0200 )edit

also can.noz update. 4 times now. reboot button does not work. had.to.do a.hardware reset

pawel ( 2018-09-04 22:58:18 +0200 )edit

"Cannot update, try again later" here too :( Maybe it’s because I forgot to uninstall Phonehook and Call recorder ... Reboot button does not work.. @pawel: how did you perform the hard reset? did you lose all your data?

dario ( 2018-09-04 23:33:28 +0200 )edit

I get the same "Cannot update, try again later" message. I tried to update with terminal:

# ssu release
# version --dup
chris_bavaria ( 2018-09-05 00:04:47 +0200 )edit

23 Answers

Sort by » oldest newest most voted

answered 2018-09-06 09:46:32 +0200

Fellfrosch gravatar image

updated 2018-09-06 09:47:35 +0200

Bug: If you want to write a new mail it's hardly possible to hit the + for opening contacts. Also if you first write the subject of the mail, you can't go back in the first line to write the receiver. If you open the extended settings all work like expected.

edit flag offensive delete publish link more



I can confirm this. Hopefully Jolla sees this and fix it in next update.

Jk ( 2018-09-06 13:09:55 +0200 )edit

@Fellfrosch: I can confirm as well. You don't even have to specifically write the subject. It's enough to just leave the to-field. You should open a question for this bug.

Mohjive ( 2018-09-13 14:14:03 +0200 )edit

Same here but typing the name helps. Just type the first letters and the contact will be added.

WT.Sane ( 2018-09-16 22:38:02 +0200 )edit

@Jk created a report for this. I've found the issue and submitted a patch, see answer in @Jk's thread.

Damien Caliste ( 2018-11-28 10:49:55 +0200 )edit

answered 2018-09-05 07:26:51 +0200

kt gravatar image

updated 2018-09-05 09:10:18 +0200

My update failed (Xperia X).

"Sailfish-käyttöjärjestelmää ei voinut päivittää. Yritä uudelleen myöhemmin." "Käynnistä uudelleen"

Restarted and tried again 3 times, does not help.

"Sailfish OS -päivitykset" shows "Päivitys valmis asennettavaksi" (

"Laitteen tiedot", "Koontiversio (Mouhijoki)"

Everything else works OK, just cannot update.

Jolla 1 update succeeded (same account).

edit flag offensive delete publish link more


This worked for me (Sailfish X) after failed update:

  1. backup data,
  2. reset to factory settings (Palauta laite alkutilaan),
  3. restore backup,
  4. update to,
  5. update to

Seems OK now.

kt ( 2018-09-05 19:54:29 +0200 )edit

Interesting, I recall having the above when doing update to

Now, update from to went pretty well; my experiences:

Downloading took something like 3 hours. Don't know exactly as I did other things while it downloaded. At the beginning it was hard to understand that download was progressing. Later It was more obvious (brightness diffence was more visible)

I also let update work "independendently" while doing something else. When I looked the device next time, the progress bar was fully drawn and nothing seemed to happen. As I did not know whether it was still doing something (did not know whether it had just filled up) I let it be on my table while doing something else and hoping it would reboot. After 3 hours I remembered to look again -- Nothing had happeded n the screen, so I manually rebooted (pressed volume up and power button)....

... After that done, device booted up twice and then it was running normally.

The first improvement I saw after trying compass application and it worked. IIRC it did not previously.

Thanks for the update.

too ( 2018-09-05 20:37:56 +0200 )edit

Upgrade hanged for me too. Only error I can see is that re-adding mer-tool repo failed.

Sep 05 00:03:02 Sailfish sailfish-upgrade-ui[703]: Reverting the enabled state of mer-tools to true
Sep 05 00:03:02 Sailfish PackageKit[715]: uid 0 is trying to obtain org.freedesktop.packagekit.system-sources-configure auth (only_trusted:0)
Sep 05 00:03:02 Sailfish PackageKit[715]: uid 0 obtained auth for org.freedesktop.packagekit.system-sources-configure
Sep 05 00:03:03 Sailfish sailfish-upgrade-ui[703]: Distribution upgrade error: [mer-tools|] Repository not found.
Sep 05 00:03:06 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:11 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:16 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:21 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:26 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:31 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
Sep 05 00:03:36 Sailfish mce[3636]: modules/battery-statefs.c: tracker_open(): /run/state/namespaces/Battery/State: open: No such file or directory
teve ( 2018-09-07 14:11:49 +0200 )edit

answered 2018-09-09 02:32:39 +0200

Fuzzillogic gravatar image

updated 2018-09-09 02:55:52 +0200

I had more problems than before updating to this release on my JP1. I do have quite a few packages from OpenRepos installed, and a few patches using PM3. I disabled all third party repos using Storeman, and unapplied all patches before updating. When trying to update, the progress came to a halt immediately with the "the system cannot be updated at this time" or something.

After reboot, I did a version --verify and version --dup. The latter downgraded some apps to version in the official store. I don't think that's a good idea in general..

image description

After this, the system update installed normally, until the very last "pixel", at which point the update stalled. After halve an hour I force rebooted, and the system came up fine.

[root@Sailfish nemo]# version --verify
/usr/bin/version: The '--verify' option has no effect now and will be completely removed in future
[root@Sailfish nemo]# version         
Sailfish OS (Nurmonjoki)
[root@Sailfish nemo]# version --dup
Finished transaction (status=1, runtime=54071ms)
Finished transaction (status=1, runtime=7705ms)

Install (1 packages)
 - sailfish-maps-all-translations-pack;0.5.0-1.4.1;noarch;store

REBOOT NOW unless you need to investigate update
issues or know what you are doing (or both).

All bugs encountered until reboot are features.

In systemupdate.log I found this, which seems to be the last relevant message:

Sep 08 23:47:50 Sailfish sailfish-upgrade-ui[679]: Distribution upgrade error: [mer-tools|] Repository not found.

I don't know what caused the update to stall. I hope the log can provide some insight, to make the update more robust, and to provide the user some clue as to why things aren't working out.

edit flag offensive delete publish link more

answered 2018-09-06 11:34:37 +0200

vlad gravatar image

Again update and still no SIP, no todo's management :-(

edit flag offensive delete publish link more


Did you expect such in a dot-dot release? I don't. SailfishOS 3 is were new features are to be expected.

Fuzzillogic ( 2018-09-07 02:18:08 +0200 )edit

Again update and still same weather. So sad.

WT.Sane ( 2018-09-16 22:40:34 +0200 )edit

answered 2018-09-05 16:27:37 +0200

Jk gravatar image

So is there any improvement about xperia x cpu cores? I checked that Aida64 application shows that sometimes core 5 and 6 running while multitasking. This post not contains any information about this subject. Not even in known issues section says nothing.

If there is not improvememt yet, will sailfish 2.2.2 fix it finally?

edit flag offensive delete publish link more

answered 2018-09-06 17:25:31 +0200

djamigo gravatar image

I do believe the Bluetooth Audio problem has been fixed. It used to stutter if WiFi was active at the same time. I tried it again last night and was able to play stutter-free to a Bluetooth speaker, and even stream audio from Youtube over a wifi data connection.

Many thanks


edit flag offensive delete publish link more

answered 2018-09-06 20:04:18 +0200

ghling gravatar image

Just a short info (unfortunately, I don't have the time for long debugging, but maybe this helps people with the same issue):

My Xperia X froze at the end of the update process. It showed the Sailfish logo with the (fully filled) progress bar, but did not reboot. I also couldn't turn the phone of / reboot it via the power button. I had to do a hard reset (press and hold Volume up + Power) to get the phone working again. But after the boot, everythings seems to be fine (no issues, version --dup finds nothing to update).

edit flag offensive delete publish link more


The same happened to me

carmenfdezb ( 2018-09-06 22:37:29 +0200 )edit

Same here.

ziellos ( 2018-09-07 08:37:20 +0200 )edit

Same here too.

txus ( 2018-09-10 09:48:09 +0200 )edit

And here, but on JP1

Tanghus ( 2018-09-12 14:24:01 +0200 )edit

Same problem : after finishing the update (bar at 100%), instead of rebooting, the Xperia X suddenly shows up as Linux File-CD Gadget (an USB CD-R /dev/sg1 and Flash /dev/sde combo). W.T.F.?!

Manually rebooting (Power + Volume-Up) solves the problem too.

Probably the "reboot" routine on the Qualcom SoC getting stuck at a weird place ?

DrYak ( 2018-09-13 02:41:31 +0200 )edit

answered 2018-09-12 10:32:59 +0200

cnlpete gravatar image

My Xperia told me "the update was not successfull", but was totally unresponsive. There was no way to actually reboot the device, power button also did not work, so i had to do a hard reset (VolUp+Pwr) to turn it of after waiting for approx 30minutes without any change... Now it won't boot at all, but stays in the white sony screen forever.... Does anybody have an idea howto proceed?

edit flag offensive delete publish link more

answered 2018-09-13 13:56:02 +0200

Raymaen gravatar image

Update hangs on the Sailfish logo with filled up progressbar. Here is what helps: wait for minimum 15 min (that shoud be enough to be sure the update is finished) and then pres power button and volume + button do hard restart the device. Afterwords it works normal.

edit flag offensive delete publish link more

answered 2018-09-13 15:28:05 +0200

pichlo gravatar image

Bug report

Sent emails may end up containing multiple "From:" headers.

Steps to reproduce

  1. Start composing a new email but close it (swipe right) half way through to move it to Drafts
  2. Got to Drafts to finish the email
  3. Send it

As long as the recipient's email server is fussy enough (I have only managed to find one so far, Gmail), the email bounces with server complaining that the email is "not RFC compliant" because it contains "multiple From headers".

Here is an example I have reproduced earlier, with personal data anonymized:

From: My Name <my.name@blabla.com>
X-Priority: 3
To: blablabla@gmail.com
From: My Name <my.name@blabla.com>
Subject: Test
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Date: Sun, 9 Sep 2018 05:48:21 +0000
Message-ID: <7jf0ws.perxgm.1hge162-qmf@mail54.blabla.com>
MIME-Version: 1.0


To be fair, I do not know whether this is a regression or it has always been like that. I have saved emails in Drafts before to send them later, but they may not have been to a Gmail address.

edit flag offensive delete publish link more



thats a real bug, you should post it in a dedicated threat...

misc11 ( 2018-09-14 14:48:33 +0200 )edit

As you wish: https://together.jolla.com/question/189572/sent-emails-may-end-up-containing-multiple-from-headers/

Though I do not want to 'threat' anyone :) (A cheap joke, I know. Sorry, I could not resist.)

pichlo ( 2018-09-14 17:26:15 +0200 )edit

Question tools



Asked: 2018-07-13 16:46:28 +0200

Seen: 18,668 times

Last updated: Oct 20 '18