REPRODUCIBILITY: every time
OS VERSION: 5.0.0.71
HARDWARE: Sony Xperia 10 III
UI LANGUAGE: german
REGRESSION:
DESCRIPTION:
After the update from 5.0.0.68 to 5.0.0.71, Android app support does not start when the device is started. Android app support also cannot be started using the button. The message “does not start” is displayed.
PRECONDITIONS:
The “Start Android app support when device starts” switch is turned on.
STEPS TO REPRODUCE:
The “Start Android app support when device starts” switch is turned on.
Reboot Device
Android app support doesn’t start
Android app support cannot be started manually using the button.
EXPECTED RESULT:
Android app support runs after the device starts up, apps are loaded in the background, and notifications are displayed.
ACTUAL RESULT:
The Android app support is not running and cannot be started.
If the option to start app support when the device starts is disabled, app support can be started after reboot manually using the button or by opening an app.
MODIFICATIONS:
I have some patches installed, and I use custom repositories from openrepos. All the same as before the update to version 5.0.0.71.
I read about this “bug” about AAS, and I notice that the users having this problem, also have enabled the option to autostart AAS after reboot.
I do not (never had) this autostart option enabled on my device, and AAS works flawlessly. Tried rebooting the device, starting and stoping AAS multiple times, and have no problem at all.
Is there a possibility that the autostart option could cause this behavior?
Xperia 10 iii with 5.0.0.71
As reported in the other thread, “Start Android app support when device starts” is working on my Xperia 10ii but not so on my Xperia 10iii.
However, on both devices, AppSupport enters an endless stop-restart loop after a few hours and Android Apps cannot be used anymore. So far, only rebooting the device helps.
Entering the endless stop-restart loop is not related to auto-starting AAS with device start. It occurs now always after a couple of hours.
X10III, autostart=on causes the AAS restart loop.
No MicroG here.
No AAS restart loops due long or intense android apps usage whatsoever.
AAS autostart=off fixes the problem.
Then, if patient and quick enough during the restart loop, you can click on the ‘stop’ button in the brief moment it is enabled. That may save a SFOS reboot.
Same for me. Xperia 10 iii, 5.0.0.71, Android 11, no MicroG. Autostart enabled, AAS runs into a loop. No problem with the previous version.
Autostart off seems to fix it for the time being. I will see for how long
… is it just me, or is Sailfish starting to suffer from bit rot? All those small issues with sound, network, AAS coming together start to make me nervous.
The conclusion from the messages in this thread seems clear: I have a working 10 III, so I am not going to update to 5.0.0.71 until the AAS issue is resolved. No point risking my phone to become unusable, given that 5.0.0.71 contains no discernible value for me. Thanks to everyone who reported here, I hope the problem gets fixed soon.
I got hit by the AAS loop this morning on my C2, never have had auto start enabled. But I usually don´t kill the AAS when done with Android apps, just have it running. Battery drained quickly also, but guess that can be related to the loop. And the alarm did not trigger this morning (again). The SW occupied with the loop?
this occurred with both of my daily drivers (Xperia10 ii and iii) after some hours of AAS use irrespective whether I had Auto-Start of AAS enabled or not and it required a reboot of the device in order to use Android Apps again.
However, the intervals of flawless operation of AAS became longer and longer after every reboot. While stopping of AAS immediately after the update required multiple reboots per day, now I have AAS uptimes of a couple of days (or even longer, because the last stop of AAS and following reboot is now two days ago).
Same here. It took about 3-4 reboots in 48hrs untill AAS became stable over days. I waited another 12 hrs untill all pictures were visible again in AAS.
Interestingly, I got hit by this after updating my Xperia 10 III to 5.0.0.72. On 5.0.0.71 Android AppSupport autostart worked just fine. But given the number of people having the issue on 5.0.0.71 I suppose I was just lucky and now I run out of luck.
Since the update from SFOS 5.0 0.68 to 5.0.0.72, it has become even worse. App Support keeps freezing and cannot be restarted. It enters a start loop. The only solution is to restart the mobile phone. This means I have to restart my mobile phone 2-3 times a day.
Did you try to switch AAS autostart off and uncheck all options before the manual start of AAS?
Especially the option to show the media gallery in Android seems to eat performance.
Resetting the SFOS media index in utilities before and waiting for all media to be visible again could also help. This takes some time once but seems to have a positive effect.
