[Release notes] Finlayson 5.2.0.20 - Jolla Phone first

Announcements
1

This is a bugfix release mainly addressing some of the issues found in the previous .18 release.
Due to those issues we did not publish that release yet to the other devices like originally planned.

Besides the fixes for the regressions in the previous release, there are also some other nice improvements.

5.2.0.20 release highlights

  • AppSupport

    • Improved handling of Android apps call UI
    • microG updated to v0.3.17.252432
    • DNS handling fixed
    • Video seeking fixed
    • Android app covers showing wrong content fixed
    • Several bugs fixed in AppSupport Bluetooth integration, some of which caused issues also with Sailfish side bluetooth connections
    • Uninstalling AppSupport now works correctly

  • Several fixes related IPv6 handling, and also support for the privacy extensions

  • WLAN EAP methods are now set correctly

  • Weather app now shows more appropriate icons depending on the time of day

  • Some fixes, improvements and documentation in Symbiosis, the TOH daemon

  • Non functional exposure modes were removed from front camera on Jolla Phone

Changelog

Full Changelog from 5.2.0.18 to 5.2.0.20 (8.9 KB)

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

Version history of the Sailfish 5.2.0 releases

2026-10-13 5.2.0.20 Jolla Phone first
2026-09-30 5.2.0.18 Jolla Phone only
2026-08-18 5.2.0.17 Jolla Phone only
2026-07-29 5.2.0.16 Jolla Phone only
2026-07-20 5.2.0.15 Jolla Phone only
2026-06-16 5.1.0.11

All recent Sailfish OS release notes can be found here.

Help articles

The Sailfish OS help articles are available at Sailfish OS Documentation.

67 Likes
2

Smooth sailing here, thanks for the update!

4 Likes
3

Wow! Big props for taking the issues with ipv6 on AAS seriously and shipping a fix so fast. Really highly appreciate it!

15 Likes
4

Wow indeed, gotta appreciate the pace of these updates :heart:

2 Likes
5

Had a slight hiccup with AAS since the vtinf/manifest.xml was overwritten with this update, but putting back the android.hardware.gatekeeper hidl section and restarting AAS fixed it.

PS: yes, this was entirely my fault.

4 Likes
6

Have we got a timeline on when this release will come to other devices?

3 Likes
7

As expected, IPv6 mobile data works with AAS apps again. Thanks for the fast update.

7 Likes
8

A usual, the update was quick and smooth :slight_smile:

Thanks to the whole Jolla team for rolling out updates so regularly!

It reminds me of the early days of the Jolla Phone 1 era: update, update, update…

7 Likes
9

No issues upgrading, went very fast.

Still issued with Amazfish when Appsuport Bluetooth is installed. So uninstalled the Appsuport Bluetooth.

10

How nice to wake up for new update! Thanks all sailors for your hard work❤

2 Likes
11

Update went fine. Just had a short car trip and my Bip is still connected to phone. Previously it was almost certain that the bluetooth stopped working after a car trip so this looks really promising.

12 Likes
12

this just gets better and better.

1 Like
13

I have not yet installed 18. Now, update propose direct upgrade from 17 to 20. Is this OK, can i proceed?

2 Likes
14

Updated both J2 and C2. No problems so far!

1 Like
15

It’s always OK if you upgrade in GUI.

1 Like
16

So far Bluetooth works without problems

1 Like
17

When I switch the phone on, it vibrates non-stop until I enter the unlock PIN.

The patches aren’t working, probably because they aren’t up to date.

Everything else is fine; Bluetooth is finally working properly – thank you.

Edit: The vibration issue sorted itself out, and the patches were applied when I updated Patchmanager. Resolved

1 Like
18

All my patches deactivated and I can’t reactivate them because they are compatible with 5.2.0.18 and not 5.2.0.20.

This is my first phone update since I got the phone so I could be doing something wrong. I’m still learning the ropes.

2 Likes
19

@rodoherty Disable version checking in patchmanager settings… Should work.

4 Likes
20

and the advice has also been to reinstall patchmanager after an OS update

9 Likes