I have a similar problem on my XA2 PLUS. When I open map apps like Here and Google Maps, as has already been reported on the forum, these apps cause App Support to stop and fail to restart. Before the update to 5.0.0.72, this didn’t happen. Turning the phone off and on again solves the problem for me.
1 Like
Same here with my Xperia 10 ii - while under 5.0.0.71 that stop-restart loop occurred less and less, it is hitting me now (5.0.0.72) more often than before and even shooting down the device for reboot (red LED is lit) takes ages now.
I’m on Xperia 10 III, 5.0.0.72, and Android App Support seems somewhat unstable – it works for a few days after reboot, then it crashes and doesn’t start up again until I restart the phone.
I always try to get an stable update as soon as possible. On my 10iii, 071 and 072 went perfect with no problems with AAS. But now I’m afraid to update my friends 10iii (the same as mine, but with whats app). Whats app is a must there.
Can I wait for the next major release, or do I have to update every single release? On lineageOS you can skip several updates and just install the latest.
How about SailfishOS, is it possible (worth it) to skip updates too?
On a forum like this it’s normal that someone gets the impression that there are a lot of problems. But people who don’t have that problems are mostly not writing / visiting here.
And there are many, many, many people which just enjoy their nice working sfos devices.
1 Like
Same here, Xperia 10, 5.0.0.71 + 72.
Autostart on boot doesn’t work. After starting AAS manually it works fine. On the phone with 5.0.0.71 since long time.
For the other phone with 5.0.0.72 I’ll report later in case it’ll crash. For now it works.
meanwhile both phones updated to 72, works mostly fine but sometimes not: AAS then crashes, or impossible to start, or start loop. Sh*t happens sometimes, but mostly it works.
… ^^…is someone able to answer this question ? Thank you.
You have to upgrade through all the ‘Stop’ releases in sequence to get to the latest. Non-‘Stop’ releases can be skipped. The release notes for each release tell you whether its a ‘Stop’ release or not.
1 Like
There are so called stop releases which cannot be skipped because of different technical reasons. Every other release should be skippable (and should automatically be skipped by the updater if a newer one is available)
1 Like
Today I updated my friends 10 iii to 072 and … … everything is fine. AAS on boot is ok. It didn’t show me the 071 update, just 072 coming from 068. Thanks a lot Jolla Boyz. 
2 Likes
I can also reliably produce the continuous AAS start-stop looping by doing the following on both Xperia 10 iii and 10 v.
Reboot with AAS start on boot set to OFF.
When the OS has fully booted just click on any Android app from the app grid WITHOUT starting AAS first.
Normally clicking on an Android app on this state would then automatically start AAS. On .72 it just gets stuck in this continuous loop trying and failing to start.
Only another reboot fixes it.
2 Likes
I can wait on the Android settings page until I can stop the AAS - you need to be quick as after a failure it will try to start again by it self!
Starting it from the settings page just worked for me.
X10III 5.0.0.72
Starting AAS as prerequisite for first android app works for me.
(AAS autostart at boot =OFF)
My workung setup is:
Have K-9 Mail and Delta Chat installed, and Fennec for the Browser.
The periodically mail checks keep AAS running, and Fennec replaces the outdated Browser.
Automatic start of AAS at boot time is OFF.
If ON, sound recording on A. apps don’t work.
I dont have AAS so I cant test, but maybe someone can try:
AAS autoboot is probably a systemd service?
if yes, does aas work when you start the aas service immediately after boot (systemctl start) ?
if it works that way, maybe just another (later?) systemd target is needed to work properly?
Perhaps it is the connection, Wi-Fi or Bluetooth, that is causing AAS to crash.
I’ve noticed that AAS crashes at a certain point on my 10 III. My flat is on a slope. When I drive there by car, I briefly come within range of the Wi-Fi below the house, but then I have to make a loop to get up to the house. So I leave the Wi-Fi range again. AAS crashes on the road just before the house. It has happened three times at exactly the same point. I suspect it’s when I come back into range of the Wi-Fi. I always listen to podcasts in the car via Bluetooth using an Android app, and the audio output cuts out at the same spot when I approach the house. So, I briefly come into range of the Wi-Fi – I leave the Wi-Fi range and then come back into it shortly afterwards – and then AAS crashes.
Translated with DeepL.com (free version)
2 Likes
I have the habit of switching WiFi and mobile data connection manually off and on whenever leaving the house or the other way round when coming back. AAS with autostart is instable instead of that.
10 III 5.0.0.72
(Edited to remove a mistaken assertion)
Did you manage to figure out what causes the issue?
Do you know if this is monitored internally ?
I’m not employed by Jolla so I don’t know if anyone there has investigated this. There is no tracked tag in this post so my guess would be “no”. Personally I haven’t really investigated as I can live with manually starting AAS for the time being.
1 Like
Yes, Jolla is aware of it. I sent Keto a comprehensive package with logs via the release post for 5.0.0.71, where the bug was first described.
4 Likes