[Release notes] Sauna

Many thanks to you our active contributors for your feedback and proposals.

Version history of the OS release

  • 2024-05-20: OS version was released to Early Access subscribers as an over-the-air update.
  • 2024-06-06: OS version was released to Early Access subscribers as an over-the-air update. See the release notes of

Stop release

It is not yet clear if 4.6.0 needs to be a Stop release. We will communicate that later.

Device models supported by Sailfish X

The supported Sailfish X devices are listed in this table .

This is the last release for the following products: Jolla Tablet, Jolla C, Xperia X and, Gemini PDA.

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.
The instructions for Xperia 10 IV and Xperia 10 V will appear in the same place soon.

This document explains what the Sailfish X licence is.

Release highlights

The list below contains bug fixes added to Sailfish OS, compared to the previous public release All Sailfish OS release notes can be found here .


  • VK removed from “Settings > Accounts”


  • Android application runtime permission queries use native Sailfish OS dialogues
  • Improved access control in AppSupport D-Bus interfaces.
  • Updated to android-security-11.0.0_r74 security patch level
  • Sharing a screenshot from the Gallery to Android apps is fixed
  • Several fixes to ensure that AppSupport starts when it should
  • AppSupport restarts also after a long uptime (of the phone)
  • Scrolling in Firefox (and in some other apps relying on timestamps) is smoother
  • Ensured that AppSupport starts automatically after a bootup if so required
  • Support of 1.4 and 1.5 IRadio interfaces added to make AppSupport compatible with 5G
  • Quick reply from notifications supported


  • When charging is completed the screen is no longer turned on


  • Bluetooth network sharing (tethering) was added to Sailfish. It is the server functionality - a Sailfish device offers Bluetooth tethering for another device. The two devices shall be connected with Bluetooth and “Settings > Internet sharing > Bluetooth network sharing” enabled on the server. Both WLAN and mobile data connections can be shared, depending on which is connected to the Internet. This feature must be enabled per device and is currently available on XA2 and newer Sony devices. The transfer speed over the Bluetooth link may be slow, often just hundreds of kilobits per second. It’s intended for low bandwidth requirements as a passive tethering, i.e. you don’t have to remember to turn it on and off. Streaming radio and accessing traffic info in a car are typical use cases.


  • Several bug fixes, many of them from Damien Caliste. Thank you!
  • Support for searching calendar events. Also, return the next coming-up occurrence on event search results
  • With a recurring event, support removing “this and later events”
  • Separate organizer and attendee information allowed. An organizer does not need to be an attendee.
  • Tapping location information in a calendar event causes a list of installed map apps to appear. Select one to see the position on the map
  • When importing an ICS file, it is now possible to select the calendar into which to import the event
  • Event times are updated on time zone changes
  • Clock time-based reminders are used for all-day events (to avoid e.g. midnight alerts)
  • Deleted calendars are no longer shown or synced. They do not appear in “Manage calendars”, either.
  • Google calendars with read-only access (e.g., shared calendars) are now shown in the calendar application


  • The assistant button on the side of Xperia 10 III is set to launch the camera and take a picture (if the camera is open)
  • Reading inverted QR codes (white pattern on black background) fixed


  • Sailfish OS supports 5G mobile networks on Xperia 10 III phones (and newer models when available). This requires a 5G SIM & contract on the phone, of course, and to enable “Settings > Mobile network > Network mode > Prefer 5G”. VoNR or ‘Voice over New Radio’ is not yet supported. Hence voice calls from/to a phone connected to the 5G network will be routed via VoLTE, i.e. the phone is switched to a 4G network for the duration of phone calls.
  • Improved CLAT support and increased CLAT reliability with dual-IP support
  • WLAN regulatory domain (i.e. country-specific WLAN channel rules) fixed to follow the user or automatically set the timezone correctly. Also, the proper regulatory domain for WLAN is enabled in the correct order at bootup. The regulatory domain should be accurate on 4.6.0, whether there is a SIM card or not in the phone.
  • Some fixes for the issue of WLAN getting stuck in the “Connecting…” state
  • Improved online check to ensure it is always done, using the correct interface. Online check functionality was brought closer to upstream.
  • Improved route management in ConnMan to avoid premature removal of DNS routes.
  • Some modem configurations added for Xperia 10 II, proposed by the community

