[Release notes] Tampella 5.0.0.62

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

Version history of the OS release

  • 2024-10-24: OS version 5.0.0.21 “Tampella” was released for the Jolla C2 community phones as an over-the-air update.
  • 2024-11-14: OS version 5.0.0.29 “Tampella” was released for the Jolla C2 community phones as an over-the-air update.
  • 2024-12-17: OS version 5.0.0.43 “Tampella” was released for the Jolla C2 community phones as an over-the-air update.
  • 2025-01-30: OS version 5.0.0.55 “Tampella” was released for Early Access subscribers of all supported Sailfish OS devices as an over-the-air update.
  • 2025-02-20: OS version 5.0.0.61 “Tampella” was released for Early Access subscribers of all supported Sailfish OS devices as an over-the-air update.
  • 2025-02-24: OS version 5.0.0.61 “Tampella” was released as an over-the-air update for all supported Sailfish OS device users.
  • 2025-02-27: OS version 5.0.0.62 “Tampella” was released as an over-the-air update for all supported Sailfish OS device users. Installable images are available at Jolla shop.

Supported devices

The supported Sailfish X devices are listed in this table.

What’s new in Sailfish OS 5.0.0?

  • Sailfish Browser engine updated to Gecko ESR91, with work ongoing towards ESR102.
  • Android AppSupport upgraded to Android 13 (API level 33) for better app compatibility – first made available in C2 and later to other devices with migration from AppSupport 11 targeted for a future release.
  • MicroG 0.3.6 enablers added and fixed, improving opt-in support for Android apps dependent on Google services. Compatible with both AppSupport 11 and 13. MicroG instructions.
  • WireGuard VPN support added — can be manually installed on 5.0.0. Wireguard instructions.
  • New landscape mode for home view, events view, alarm view, and lock screen, with better support for notches and rounded corners.
  • Call blocking capability added, allowing selected incoming calls to be blocked.
  • Support for Jolla C2 and Jolla Mind2 built into the system, shaping the roadmap for future Sailfish development.

Release highlights 5.0.0.62

The list below contains the improvements of 5.0.0.62 compared to 5.0.0.61. All Sailfish OS release notes can be found here.

  • C2:
    • Size of system image reduced by 500 MB
    • Use of mobile data in AppSupport improved
    • Audio problems in Deezer and Duolingo fixed
    • Font sizes in Android apps reduced
    • Crash fix related to disabling the active SIM card
  • Robustness fixes in handling OS and other updates
  • Venho update for Mind2

All Sailfish OS release notes can be found here.

Installable images

Installable images are available at Jolla shop. Installation instructions for Xperia phones are at Sailfish X Installation Instructions - Jolla.

Known issues on the latest devices

Jolla C2

  • The touch panel doesn’t sometimes work on the first device unlock screen, and the security code can’t be entered.
    • Workaround: Shut down and start the device using the power button.
  • Recording videos does not work
    • Try Android camera apps, e.g., Open Camera
  • Disabling a SIM card crashes AppSupport after which mobile data does not work
    • Toggle the flight mode on and off to eliminate the problem.
  • Limited fastboot flashing support added to the C2 bootloader. Allow users to flash specific partitions with the public fastboot tool. C2 flashing instructions.

Xperia 10 IV and 10 V

  • Still in the free trial phase. No Android AppSupport (and Sailfish licence) is available. Download the installable images from the Shop.
  • The issues of 4.6.0.15 remain.
  • Reflashing Sailfish (the 2nd time) does not work with the flashing script. The additional flashing instructions for Xperia 10 IV and 10 V are here (while the first-time flashing instructions are in the Shop).

Changelog

The changelog compared to 5.0.0.61 is here.

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 are available at Sailfish OS Documents repository.

Other

This 5.0.0.62 is the target for the public release for all supported devices. There will be more 5.0.0 update releases later during the year’s first half.

11 Likes

Shouldn’t that be 5.0.0.62?

Definitely. A copy-paste mistake.

1 Like

My Phone (XA2Ultra) tells me there is an update, but to my understanding this would do nothing, right? So I can just skip it

“Robustness fixes in handling OS and other updates”

If you update to 5.0.0.62, these fixes will help you when installing the next update.

3 Likes

On first boot I didn’t need to disable and reenable SIM to be recignized! Many thanks!

Wait the second boot then you have no mobile data

For me the necessary steps to get mobile data working on my C2 with 5.0.0.55 and .61 were

  • Disable SIM1
  • Enable SIM1
    AppSupport restarted on its own. I understand that it crashed :slight_smile:
    Now with 5.0.0.62 I have to do
  • Stop AppSupport
  • Disable SIM1
  • Enable SIM1
  • Start AppSupport
    I have to redo it after every reboot. Is there any information I can provide so that you can locate and fix the problem?
1 Like

same here (C2, 5.0.0.62, German prepaid o2 LOOP card). This is actually the first time that I saw mobile data working on the C2 at all, before I didn’t try the disabling/reenabling thing, only restarting AppSupport, which didn’t help. With the Android-App pl.lebihan.network from F-Droid (which is just a frontend to android system settings network, I think) I only see IPv4 connectivity though, with my Xperia 10 III I see IPv6+IPv4. With a different (contract) SIM though.

2 Likes

Blockquote “Reduced Font size”
I use huge text size in UI and now appsupport screens show a tad larger than normal text size. That was slightly smaller than expected.

Am I right that Android Support 11 with API level 33 (Android 13) is just available for C2? Will it come for all official with SFOS 5.x supported devices?

My devices have Andorid Support 2.1.0 from 2023 with API Level 30.

Congrats!

very fine, flashed 5.0.0.61 in the morning and tweaked all day and now see that 5.0.0.62 is out meanwhile…

2 Likes

According to Release notes 5.0.0.55 also Xperia 10 IV and 10 V has AppSupport 13.

Yes according to release note, but on xperia 10III after latest update still api 30.

we just need to wait for a bit more to have it. :wink:

To reread. Emphasize mine.

2 Likes

Exactly, on the release notes X10III is not upgraded to 13. And somebody from Jolla said in the comments that they were so busy that they didn’t yet upgrade the X10III.
I have also X10III, so waiting also. But actually it’s good. Others get to report bugs first from 13, so we can then enjoy more bugfree experience when it lands to X10III :smile:

1 Like

AppSupport version for different devices is shown in that table.
Currently, C2, 10 V and 10 IV have AppSupport 13. The older products have AppSupport 11.

1 Like

…once licenses are available. :wink:

4 Likes

MobilePay not working on Xperia 10 III

MobilePay ver: 8.8.0 (in DK)
SFOS: 5.0.0.62 (same problem on 5.0.0.61)
MicroG version: 0.3.6.xxx (also tried older versions, same problem)

MobilePay can be installed and at the end of the installation it runs and I can use the app, but after closing the app, when I later try to access the app, I enter the pin and the app display: “a problem occurred, try again later” but I never succeed to log in again.

If I delete all data or delete the app and reinstall the installation process work and I am able to enter the app, until I shut it down, after shut down it’s not possible to open it again.

During one of the installation attempts I noticed the app very briefly displayed at quick warning that the app assumed there was not network connection.

The MobilePay app works well in my C2 and XA2 with same setup.

Other Android apps works well on the 10 III.

The problem occur regardless of being on wifi or on mobile network.

Has anyone else experienced this problem - or have suggestions how to correct the problem?

Rather there. :wink: