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

[release notes] 2.0.5 / Haapajoki [released]

asked 2016-11-01 18:27:14 +0300

jovirkku gravatar image

updated 2018-05-03 23:53:37 +0300

lpr gravatar image

This update, 2.0.5 alias Haapajoki was made to fix a number of vulnerabilities and to upgrade code libraries. It improves robustness and makes a baseline for next releases that bring in significant architectural changes. This release has only few new features, for instance, each tone category has now a choice of several tones, there is the ability to delete incorrect entries in Browser's search history, and zooming range in Documents app has been increased.

Upgrade version history

  • 2016-11-22: Early access release (not available for Aqua Fish and Turing users yet)
  • 2016-11-30: Rolled out to all (not available for Aqua Fish and Turing users)

Release Highlights

This list contains examples of new features (and some bug fixes) added to SailfishOS since the 2.0.4 release.


  • Several tones available for each tone category (ring, alarm, message, etc.)


  • Added a proper indication when memory card cannot be used for backups


  • UserAgentUpdates component added to Browser. This enables User Agent overrides.
  • In addition to QML API, Sailfish.WebView now provides the C++ API, too. This is necessary when setting up the Mozilla Context and Preferences.
  • Added the possibility to delete incorrect instances from the list of history suggestions (e.g. those having typing errors)
  • Aligned tile size based on screen size.
  • Disabled Javascript loading from html email with Gecko based WebView.


  • Default MMS parameters are now configurable per-product.

Developer mode

  • Developer mode now includes libraries needed to debug and profile C++ and QML application code with Sailfish SDK.


  • Stability fixes.
  • Document can be zoomed more due to partial rendering capability - contributed by Damien Caliste among bug fixes.
  • PDF toolbar design changed a bit to allow having annotation actions.


  • Disabled Javascript loading from html email with Gecko based WebView.



  • Allow items in the Transfers list to be individually removed


  • Multiple bug fixes to MTP data transfer

Vulnerabilities fixed:

  • Dirty COW LPE CVE-2016-5195 (kernel)
  • [Jolla C] CVE-2016-2504 (kernel, hw adaptation)
  • CVE-2016-4579, CVE-2016-4574, CVE-2016-4356, CVE-2016-4355, CVE-2016-4354, CVE-2016-4353, CVE-2014-9087 (libksba)
  • CVE-2016-5421, CVE-2016-5420, CVE-2016-5419, CVE-2016-8615, CVE-2016-8616, CVE-2016-8617, CVE-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624 (curl)
  • [Jolla1] CVE-2016-2059 & CVE-2016-2504 kernel, hw adaptation)
  • CVE-2016-6313 (libgcrypt)
  • CVE-2016-4008 (libtasn1)
  • CVE-2015-5479, CVE-2016-3062, CVE-2015-3395 (libav)
  • CVE-2015-3245, CVE-2015-3246, CVE-2012-5630, CVE-2012-5644 (libuser)
  • CVE-2016-5384 (fontconfig)
  • CVE 2016-5696 (kernel) (JollaC and Tablet, jolla1 affected but not fixed yet)
  • CVE-2015-3245, CVE-2015-3246, CVE-2012-5630, CVE-2012-5644 (libuser)
  • CVE-2015-0247 (e2fsprogs)
  • CVE-2015-0571, CVE-2015-0570, CVE-2015-0569 (JollaC wlan)
  • CVE-2015-0247 (e2fsprogs)
  • CVE-2014-8121, CVE-2015-1781, CVE-2015-5277, CVE-2015-8776, CVE-2015-8777, CVE-2015-8778, CVE-2015-8779, CVE-2016-3075 (glibc)
  • CVE-xxx (lzo)

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

Thank you for your valuable contribution!


For detailed changelog, see https://together.jolla.com/question/150236/changelog-205haapajoki/

Updating your device

Your device must be connected to the Internet and signed in to 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:

  • If you use Phonehook from OpenRepos, uninstall it before upgrading.
  • If you use oFono from OpenRepos, revert to the official oFono before upgrading (or else you may face problems with LTE etc.).
  • If you use Patchmanager, revert all applied patches before upgrading.

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 ].

