Keto
18 August 2026 08:00
1
This is another minor bug fix release, still targeted only for the Jolla Phone.
5.2.0.17 release highlights
Known issues
Thank you for all the reports in the bug reports category . Keep them coming, and we’ll do our best to address them.
Changelog
Full Changelog_from_5.2.0.16_to_5.2.0.17.md (4.0 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
Version history of the Sailfish 5.2.0 releases
All recent Sailfish OS release notes can be found here .
The Sailfish OS help articles are available at Sailfish OS Documentation .
32 Likes
There are still some charging issues with JP. As that has serious UX influence I guess it should be added to the known issues?
12 Likes
+1 to this. I have been able to charge normally now 2 weeks, but had phone rebooting while connected to charger during night: Complete crash when charging - #19 by CLMA31 . Would be good to have charging problems as known issues.
PS. Thanks for the update! Great to see quick release cycles for Jolla phone
5 Likes
Many thanks for this update, which went off without a hitch!!
Also, are there any plans in the near future to try and resolve the video issue within AAS? (I believe this affects some native apps as well, if I’m not mistaken…)
https://forum.sailfishos.org/t/5-2-0-16-jp2026-graphics-engine-bug-in-aas/31436/14
4 Likes
Great addition to the known issue list
Kea
18 August 2026 10:39
7
Thank you for the update. It went smooth without problems. Yet it was different this time: I had to tap the safety code of my device three times.
Kea
18 August 2026 10:41
8
On my JP charging reaches 90%, it never charges to 100%.
So yours works as expected. As that’s the default. You can change it.
3 Likes
ric9k
18 August 2026 10:56
10
My JP2 doesn’t see the update.
It says:
Up to date
Last checked: Just now
The indicated version is 5.2.0.16
Anyway, thanks for the update and all the work!
This phone is great!
Can I use the manual way or is it not recommended for some reason?
or Sfos-upgrade from Chum?
mal
18 August 2026 12:11
11
You can control maximum charging level in Settings->Battery->Battery aging protection
3 Likes
So wait another hour. Since ever the SFOS-updates don’t hit every phone in the same minute.
2 Likes
ric9k
18 August 2026 13:31
13
Thanks. I didn’t know. Well… too impatient I was, I did a:
devel-su
version --dup
It installed 53 packages
csd-toh;0.16.105-1.33.1.jolla;aarch64;jolla
csd;0.16.105-1.33.1.jolla;aarch64;jolla
droid-config-jp2601-bluez5;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-config-jp2601-flashing;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-config-jp2601-policy-settings;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-config-jp2601-preinit-plugin;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-config-jp2601-pulseaudio-settings;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-config-jp2601-sailfish;1.0.61-1.11.1.jolla;noarch;adaptation0
droid-config-jp2601;1.0.61-1.11.1.jolla;aarch64;adaptation0
droid-hal-jp2601-detritus;0.0.6-202608031225;aarch64;adaptation0
droid-hal-jp2601-img-boot;1.3.0-1.4.5.jolla;aarch64;adaptation0
droid-hal-jp2601-img-vbmeta;0.1.0-1.3.7.jolla;aarch64;adaptation0
droid-hal-jp2601-init_boot;1.3.0-1.4.5.jolla;aarch64;adaptation0
droid-hal-jp2601-kernel-dtbo;0.0.6-202608031225;aarch64;adaptation0
droid-hal-jp2601-tools;0.0.6-202608031225;aarch64;adaptation0
droid-hal-jp2601-users;0.0.6-202608031225;aarch64;adaptation0
droid-hal-jp2601-vendor_boot;1.3.0-1.4.5.jolla;aarch64;adaptation0
droid-hal-jp2601;0.0.6-202608031225;aarch64;adaptation0
droid-hal-version-jp2601;1.0.0-1.3.17.jolla;aarch64;adaptation0
droid-system-jp2601;1.0.21-1.6.1.jolla;aarch64;adaptation0
droidmedia;0.20260522.0+7+g96f8c18-1;aarch64;adaptation0
embedlite-components-qt5;2.0.2-1.32.1.jolla;aarch64;jolla
feature-jolla;0.3.0-1.7.10.jolla;noarch;customer-jolla
harbour-file-browser;3.10.0-1;aarch64;store
harbour-gpsinfo;0.9-1;aarch64;store
harbour-maep-qt;1.4.13+master.20220516083048.3.gedaa56b-1.2.1.bso;aarch64;sailfishos-chum
harbour-simplecrop;1.2.3-1.8.1.bso;noarch;sailfishos-chum
harbour-spritradar;0.2.5-1.6.1.bso;aarch64;sailfishos-chum
harbour-stopmotion;0.4.5-1.8.1.bso;aarch64;sailfishos-chum
harbour-stumblefish;0.1.8-1.2.1.bso;aarch64;sailfishos-chum
jolla-camera;1.3.10-1.7.1.jolla;aarch64;jolla
jolla-developer-mode;0.6.25-1.5.3.jolla;aarch64;jolla
lipstick-jolla-home-qt5-components;1.27.13-1.55.1.jolla;aarch64;jolla
lipstick-jolla-home-qt5-weather-widget-settings;1.27.13-1.55.1.jolla;aarch64;jolla
lipstick-jolla-home-qt5;1.27.13-1.55.1.jolla;aarch64;jolla
nemo-qml-plugin-connectivity;0.3.3-1.19.1.jolla;aarch64;jolla
ofono-vendor-mtk-radio-plugin;1.0.5-1.6.1.jolla;aarch64;adaptation0
patchmanager;3.2.12-1.4.1.bso;aarch64;sailfishos-chum
patterns-sailfish-device-adaptation-jp2601;1.0.61-1.11.1.jolla;aarch64;adaptation0
patterns-sailfish-device-configuration-common-jp2601;1.0.61-1.11.1.jolla;aarch64;adaptation0
patterns-sailfish-device-configuration-jp2601;1.0.61-1.11.1.jolla;aarch64;adaptation0
platform-images-jp2601;1.3.13-1.6.1.jolla;aarch64;adaptation0
pulseaudio-modules-droid-common;14.2.110-1.5.1.jolla;aarch64;adaptation0
pulseaudio-modules-droid;14.2.110-1.5.1.jolla;aarch64;adaptation0
sailfish-components-weather-qt5;1.3.11-1.20.1.jolla;aarch64;apps
sailfish-content-ambiences-2026;1.0.0-1.1.1.jolla;noarch;jolla
sailfish-nfcshare;1.0.4-1.4.1.jolla;aarch64;jolla
sailfish-version-variant;5.2.0-1.14.17.jolla;noarch;jolla
sailfish-version;5.2.0-1.14.17.jolla;noarch;jolla
sailfish-weather-backend-metnorway;1.3.11-1.20.1.jolla;aarch64;apps
sailfish-weather-backend-openweather;1.3.11-1.20.1.jolla;aarch64;apps
sailfish-weather;1.3.11-1.20.1.jolla;aarch64;apps
xulrunner-qt5;115.37.0+git5-1.32.1.jolla;aarch64;jolla
And finished asking to reboot with a nice humoristic comment, typical of the Linux ethos:
“REBOOT NOW […]
All bugs encountered until reboot are features.”
Phone seems (3 minutes test) to behave nicely and is up to date!
3 Likes
Cryx
18 August 2026 14:01
14
Just noticed that Patches don’t work anymore.
4 Likes
koza
18 August 2026 14:36
15
Yes no Patches at all ( EDIT: uninstall and install PatchManager to fix this)
btw. Call volume on hands-free speaker seams to be normal on good level now, even i can not see anything related in changelog, before update it was almost unusable outdoor.
1 Like
ric9k
18 August 2026 15:01
16
I seem to recall that Patchmanager needs to be de+reinstalled after updates for some not so easy to fix reasons.
I did and it works now.
10 Likes
Cryx
18 August 2026 15:23
17
Thanks, worls now. Never had that before…
Kea
18 August 2026 15:36
18
Better not change anything if there is no problem.
Just installed 5.2.0.17 and I can already confirm that anachb.at, an Austrian multimodal route planner, is now usable on the native browser. Previously it was not possible to enter the departure and target locations. There is still an issue with some buttons being unresponsive, for example when opening the map (which works), the back button on the site does not respond.
3 Likes
Update went through without issues.
One issue with hotspotting while downloading the update - internet cuts out on the client side (that is connected to the hotspot). I dont know if this is something that happens in general, tho; I have noticed that hotspot connectivity is a bit more “flaky” than f.e. on X 10 II