Device lock & display blanking

  • Automatic locking: the options have been revisited in “Settings > System > Device lock”
  • 60 minutes option was added to display blanking (“Settings > System > Display”)
  • The lock icon at the Top Menu is fixed to lock up the device immediately
  • Extra delays in display blanking eliminated


  • Improvements related to the display notch and rounded corners


  • The replied and forwarded status of messages is indicated with a tiny arrow just under the time stamp of a message in the message listing
  • The encryption status of an IMAP message is indicated with a lock icon just under the time stamp of a message in the message listing
  • Added ‘Reply’ actions to notifications (shown in the Events view) to allow quick replies to email messages without opening the app.
  • Deletion of email attachments is handled correctly
  • Attachment sizes indicated correctly
  • Set the response type (reply, reply all, forward) to the original message on send
  • Better cover graphics with light ambience


  • Fixed to save video timestamp when Gallery minimized
  • Fixed context menu in the last row
  • Photo exposure time is shown as a fraction of a second (in the common way)
  • Image format handling registered only for supported types


  • Scalable 3rd party icons and graphical assets are supported. The image provider is a public component that an app developer can instantiate.


  • Apps are no longer coupled with the setting “Touch screen vibration”. Hence they can vibrate also when that setting is OFF. A separate feedback event was added for non-touch usage.


  • Qt.labs.folderlistmodel allowed in Harbour rules
  • RPM validator checks not only the dependency types obsoletes and requires but also conflicts, provides, recommends, suggests, supplements or enhances

Home screen

  • When charging is completed the screen is no longer turned on
  • Added indicators to show the areas of application close gesture. Two short vertical lines appear near the top corners and a close icon appears on the app icon. These indicators do not show up if one pulls down from the middle of the top edge.
  • The mouse cursor is shown when such a device is connected
  • Basic home screen support for devices with a display notch implemented

HW Adaptation

  • All Sony adaptations have the suffix ‘(AOSP)’ on their model names, which comes from Sony sources to indicate that the device is running AOSP. Our devices aren’t, and this suffix is misleading, so it was removed.
  • The root partition size on Xperia X, Xperia XA2, Xperia 10 and, Gemini PDA was increased to 4 GB. The newer devices have it already. You can obtain the bigger root partition only by flashing SailfishOS ≥ 4.6.0. If one upgrades to SailfishOS ≥ 4.6.0 over-the-air the root partition size will not be altered.

Location & Maps

  • Changed the way offline data is stored and handled.
  • Tapping location information in a calendar event causes a list of installed map apps to appear. Select one to see the position on the map
  • MLS data updated to the level of 2024-03-15


  • Fixed handling album names with slash characters
  • Android players can indicate over MPRIS if shuffle and repeat are supported
  • Album art embedded in OGG Vorbis files is supported
  • Artists page using album artist information if available
  • Show a busy state while content is fetched


  • Added ‘Reply’ actions to notifications (shown in the Events view) to allow quick replies to text messages without opening the app.


  • GCC compiler updated from version 8 to 10 (arm 10.3-2021.07)
  • Rust updated to version 1.75.0


  • Support for text drawing in ffmpeg added, making subtitles and text animation possible
  • Multiplier of MPRIS seek methods fixed (µs instead of ms). This bug shortened the seeks to a fraction

Notifications & Events view

  • Resident property for notifications is supported. This prevents notifications from closing automatically when an action is triggered.
  • LED notification about missed calls does not anymore turn off on consecutive missed calls
  • ‘Reply’ action added to the Events view. It invokes a text field for easily replying to a text message, for example.


  • Storing PDF passwords is supported in the Documents app

Sailfish middleware

  • 120+ open source packages updated


