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

[Release notes] 1.1.2 / Yliaavanlampi [released]

asked 2015-02-19 12:20:22 +0300

Aard gravatar image

updated 2017-10-02 22:27:37 +0300

olf gravatar image

Update: 03. March, SDK is also available now

Update: We'll roll out to all soon. SDK release will follow soon

This is the early access release of upgrade 11/1.1.2. The current version is, see upgrade version history below. During the next week we will collect feedback, amend this page and fix issues, if necessary, followed by releasing this upgrade to all users.

Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly.

As usual,

  • If your device is running software version lower than and have WareHouse app installed (i.e you are using OpenRepos), disable all openrepo repositories before attempting to upgrade your device.
  • Do not reboot the device while the update is in progress.
  • The 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

Upgrade version history


  • New weather application with events feed integration available through store
  • Browser received a new interface
  • Colours in ambiences can be adjusted
  • Email authentication capabilities can be autodetected
  • Improved low memory handling, now swap is properly taken into accoun

Security fixes

CVE-2013-6393 CVE-2013-6435 CVE-2013-7353 CVE-2013-7354 CVE-2014-2525 CVE-2014-3707 CVE-2014-7824 CVE-2014-8104 CVE-2014-8139 CVE-2014-8140 CVE-2014-8141 CVE-2014-8767 CVE-2014-8768 CVE-2014-8769 CVE-2014-8964 CVE-2014-9112 CVE-2014-9130 CVE-2014-9140 CVE-2014-9293 CVE-2014-9294 CVE-2014-9295

It also contains a fix for an issue in SailfishOS, details will be disclosed after rolling out this update to everyone.

Known issues

OS update process

  • Currently, checks on available disk space happens very late during the OS upgrade process and will fail in the installation phase if the disk space is low. Normally there should be an error note asking you to free some disk space and try again, but in some marginal cases it might not be shown. Should this happen, free some disk space and try to install the OS update again.
  • OS update may fail due to some other reasons too, for example it may have installed some packages from the new release and still have something left from the old. If the device can boot up, you can try to recover by doing the following. If not, you can attempt to recover the device using the recovery mode.
    • Delete the file /home/nemo/.cache/store-client/os-info
    • Stop the store-client process (for e.g. pkill store-client)
    • Reopen Settings app, check for updates again and attempt to install the OS update again
  • We have also noted that if the OS update is attempted while there is long queue of installation of apps from the Store, the system may end up in mixed state (for e.g. select all the apps from startup wizard, and start the system update already while the apps are being installed).
    • In such cases, the OS update appears to be stalled, however it is just waiting for the installations to complete before attempting to upgrade the OS. Just wait patiently, the worst thing to do here is to reboot the device!

Other issues ##

  • Sometimes Messages and Phone app show black active covers.
  • calDAV and cardDAV services are in experimental stage. We have made some improvements with this update, however you may still face issues with certain service providers. Do report it in t.j.c. We'll take a look and try to sort it out.
  • Deleting photo from Camera roll may also delete the previous photo. If camera reel's pulley menu has "Show details" greyed out - means the photo hasn't been indexed yet. Deleting photo in such state will result in previous photo deleted too. If you wait long enough (~10-15seconds) for 'Show details' to become active, only that photo will get deleted when you choose to.

Bugfix and feature highlights


  • Android runtime should not warn on low battery.
  • Can't erase/delete selected text with Backspace.
  • Cleaning of the clipboard crashes Alien Dalvik.
  • Aliendalvik does not detect mobile data being connected anymore (since 5th Dec 2014).
  • Switching between portrait and landscape messes up swipe gestures in Android apps.
  • Alien screen orientation is wrong sometimes.
  • VKB does not work with aliendalvik/android apps but works with native ones.
  • Set oom_score_adj according to process importance if Sailfish hasn't set it.


  • Use ignore_ssl_errors configuration option


  • Download MMS automatically by default
  • Delete attachments from the filesystem


  • Cancel browser requests if useragent has not returned anything
  • Start/stop ntp activity when TimeUpdates property is changed


  • Fix CVE-2014-9112


  • Fix CVE-2014-3707


  • fix CVE-2014-7824


  • Fix opening a day page from dbus invoker.


  • do not allow dhcp-server to change the hostname by default.
  • Enable D-Bus security checking
  • Added color editor and new settings layout.


  • Fixed language selection popup layout.


  • Add 'Ignore SSL errors' option.
  • Add missing version for oauth2 plugin for google.
  • Use QMF auth from capabilities.


  • dim WLAN hotspot when roaming not allowed.


  • Require 500 Mb disk space for installing the update.


  • Turn on heap randomization.


  • Prioritize requests that make app startup more responsive
  • look up address resolve requests in a QHash
  • Schedule resolveAddress immediately


  • Ignore spurious iphb wakeups.


  • Upgrade to 1.5.21
  • Fixes out-of-bounds memory access in png_user_version_check()
  • Fixes overflow in png_combine_row with very wide interlaced images
  • Fixes CVE-2013-7354, CVE-2013-7353


  • Fix bunch of security vulnerabilities
  • Fix CVE-2013-6393
  • Fix CVE-2014-2525: Heap overflow when parsing YAML tags
  • Fix CVE-2014-9130: assert failure when processing wrapped strings
  • Guard against overflows in indent and flow_level


  • Timers for cellular icons.
  • Disable scrolling to launcher area and lock screen shortcut access during boot busy state.
  • Do not show busy-indicator if wlan is off.
  • Don't show launcher until boot sequence has finished and normal app launch speeds can be guaranteed.
  • Detect apps that failed to load.
  • Make sure to show searching & busy when no networks are found.
  • Don't pop up ConnectionSelector more often than once in 10 sec.


  • Don't attempt to connect signal to a NULL HomeApplication
  • Fix crash on close regression


  • Assume proximity covered while waiting for sensord to start up.
  • Allow user processes to query current memory level over D-Bus.
  • More robust low memory signaling
  • Add enablers for evdev event mapping
  • Enablers for TOHKBD and other hw keyboards
  • Allows actions such as automatic DTMF signaling to proceed when outbound call is answered


  • Fix CVE-2014-9295, CVE-2014-9294, CVE-2014-9293


  • Fix CVE-2014-8104


  • Fix CVE-2014-8964.


  • Mask login information in the IMAP login logging.
  • Handle SMTP response 504.
  • Introduce discovery of authentication from the anounced capabilities(IMAP/SMTP)
  • Mask login information in the SMTP debug logging.
  • Update account lastSyncTime when IMAP IDLE disconnects.


  • Fix crash due to floating point precision issues, and update poly2tri to latest upstream.


  • Fix CVE-2013-6435