Known issues

  • If you have an OS version earlier than in your device we recommend taking a backup of your data before seeking for OS update. This is because the backup option in the Sailfish OS update dialog tends to stall in some cases with earlier OS versions (after which the device must be rebooted). Backup works okay if initiated from Settings > Backup.
  • This should happen only if you have one of the pre-releases to in your device:
    Sometimes an attempt to update Sailfish OS (in Settings), particularly with Jolla 1 device, may result in an error message "Update requires x MB of free space. Y bytes currently available. Free up space on your device" although there is plenty of space. In this case you should restart your device and try again (which may not always help), or use the following commands in the Terminal (requires the developer mode) after which the menu page "Sailfish OS update" should work correctly:
    ssu re
    pkcon refresh
    pkcon update jolla-settings-sailfishos
    This issue has been fixed to The fix is in effect when updating your device from to the next release.
  • If you have multiple Jolla C devices and backed them up to a cloud service, then in this case it may be difficult to select the wanted backup to be restored. Consider deleting the unwanted backups from the cloud (or moving them to another cloud folder temporarily) and then try again to restore.
  • Very rarely Jolla tablet fails to boot to the home screen after update. Workaround it is to reboot the device.
  • Rarely pulley menu gets stuck on Jolla. Workaround is to swipe sideways to enter the home view, and then go back to app and now the pulley menu should work again.
  • There are a couple of reports where the automatic device lock goes on (time out) too early, e.g. in 20 minutes instead of 30.
  • Reliance Jio SIM cards (India) work in SIM slot #2 only according to some reports. We are not aware of similar issues in other networks.
  • Native Maps application gets uninstalled during the system update and needs to be reinstalled from store afterwards.
  • Automatic screen lock may time out sooner than you have chosen in Settings > Device lock. Furthermore, the timer is not restarted by user actions. To avoid having to type the security code (lock code) too often we recommend setting a longer timeout value for now.
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by olf
close date 2017-10-02 22:06:11.848066



To be corrected: Document entry is partly the one from last update. The mention of zooming in the introduction is also a mistake, if I remember well, this was introduced in 2.0.4.

Maybe, the changelog for Document about the change in toolbar design should mention that annotation actions are for a future release, it's not crystal clear as it is now.

This comment can be safely erased after reading ;)

Damien Caliste ( 2016-11-02 10:54:47 +0300 )edit

@jovirkku early access info? or it is directly downloadable for all.

cemoi71 ( 2016-11-22 12:29:44 +0300 )edit

@cemoi71: Read "Upgrade version history".

Armadillo ( 2016-11-22 12:45:43 +0300 )edit

i really like the links to the tjc threads! makes it easier to close solved issues

misc11 ( 2016-11-22 14:01:47 +0300 )edit .... Updating went very well. Thank you Jolla for good work. Hopefully power consumption would be smaller. Also in flight mode ... I am testin in next days.

N9Sailfish ( 2016-11-23 17:18:15 +0300 )edit

15 Answers

Sort by » oldest newest most voted

answered 2016-11-22 17:42:58 +0300

ArmsOfSorrow gravatar image

This update, 2.0.5 alias Haapajoki was made to fix a number of vulnerabilities and to upgrade code libraries. This improves robustness and makes a baseline for next releases that bring in significant architectural changes.

All in for quality! Damn, I'm looking forward to those changes.