Vulnerabilities fixed:

  • aspell v. CVE-2019-17544, CVE-2019-20433, CVE-2019-25051
  • binutils v. 2.41 and profile v. 1.4.0: about 240 CVEs
  • bluez5 v. 5.72: CVE-2023-45866
  • busybox v. 1.36.1: CVE-2022-28391
  • byacc v. 2.0.20230521: CVE-2021-33641, CVE-2021-33642
  • c-ares v. 1.23.0: CVE-2022-4904, CVE-2023-31124, CVE-2023-31130, CVE-2023-31147, CVE-2023-32067
  • connman patch v. 1.32+git207: CVE-2017-12865, CVE-2021-26675, CVE-2021-26676, CVE-2022-23096, CVE-2022-23097, CVE-2022-23098, CVE-2022-32292, CVE-2022-32293, CVE-2023-28488
  • cups v. 2.4.7: CVE-2023-32324, CVE-2023-34241, CVE-2023-4504
  • curl v. 7.87.0: CVE-2022-42915, CVE-2022-42916
  • curl v. 8.4.0: CVE-2023-38546, CVE-2023-38545, CVE-2023-38039, CVE-2023-28322, CVE-2023-28321, CVE-2023-28320, CVE-2023-28319, CVE-2023-27538, CVE-2023-27536, CVE-2023-27535, CVE-2023-27534, CVE-2023-27533
  • e2fsprogs v. 1.47.0: CVE-2022-1304
  • elfutils v. 0.190: CVE-2020-21047
  • expat 2.6.1: CVE-2022-25313, CVE-2022-25314, CVE-2022-25315, CVE-2022-25235, CVE-2022-25236, CVE-2022-40674, CVE-2022-43680, CVE-2023-52425, CVE-2023-52426
  • ffmpeg v. 5.1.3: CVE-2023-37327, CVE-2023-37329
  • firejail v. 0.9.72: CVE-2022-31214
  • freetype v. 2.12.1: CVE-2022-27404, CVE-2022-27405, CVE-2022-27406
  • fribidi v. 1.0.12: CVE-2022-25308, CVE-2022-25309, CVE-2022-25310
  • gdb v. 12.1.0: CVE-2019-1010180
  • gdk-pixbuf v. 2.42.10: CVE-2021-46829
  • giflib v. 5.2.2: CVE-2022-28506, CVE-2021-40633, CVE-2023-39742 and CVE-2023-48161
  • git v. 2.43.0: CVE-2022-23521, CVE-2022-41903, CVE-2022-24975, CVE-2023-22490, CVE-2023-23946, CVE-2023-25652, CVE-2023-29007
  • glib2 v. 2.7.84: CVE-2023-29499, CVE-2023-32611, CVE-2023-32636, CVE-2023-32643, CVE-2023-32665
  • gmp v. 6.3.0: CVE-2021-43618
  • gstreamer1.0* v. 1.22.4: CVE-2023-37327, CVE-2023-37329
  • less v. 649: CVE-2022-46663
  • libarchive v. 3.7.2: CVE-2021-36976, CVE-2023-30571
  • libcap v. 2.69: CVE-2023-2603
  • libid3tag v. 0.16.2: CVE-2017-11550
  • libksba v. 1.6.3: CVE-2022-47629, CVE-2022-3515
  • libsndfile v. 1.2.2: CVE-2022-33065
  • libtasn1 v. 4.19.0: CVE-2021-46848
  • libtiff v. 4.6.0: CVE-2022-3970, CVE-2022-0908, CVE-2022-1354, CVE-2022-1355, CVE-2022-2953, CVE-2022-3597, CVE-2022-3598, CVE-2022-3599, CVE-2022-3626, CVE-2022-3627, CVE-2022-2869, CVE-2022-2868, CVE-2022-2867, CVE-2022-0561, CVE-2022-0891, CVE-2022-3570, CVE-2022-0562, CVE-2022-0865, CVE-2022-0907, CVE-2022-0909, CVE-2022-0924, CVE-2022-1056, CVE-2022-1210, CVE-2022-1622, CVE-2022-1623, CVE-2022-22844, CVE-2022-48281, CVE-2023-26965, CVE-2023-2908, CVE-2023-3576, CVE-2023-3618, CVE-2023-3316, CVE-2023-25433, CVE-2023-25434, CVE-2023-25435, CVE-2023-26966, CVE-2023-40745, CVE-2023-41175, CVE-2023-1916, CVE-2023-6277
  • libvncserver v. 0.9.14: CVE-2016-9941, CVE-2016-9942, CVE-2018-7225, CVE-2018-15127, CVE-2018-15126, CVE-2018-15127, CVE-2018-20019, CVE-2018-20020, CVE-2018-20021, CVE-2018-20022, CVE-2018-20023, CVE-2018-20024, CVE-2018-20748, CVE-2018-20749, CVE-2018-6307, CVE-2019-20788, CVE-2018-21247, CVE-2019-15681, CVE-2019-20839, CVE-2019-20840, CVE-2020-14396, CVE-2020-14397, CVE-2020-14398, CVE-2020-14402, CVE-2020-14403, CVE-2020-14404, CVE-2020-14405, CVE-2020-14399, CVE-2020-14400, CVE-2020-14401, CVE-2017-18922
  • libvpx v. 1.13.1: VE-2023-5217, CVE-2023-44488
  • libwebp v. 1.3.2: CVE-2023-1999, CVE-2023-4863
  • libxml2 v. 2.12.3: CVE-2022-23308, CVE-2022-29824, CVE-2022-2309 CVE-2022-40303, CVE-2022-40304, CVE-2023-29469, CVE-2023-28484
  • libyaml v. 0.2.5: CVE-2014-2525
  • lua v. 36.2.1: CVE-2020-15888,CVE-2020-15945,CVE-2021-43519,CVE-2019-6706
  • lxc v. 5.0.2: CVE-2022-47952
  • nghttp2 v. 1.58.0: CVE-2023-35945, CVE-2023-44487
  • ofono v. 1.29: CVE-2023-4233, CVE-2023-4234
  • openssh v. 9.6p1: CVE-2021-36368, CVE-2023-38408, CVE-2023-48795, CVE-2023-51384, CVE-2023-51385
  • openssl v. 1.1.1v: CVE-2022-4304, CVE-2022-4450, CVE-2023-0215, CVE-2023-0286, CVE-2023-0464, CVE-2023-0465, CVE-2023-0466, CVE-2023-2650, CVE-2023-3446, CVE-2023-3817
  • openVPN v. 2.5.8: CVE-2022-0547
  • pixmap v. 0.42.2: CVE-2022-44638
  • rsync v. 3.2.7: CVE-2022-29154
  • rust v. 1.61.0: CVE-2021-29922, CVE-2022-21658
  • screen v. 4.9.1: CVE-2023-24626
  • sofia-sip v. 1.13.11: CVE-2022-31001, CVE-2022-31002, CVE-2022-31003
  • sqlite v.3.40.1: CVE-2022-35737
  • sudo v.1.9.15p4: CVE-2022-43995, CVE-2023-22809, CVE-2023-28486, CVE-2023-28487, CVE-2023-27320
  • tcpdump v. 4.99.4: CVE-2017-16808, CVE-2018-14468, CVE-2018-14469, CVE-2018-14470, CVE-2018-14466, CVE-2018-14461, CVE-2018-14462, CVE-2018-14465, CVE-2018-14881, CVE-2018-14464, CVE-2018-14463, CVE-2018-14467, CVE-2018-10103, CVE-2018-10105, CVE-2018-14880, CVE-2018-16451, CVE-2018-14882, CVE-2018-16227, CVE-2018-16229, CVE-2018-16230, CVE-2018-16452, CVE-2018-16300, CVE-2018-16228, CVE-2019-15166, CVE-2019-15167, CVE-2018-14879, CVE-2018-16301, CVE-2023-1801, CVE-2023-45322
  • vim v. 9.0.2167: about 140 CVEs
  • xdg-utils v. 1.2.1: CVE-2020-27748, CVE-2022-4055
  • zlib v. 1.3: CVE-2023-45853


  • Utilities: “more info” links changed to point to relevant documents in docs.sailfishos.org
  • Utilities: vertical scroll bar added
  • The licensed services can be checked at “Settings > Accounts > Jolla > My Add-Ons”. This item also serves the purpose of checking if there is a valid Sailfish OS licence on this device for the signed-in Jolla user.
  • An extra ‘Do Not Disturb’ button removed from the Top menu

