[release notes] 2.0.5 / Haapajoki [released]

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

jovirkku
23703 ●213 ●311 ●247

  moderator

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

lpr
4819 ●186 ●253 ●257

http://www.uni-tuebingen....

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
• Release Highlights
  • Ambiences
  • Backup/Restore
  • Browser
  • Connectivity
  • Developer mode
  • Documents
  • Email
  • Maps/Android
  • Settings
  • USB
  • Vulnerabilities fixed:
• Issues reported by the community at together.jolla.com and fixed in this update
• Changelog
• Updating your device
• Known issues

Upgrade version history

• 2016-11-22: 2.0.5.6 Early access release (not available for Aqua Fish and Turing users yet)
• 2016-11-30: 2.0.5.6 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.

Ambiences

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

Backup/Restore

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

Browser

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

Connectivity

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

Documents

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

Email

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

Maps/Android

• HERE location API: api.nokia.com replaced with api.here.com

Settings

• Allow items in the Transfers list to be individually removed

USB

• 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

• https://together.jolla.com/question/148974/patch-request-sailfish-kernel-and-dirty-cow-cve-2016-5195/
• https://together.jolla.com/question/150594/2054-update-fails-due-to-out-of-space/
• https://together.jolla.com/question/150211/nfs-support-for-intex-aqua-fish/
• https://together.jolla.com/question/147508/lpm-low-power-mode-breaks-lock-homescreen-in-20413/
• https://together.jolla.com/question/145579/backup-fails-due-to-lack-of-space/
• https://together.jolla.com/question/146300/release-notes-204fiskarsinjoki-released/?sort=votes&answer=147221#post-id-147221
• https://together.jolla.com/question/109552/bug-charging-notification-when-full/
• https://together.jolla.com/question/147520/20413-jolla-c-bug-glance-screen-freezes-the-device/
• https://together.jolla.com/question/147360/homescreen-crash-in-20413-jolla-c/
• https://together.jolla.com/question/148846/media-player-will-not-start-after-204-upgrade-if-language-is-norsk-or-dansk/
• https://together.jolla.com/question/138603/wrong-premission-after-sd-card-formated-by-native-storage-app-to-ext4/
• https://together.jolla.com/question/146007/bug-unlock-swipe-left-shows-last-application-not-eventsview/
• https://together.jolla.com/question/148511/unlock-from-lockscreen-can-not-go-to-events-view/
• https://together.jolla.com/question/147883/dead-link-on-where-am-i/
• https://together.jolla.com/question/143912/bug-jolla-c-device-lock-problems-20251/
• https://together.jolla.com/question/146024/bug-device-lock-lock-delay-problem/
• https://together.jolla.com/question/145911/bug-disabled-sim-shows-id-insted-of-operator-name/
• https://together.jolla.com/question/144761/bug-2045-untranslated-string/
• https://together.jolla.com/question/140358/jolla-c-mtp-timestamp-weirdness/
• https://together.jolla.com/question/117031/weather-app-wind-direction/
• https://together.jolla.com/question/85490/weather-app-improvements/
• https://together.jolla.com/question/147124/new-gallery-in-204fiskarsinjoki-ea-crashes-when-trying-to-edit-photos/

Thank you for your valuable contribution!

Changelog

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 2.0.4.14 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 2.0.5.3 to 2.0.5.5 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:

  
  devel-su
  ssu re 2.0.5.6
  pkcon refresh
  pkcon update jolla-settings-sailfishos
  reboot
  

  This issue has been fixed to 2.0.5.6. The fix is in effect when updating your device from 2.0.5.6 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.