sailfish-components-contacts-qt ####5

  • Fixed SIM import
  • Fix calendar d-bus call on <10 day/month.
  • Don't make RecentContactsList wait for the contactsModel


  • Add text eliding and text wrap to the details page.
  • fix issue #3: PDFs with mixed orientations not displayed correctly


  • Adjust vm.swappiness to 50.


  • Fix CVE-2014-8767
  • Fix CVE-2014-8768
  • Fix CVE-2014-8769
  • Fix CVE-2014-9140


  • Fix content height of Twitter image sharing.


  • Fix CVE-2014-8139, CVE-2014-8140 and CVE-2014-8141
edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by r0kk3rz
close date 2015-08-26 15:59:47.111998



Sweet! Downloading right now!

nick75 ( 2015-02-19 12:35:26 +0300 )edit

is there a chance to get a "reset color" option to revert manual changes to the ambience main color?

dmnk ( 2015-02-19 12:35:46 +0300 )edit

Downloading now, next step BACKUP then upgrade else ......

WilliePre ( 2015-02-19 13:05:31 +0300 )edit

@dmnk revert option is implemented but didn't make it with this update

sledges ( 2015-02-19 13:14:40 +0300 )edit

downloaded, tried to install (3 times same result)
Sailfish Logo appears, after a few seconds:
update could not be installed, try again later.
(there is enough freespace - btrfs fi show: used 6.13GiB)

rudi ( 2015-02-19 13:26:57 +0300 )edit

41 Answers

Sort by » oldest newest most voted

answered 2015-03-03 23:16:09 +0300

martinrusler gravatar image

Regression: The behavior of introduced in Opt-in upgrade to software version ( https://together.jolla.com/question/59874/release-notes-opt-in-upgrade-to-software-version-11038-uitukka/ ) "Attempting to view events (via swipe-up gesture on the lock screen) while the device is locked now brings up the device lock keypad to allow unlocking the device" is lost in

We are back to the old cumbersome way (when lock-code is active):

  • Double-tap to wake screen.
  • Swipe from below to see notifications
  • When you release finger to tap on a notification, you get directly to the lock-code screen.
  • You enter the lock code
  • Once again have to swipe from below to get to the notification screen
  • Now you can tap on the notification.

Wanted behavior:

  • Double-tap to wake screen
  • Swipe from below to get to notification screen
  • Tap on notification
  • Lock-code screen is presented - enter code
  • Get directly to the notification you pressed.

Please bring this behavior back, or better yet, get rid of the "lock-screen":

edit flag offensive delete publish link more



Yes, that is a little annoying. However, I would like it to go like this instead:

  • Double-tap to wake screen.
  • Swipe from below to see notifications
  • Release finger to get unlock screen
  • Enter lock code, entering notification screen

I'm not sure if seeing the notification screen with device lock code set is a feature or a bug, but I do use it and like it! It's not revealing too much information IMHO, and is really a fast way to check if that SMS you just got is or isn't urgent without reading the whole text.

Direc ( 2015-03-05 19:32:14 +0300 )edit

I think there is a setting for showing text on the notification screen or just the icon. The thing is - if Jolla cares about security and privacy, they will have to make it easy to use features like lock code. I hope this is just a regression, and that it is fixable via a configuration file. Jolla - can you help us out and provide some command line magic? :)

martinrusler ( 2015-03-05 21:28:26 +0300 )edit

Question tools



Asked: 2015-02-19 12:20:22 +0300

Seen: 38,676 times

Last updated: Oct 02 '17