Startup wizard

  • Added support for customizable startup wizard logo


  • Support for android.hardware.radio@1.5::IRadio was added. The 5G needs this.
  • Support for 5G in oFono was added
  • Support for 5G in AppSupport


  • VPN support for CLAT added
  • Starting the VPN does not clear the contextkit key values any more. An improved method to keep the apps (and upper layers) aware of the service status was developed.
  • OpenVPN was updated to 2.6.9 introducing stricter cipher settings. Settings of OpenVPN now include “Ciphers”, “Ciphers list” and “Fallback Ciphers”. The “Ciphers list” is the list of the supported ciphers to be used in negotiations with the server — access the OpenVPN manual/website for further info or overview this cipher negotiation info.
  • OpenConnect was updated to version 9.
  • Fixed issues on VPN services or VPN settings not being saved on some devices.
  • Importing VPN configuration files made more robust


  • Uninstalling the Weather app at the app grid is fixed
  • The Weather app is hidden from the Events view


  • Fullscreen notification shown for incoming calls, also when the phone is locked (this requires that “Allow background services to start on bootup” be enabled in “Settings > Apps > WhatsApp”).

Sailfish OS Forum: issues reported by the community fixed in this update

Technical changes

The detailed changelog is here.

Sailfish-default icons are moved from

