Was the battery running low? In that case it’s a known bug:
3 Likes
lolol that is NUTS!!!
thanks, of course that was my problem. what a NIGHTMARE.
2 Likes
Maybe @mal could make use of it? Sorry not sure, but can you make a copy of it just in case (seems there was another report of in-pocket reboot, so something’s there, but then again no reports of repeats so far, so maybe not a big deal)
Same here. All Android apps offline after upgrade. Regardless if 4 or 5G.
My 25W PD Samsung charger no works again. It also starts for maybe 10-20s at basically doing nothing but then goes up to 2700 mA. Which is not the full load but I think perfectly fine.
After update the phone seems to run hotter, when there is an android app running on the background listening music. At work I use some android web/fm radio and I can feel the phones heat when in pocket. Also the battery life feels worse. With my usage the battery was usually at ~20% after 48 hours before plugging it in. Now after 24h its already at 31%.
Yesterday after the update and after some use, my phone restarted itself twice. I don’t think it was a real restart: The follwoing happend:
It was lying on the table and suddendly, I noticed the Jolla Logo on the display. I Think, after that, the Sailfish Logo flashed up. Then I was promted to enter my Pin as alway after a boot up. I was not automaticly prompted to enter the PIN a second time, only after I swiped in th homescreen. Also I was not promted to enter my SIMPIN, which it should have after a normal restart. Sim showed connected and I could recieve a call.
After the second “restart” I shut down my phone, and restarted it again. Since then, it seems stable.
My phone crashed today when typing a message in Android WhatsApp. I have only ever witnessed crashes when I have had a heavy website running in the browser in the background so far, so this is a first. Phone just went completely black and I had to reboot it by holding the power button for a long time.
pstore doesn’t have anything new for this latest crash.
1 Like
My phone crashed too, while charging. Didn’t see it happening, just got a black screen. I did had AAS active, with some messaging apps running. I had to keep power pressed for some time to wake device again.
In retrospect, I didn’t try to login via ssh, so it might just be a very unresponsive UI.
Sounds like
1 Like
I’m not completely sure, but I believe in my case the phone actually turned off when it crashed. When I held the power button, it turned on as if it was turned off to begin with. Otherwise it sounds similar.
1 Like
ok, I found the gather_logs script in the sailfish docs and created a persistent log package + the console-ramoops-0
sailfish_logs_console-ramoops-0.targz (299.2 KB)
sailfish_logs_2026.10.03-02.08.08.targz (562.8 KB)
(I removed the . between tar.gz else it won‘t upload.)
1 Like
Bug report: 5.2.0.18 AAS no longer online when not in wifi
5 Likes
I had another crash just now. Phone was completely black and red LED was blinking slowly when I took it out of the pocket. I had to hold power button to turn the phone off. After holding the power button, phone vibrated briefly and then turned off. After that I was able to turn it on normally.
went on a long run yesterday, with the phone in a running belt that limits sweat but doesn’t keep the phone totally dry.
it got wet, but worked fine at first for taking pics/etc. when i took it out after about an hour, though, the phone’s touch screen completely stopped working.
the power and volume buttons continued to work, so i could control my media with sf-button-monitor, and my gps was still tracking my route and alerting me, so i didn’t want to restart the phone.
i carried it in my hand for the next 20 min so it could dry off and it did, but it still just wouldn’t work. i eventually put it back in the pouch and figured i’d deal with it when i finished.
i checked again an hour later, and it was drenched…but now it was working fine (with low accuracy and some false touches like you’d expect from a wet phone). it was probably the sweat anyway, but i was wondering- anyone else have the touch screen temporarily completely fail?
1 Like
Just updated to 5.2.0.18 (so much testing still to do), but wanted to mention my main fear was unfounded:
While it’s true that Android apps can no-longer access the internet without WiFi, I was able to fix that by changing Settings > Mobile network > Data access point > from Dual to IP(v4)… However I already knew that this fix worked for Internet sharing (WLAN hospot), which doesn’t handle IPv6-only mobile networks.
And the key point: Switching to IP(v4) only works because my mobile network provider (EE in the UK) supports IPv4-only data connections. Other mobile networks in this or other countries may not, which explains why this work-around doesn’t work for everyone. So you can test if the IP(v4) work-around will work for Android apps BEFORE upgrading, by testing if the same work-around works (or is even needed!) for Internet sharing (WLAN hospot).
8 Likes
Another small update: It seems that 5.2.0.18 has also fixed the problem I had with GPS basically not working with any Android apps (after you started moving), although I haven’t heavily tested this yet. This is great, because it was the one big thing stopping me from dropping Android entirely.
As Jolla didn’t mention GPS in their updates, I can only guess that full-screen Android apps not being able to rapidly refresh their display somehow interfered with them getting GPS satellite updates (so when they fixed Android apps being able to update their display rapidly, that also fixed the weird GPS issue).
4 Likes
I am also done upgrading. The bluetooth audio routing issues are fixed and audio plays through the headphones with no hesitation.
The only confusing part was the phone waiting for the LUKS pin at the first restart, with the green led steadily on but the screen off. A press on the power button revealed the keypad on screen, and all went well.
Great work! 
1 Like
Since the update I’m affected by High cpu-usage by system_server (AAS) - #3 by broncheolus
Battery life is terrible. When AAS is running, after some time one CPU core is stuck at 100%. System_serve is constantly at 13% cpu usage and the battery consumption is above 800 mA while the handset gets noticable warm. Never had this (according to together.jolla ?old?) problem in over 12 years. Restart AAS is mending it just for a short time…and even when not using any Android app after restart, this reappears after some time.
After the update I did not install any Android app, or changed autostart settings for background services of any app. No patchmanager, nothing special apart from running CargoDock not sailjailed
So, AAS has to be off, if the mobile has to last a whole work day.
By by 
to my main calendar (fossify) and Matrix (Element). That’ll be my biggest painpoints… [I know the native alternatives…just in case, one would suggest to switch 
]
If anyone knows a workaround, or even a solution - that would be highly appreciated!!!
EDIT:
I removed the Jolla store Android apps and then the aas itself (see Removing Android AppSupport | Sailfish OS Documentation → 1. 1) & 1. 3) without touching all the other Android apps), shut down the device, reinstalled aas after Boot up … and all seemed normal then !!! 
. …until the next morning…when the system_serve was again at 13%… But, after aas restart: result!!! Right now it runs 24h like expected. …happy camper again and I hope system_serve behaves from now on.
4 Likes
5 Likes