(Does that mean Qt 5.6, newer gstreamer and bluez5? That'd be awesome because I could finally share code between Android/PC and Sailfish for my app.)

Keep it up guys, you're awesome!

edit flag offensive delete publish link more


Seeting Qt 5.6 would mean Bluetooth-MessageAccessProfile (MAP -> SMS/MMS) and Bluetooth-LE and...everything Bluetooth.

hoschi ( 2016-11-23 14:11:10 +0300 )edit

Not necessarily; bluez5 is needed for that. Qt 5.6 and QtBluetooth as a supported harbour API for cross-platform developers would be the next step, though.

ArmsOfSorrow ( 2016-11-24 01:01:43 +0300 )edit

Both Qt5.6 and Bluez5 are in the pipeline...

jovirkku ( 2016-11-24 11:57:16 +0300 )edit

answered 2016-11-22 14:24:05 +0300

Alex gravatar image

updated 2016-11-27 21:48:05 +0300


Maps (from Jolla) will be uninstalled automatically on upgrading to - happened on my Jolla Tablet and Jolla 1.


Also the MeeRun app from OpenRepos got uninstalled: Separate question.

edit flag offensive delete publish link more


Are you able to install Here from Jolla Store?

magullo ( 2016-11-22 14:31:35 +0300 )edit

Are you talking about the Android Here Maps App (Here Wego)?

I am able to install the native Jolla Maps again without problems but the Andorid Here Maps are still not shown in the Jolla Store for my Jolla 1 Phone.

Alex ( 2016-11-22 14:35:45 +0300 )edit

Added this to the known issues. Unfortunately we cannot do anything about it at the moment.

Keto ( 2016-11-22 14:41:50 +0300 )edit

Wasn't the native sailfish maps removed from the store last time around?

coley ( 2016-11-22 15:05:02 +0300 )edit

Maps is still installed on my phone. Did an upgrade from 2.0.4 on my Jolla phone. So it seem it doesn't affect all users.

mdosch ( 2016-11-22 15:52:57 +0300 )edit

answered 2016-11-24 00:27:03 +0300

DarkWhite gravatar image

updated 2016-12-08 20:56:08 +0300

I updated my Jolla 1 to Haapajoki early access and I have found a jolla-camera focus binding loop bug. I can take only 1 image and after it the shutter icon or corresponding volume button stops working.

Expected: Take series of pictures. What happens instead: You can take only a single picture and have to close app. Steps to reproduce the spotted behavior on Jolla 1:

  1. -Step 1: Ensure your camera save path is to memory card
  2. -Step 2: Launch camera from app launcher page
  3. -Step 3: Do not change nor touch any settings and be sure you have before step 2 reseted to default image settings
  4. -Step 4: Take a picture with screen button or volume key (does not matter)
  5. -Step 5: Camera focus is now in loop and you can not take a second picture and you have to restart camera app to do so.

But it gets even fuzzier when you start to changing camera settings from the settings app -> camera. Changing from there save location (eMMC/SD) and image quality (8MP/6MP) can sometimes lock the active camera focus finder (square) and forbid you taking the first picture. Plus these variables produce different debug trace file than I have writed below.

However a workaroud is to change camera focus setting in Step 3 and camera will continue to work as expected.

Here is the step-by-step jolla-camera app debug trace code:

[D] QWaylandEglClientBufferIntegration::QWaylandEglClientBufferIntegration:62 - Using Wayland-EGL 
[D] QGstreamerVideoWindow::QGstreamerVideoWindow:72 - No m_videoSink available! 
[W] unknown:17 - file:///usr/share/jolla-camera/pages/capture/CaptureOverlay.qml:17:1: QML CaptureOverlay: Binding loop detected for property "_startTime"
[D] QGstreamerVideoWindow::QGstreamerVideoWindow:72 - No m_videoSink available! 
[W] unknown:315 - file:///usr/share/jolla-camera/pages/capture/CaptureView.qml:315: TypeError: Cannot call method 'appendCapture' of undefined
[W] unknown:121 - file:///usr/share/jolla-camera/pages/CameraPage.qml:121:13: QML CaptureView: Binding loop detected for property "_stillFocus"

Vote up and comment if you can somewhat reproduce this.

edit flag offensive delete publish link more


What do you mean with 'camera focus is in loop'?

I am unable to reproduce your issue.

Alex ( 2016-11-24 11:39:09 +0300 )edit

Me neither, I only noticed a warning sign beside focus square.

magullo ( 2016-11-24 11:46:17 +0300 )edit

Your post didn't get lost, it's just above: https://together.jolla.com/question/150237/release-notes-205haapajoki/?answer=152020#post-id-152020

Sthocs ( 2016-11-24 15:33:54 +0300 )edit

I tried your steps to reproduce, but was not able to. Sorry! Actually not sorry at all that my camera works as it should, but sorry it doesn't work for you.

Kjetil Kilhavn ( 2016-11-25 01:04:19 +0300 )edit

Now I can confirm that this is issue exists, since I just experienced it on my Jolla 1 Phone. It is not reproducable with the listed steps above but it occurs randomly.

I copied the journalctl and dmesg logs while this bug occured, if someone is interested.

Alex ( 2016-11-27 21:24:45 +0300 )edit

answered 2016-11-22 19:46:37 +0300

Schturman gravatar image

updated 2016-11-22 19:47:01 +0300

Guys, can someone explain me what the problem ?
EA activated on my account, but all my 3 devices (tablet/jolla1/jollaC) still don't see this update :/
Already tried:
* pkcon refresh
* reboot
But Jolla Settings still show me up to date for Someone know what the problem ?

P.S. Yes I know that I can update via version --dup, but it not a question...

edit flag offensive delete publish link more


@schturman try to reinstall jolla-settings-sailfishos

pkcon refresh
pkcon update jolla-settings-sailfishos
atlochowski ( 2016-11-22 20:08:47 +0300 )edit

I unapplied all patches first and reinstalled:


Now lipstick restart = still up to date with, reboot = still up to date with
Any other suggestions ?

Schturman ( 2016-11-22 21:32:18 +0300 )edit

Which version of jolla-settings-sailfishos do you have? This ?

atlochowski ( 2016-11-22 22:40:45 +0300 )edit

I have updated to by choosing the version and I got now the message that a system update is available with version on my intex phone. gg

megalith ( 2016-11-22 22:44:19 +0300 )edit

@megalith it's normal if you force update from terminal and there is no official update (or your phone can't see it) for your phone, system want downgrade your system.