There’s now an image provider component in Silica which can be registered with custom paths. Apps don’t need to put their things in the global directory.

Updating your device

By installing this update you accept the updated The Sailfish OS End User License Agreement.

The usual update process

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 your PC or cloud service).

This is the usual drill before attempting to update your devices:

Back up your data before an attempt to update your device and save the backup to an SD card or 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 get blank 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. When 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 ones stored on your computer if you should want to reflash one of them later on.

Notification concerning apps from Open Repos

  • Compatibility with the release 4.6.0 has not been verified yet. Early Access users, please report

Some apps from Open Repos have been reported to cause problems when installing OS updates. Read the recent comments on those apps.

  • Call recorder has caused serious problems. We recommend uninstalling that app before the OS update. Read this comment, please.

Known issues

We have relocated the known issues to a table in Sailfish OS documents .

How did the upgrade go?

  • 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!)
  • I did not dare or want to update

0 voters

Help articles

The Sailfish OS help articles, previously kept in Zendesk, have been moved to Sailfish OS Documents repository.


Switched to Calyxos for daily driver. Sorry, solving features by removing them (weather)…
What about supporting state of the art wireguard out of the box?
Oom Killer solved?

But it will get better, with AI…


Jolla tablet update - the progress bar never showed up, but update succeeded, so if you get black screen after jolla logo, leave it be for 15mins or so

Upgrade went flawlessly. Thanks.


XIII - ignored the advice to uninstall angelfish and osm scout server (and a bunch op-kf5…), update failed halfway through, with ‘unable to update at this point’, reboot, now boots to a flashing white background with msg No apps running… Bricked it seems :confused:


I appreciate this change. Having to start it each time there is a device restart is not great.

1 Like

Alright guys and gals ping me here when you notice my app is broken lol

I doubt none of my apps will break


Xperia 10 II with was successfully updated to 4.6.

Android AppSupport managed to start only on the second attempt after the update, though.

YAY! 5G! cant wait to install it (although i have to wait until work is over…)


Updating my Xperia 10 ii for testing purposes went well, however OSM Scout Server got uninstalled. When trying to re-installing it I get an error message regarding missing libicui18n.so.68.


uh, i cant download the new image for 10III from shop.jolla.com.
i only get for previous releases, it was available when i saw the relnotes thread

1 Like

Looks like the file server is down, as I am not able to initiate a download from my phone.

Is larger root partition requirement for installation on older devices (XA2)?

Anyway, maybe, in next update it will be good to think about reverting back some suggestions from former russian partner. For example: return old incomming screen.


Good to have 5G on 10III, but are there any VoLTE improvements?

Anyone already upgraded could try if sending SMS with VoLTE enabled works for affected providers?

I couldn’t see any mentions besides renaming the option and adding ‘patterns’ for 10IV/V…

1 Like

Do I need to reflash Xperia XA2 even if I already have 7,7 GB in system partition?

No. The logical implication of the release notes that only if you want the larger root partition, the reflash is needed. In all other cases, no reflash needed.


Yeah. It has been like this for quite some time. Sorry for that.

We publish the flashable images only after rolling out the release to all users. This is just the Early Access step.

No, it is not. Flashing 4.6.0 (to get the larger root partition) would help in the future.


Jolla knows why: Bluetooth obex push is using chunks of 666bytes while N9 is using 32K

Please fix your old bugs faster than introducing new ones.
@Jolla, i.e. please change your policy on this, otherwise SailfishOS will behave like an “early beta version” forever. Actually the late SailfishOS 2 releases (e.g. 2.2.1) were clearly less buggy, so this is a structural regression for long.


It’s only Early Access for now:

    2024-05-20: OS version was released to Early Access subscribers

I just checked on the Account Page — I am signed up for the early access. The update screen reports “waiting for connection…” until it gives up.

EDIT: yes, I can see the “update is ready to download” screen.