asked 2015-07-15 13:43:48 +0200

Aard
13973 ●68 ●61 ●55

http://bwachter.lart.info...

updated 2017-10-02 22:22:00 +0200

olf
10393 ●104 ●201 ●158

Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.

In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.

If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.

As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.

Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly.

As usual,

• If you use phonehook from OpenRepos, uninstall it before upgrading
• If you use patchmanager, revert all applied patches before upgrading
• 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
• Highlights
  • Security fixes
  • Known issues
• OS update process
  • Other issues
  • Changelog

Upgrade version history

• 1.1.7.24 (15.7.2015): Initial early access release
• 1.1.7.25 (27.7.2015): Fix an issue in package management middleware
• 1.1.7.27 (13.8.2015): Fix a reboot issue when using hotspot with GPS and an icon scaling issue for favourite settings
• 1.1.7.28 (27.8.2015): Fixes issues youtube video playback in native browser, adds a feature to enable persistent logging during the upgrade process and fixes MER #1208.
• 1.1.7.28 (31.8.2015): Roll-out to all users

Highlights

• New gcc 4.8 based tool chain is used on SailfishOS platform from this release onwards, bringing C++11, among other things
• Alien Dalvik (Android support)
  • Added 'Android Support' settings to Settings > System > in the 'Info' section
    • Option to prevent Android apps from accessing your contacts
    • Option to Stop/Start Android support
  • Added a settings page for Android applications in Settings > App from where you can control how the installed application works on your Jolla device (Force stop, Clear cache, Clear data, and running the app on background)
  • Having the option to run Android applications on background enables receiving notifications for Android messaging apps even when the app is closed.
  • Better WLAN connection handling for Android apps
• Introduce certificate handling middleware (p11-kit). All crypto libraries now share one CA store.
• Update to PulseAudio 6.0, improving Bluetooth audio
• Possibility to choose different keyboard layouts for Bluetooth keyboards if paired with one for different languages via Settings > System > Text input > Active layout

Security fixes

CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153

Known issues

OS update process

• OS update may remain at about 95% for a long time. If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade went through.
• If you have phonehook from OpenRepos installed uninstall it before upgrading.
• 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

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

Changelog

The full changelog is available in a separate post