atlochowski ( 2016-11-22 22:55:35 +0300 )edit

answered 2016-11-22 18:58:15 +0300

itdoesntmatt gravatar image

image description

from command 37 to 42. for me worked...i used to have it already installed but disappeared after updat

edit flag offensive delete publish link more



Who need sailfish maps, after first boot, run:

pkcon refresh
pkcon install sailfish-maps

the package "qt5-plugin-geoservices-nokia" changed to "qt5-plugin-geoservices-here" and sailfish-maps need it... sailfish-maps installed without any problem on all 3 devices...

Schturman ( 2016-11-23 12:21:31 +0300 )edit

Thank you; it worked for me too! I'm trying to avoid using Android apps and Sailfish Maps is good enough for me... I got worried that this update was the end of sailfish maps but it wasn't! :)

goldenm ( 2016-11-25 00:22:31 +0300 )edit

answered 2016-11-26 13:53:00 +0300

p_pahare gravatar image

updated 2016-11-26 13:54:33 +0300

Jio network (India) is working in SIM Slot 1 of Aqua Fish , Untill Fiskarsinjoki Update Its 4G Data Connection was Refreshing Many times in Slot1 but After Updating to HaapaJoki EA this Issue is Resolved

edit flag offensive delete publish link more


Aren't you getting network denied? Edit: Ok, so I got network. but cannot enable jio net. It says problem with connection

Mystel ( 2016-11-27 16:47:12 +0300 )edit

I Dont Know If problem is with your Device, But It should work after APN settings are fed correctly

p_pahare ( 2016-11-29 13:51:19 +0300 )edit

Tell me plzzz wht you wrote in APN....Coz it isn't working

Nitesh ( 2017-01-25 16:05:39 +0300 )edit

answered 2016-11-22 16:58:03 +0300

pawel gravatar image

updated 2016-11-22 20:37:03 +0300

can not install update on Aquafish. did try it twice. always got the message that installation failed. press ok to reboot

update: it failed twice, then i did turn on dev mode and tried again: sucess other then that: the first two times i did download using mobile data, the last time with wifi

edit flag offensive delete publish link more



I installed it without any problem on my aquafish (on which there are no intex packages neither intex repository)

scegliau ( 2016-11-22 17:11:19 +0300 )edit

@pawel same here w/ a Jolla C.

sidv ( 2016-11-22 18:46:33 +0300 )edit

Got the update on the Intex working fine appart from the maps issue.

megalith ( 2016-11-22 19:23:27 +0300 )edit

I still can't. With version --dup too. Only upgrade packages, not version.

DimaAsket ( 2016-11-24 13:02:46 +0300 )edit

answered 2016-11-25 11:18:51 +0300

mikelima gravatar image

Since the update, I can receive calls, but not call my contacts anymore. I get a problem with network message and a disconnected tone. Internet works, but the wireless router functionality does not.

edit flag offensive delete publish link more

answered 2016-11-25 19:09:13 +0300

treeman gravatar image

Since the update the native Browser doesn't load anymore. I checked this on two Jolla 1. On pressing the browser Icon the moving Circle is shown on the homescreen tile but after some seconds the tile dissapears and nothing happens. Does Anyone else have the problem?

edit flag offensive delete publish link more


browser switch to a christmas tree while visiting a specific french website to check tracking package : https://m.mondialrelay.fr/

clovis86 ( 2016-11-26 01:25:15 +0300 )edit

problem solved with doing: version --dup in terminal. Native browser now does it right again.

treeman ( 2016-12-07 16:24:58 +0300 )edit

answered 2016-12-01 11:54:37 +0300

ds2k5 gravatar image

Hello, mail app bug "empty mail" is still include. https://together.jolla.com/question/53709/bug-unable-to-open-an-empty-e-mail-with-an-attachment/ https://together.jolla.com/question/149987/jolla-mail-app-error-if-only-attachmend/ Please add to fixlist Thanks

edit flag offensive delete publish link more

Question tools



Asked: 2016-11-01 18:27:14 +0300

Seen: 26,238 times

Last updated: May 03 '18