Many thanks to you our active contributors for your feedback and proposals.
Table of content
Table of content
- 2023-02-02: OS version 18.104.22.168 was released to Early Access subscribers as an over-the-air update.
- 2023-02-09: OS version 22.214.171.124 was released to all users as an over-the-air update. Installable images are available in the Jolla Shop
- 2023-02-16: OS version 126.96.36.199 was released to all users as an over-the-air update.
- 2023-03-20: OS version 188.8.131.52 was released to all users as an over-the-air update. Installable images are available in the Jolla Shop
- 2023-07-12: OS version 184.108.40.206 was released to all users as an over-the-air update. Installable images are available in the Jolla Shop .
This release is a stop release .
– Is 220.127.116.11 also a stop release?
– Yes. We have switched the rpm compression from xz to zstd on 4.5.0. In addition, 4.5.0 moves AppSupport to Android 11 API Level. 18.104.22.168 replaces 22.214.171.124 and 126.96.36.199 and 188.8.131.52 as stop releases.
So far, all Sailfish 4 releases have been stop releases. Because of this, if there is a reason to reset an Xperia device, please do not do it with “device reset” but, instead, re-install Sailfish - see the comparison .
Please read about the upgrade of Android AppSupport before you start the OS update. This concerns users updating from 4.4.0 (or earlier) releases only.
Read the new blog about this 4.5.0 OS release, please. It contains not only technical details but also some background for the strange nickname of this release, “Struven ketju”.
The supported Sailfish X devices are listed in this table .
The instructions for installing Sailfish OS to Sony Xperia X, Xperia XA2, Xperia 10, Xperia 10 II (mark 2), and Xperia 10 III (mark 3) devices are here - covering Windows, Linux, and macOS computers.
Read this, please, to learn about the Sailfish X licence.
- Fix Elements and other other Android apps using RealmDB to work inside the container
- Fix Browser crash when using media codecs (video or audio)
- Provide better control over sensor data rate selection
- Fix recurring Calendar event alarms
- Fix tile service urls for QtLocation
- Fix sharing a web site via email
- Fix notification popups not getting stuck when triggering an action
- Add support for array of string-variant key-value pairs to D-Bus QML bindings.
- Cannot run android apps that use realm (e.g. Element) after updating to 4.5
- Sharing a webpage via email
- Calendar alarms don’t work for recurring events since SFOS 4.5.x.x [Solved] - #23 by wetab73
- Improvements situation with Browser crashes on visit to watson.ch/fr website and Browser crashing a lot since update to 4.5 - playing YouTube - #14 by poetaster
The detailed changelog is here .
OS release 4.5.0 contains a major upgrade of the AppSupport, from Android 10 to Android 11. This upgrade brings in modified and relocated app launchers, different access rights for the data directory of the apps, optimized apps, new app icons, and other changes.
When the phone has rebooted at the end of the OS update, AppSupport will start running a migration script transforming the Android apps for Android 11. While the script is running there are no Android app icons on the app grid. This is not a defect.
If there are plenty of Android apps installed on the phone, the migration process may last for several minutes.
NOTE: If you have updated your phone to 184.108.40.206 or 220.127.116.11 or 18.104.22.168 already then the migration has been done previously.
Please wait patiently .
As soon as the new Android icons appear on the app grid, the migration is complete.
Note that it is important to keep the AppSupport installed and enabled over the OS update. Only then can the migration script do its job correctly.
If you have accidentally turned the phone off during the migration, simply turn the phone on again. The migration process should resume automatically.
OS release 4.5.0 is a stop release. This release cannot be skipped over when updating a phone from an earlier release to a more recent one.
Your device must be connected to the Internet and signed into your Jolla account.
Start the update from “Settings > Sailfish OS updates”. Avoid running updates on the command line, please.
We warmly recommend making some 3-4 GB of free space for the internal storage of your device (
/home ) before starting the update. Processing an OS update of almost 1 GB requires a good amount of work area. Move your pictures and videos to the SD card (or to your PC or cloud service).
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. The device screen may blank out during the update process; you may wake the display with a short press of the power key to monitor the progress.
For detailed instructions on updating software, read our help article in Sailfish OS Documentation.
Sailfish OS does not support downgrading. Never try to downgrade the OS as this would break your device.
After downloading an update and selecting “Install” in the pulley menu, the device runs a restart first. You will need to type the security code before the actual installation can start. A horizontal progress bar appears on a black background, under the Sailfish OS logo. As soon as the other end of the bar has been reached the phone will restart automatically. If it doesn’t, please wait for 15 minutes. If it is still stuck at the 100% point of the progress bar it is time to perform forced power off . Next, turn the phone on with the power key and check the OS version at “Settings > About product”.
The Jolla Shop has the images of the latest OS release only. Keep the previously downloaded images stored on your computer if you might want to reflash one of them for some reason later on.
The apps below have been reported to cause problems when installing the previous OS updates. We recommend that you uninstall them before proceeding to the OS update. At least, read the recent comments on those apps.
- GetiPlay has caused problems to some users - see this post .
- If you’ve previously installed the RIME input engine from Open Repos, please remove both that and its version of libyaml-cpp before upgrading, as the latter will cause the upgrade to fail
- If you use Privoxy , be sure to disable it before downloading the update, especially if you have configured the HTTPS-inspection. The latest update is from September. There is no information about compatibility with Sailfish OS. See author’s instructions .
- If you use Aliendalvik Control , see the author’s instructions . It says there “Application has no support for SFOS 4 and later”
- If you use Phonehook be careful. The latest update (32-bit) is from October 2020. The 64-bit version (Xperia 10 II) was published in May 2021.
- If you use OKBoard (a.k.a. Magic Keyboard), update it first to version 0.6.34 which has the fix for the “Installation not complete” error. Also, read the author’s advice , please.
We have relocated the known issues to a table in Sailfish OS documents .
- I had no issues during the upgrade process
- I had small issues but was able to handle them
- I got into serious trouble when upgrading my device (please help!)
The Sailfish OS help articles, previously kept in Zendesk, have been moved to Sailfish OS Documents repository.