AAS simply stops after some time and cannot be restarted without rebooting the phone. This bug affects both my daily drivers, i.e. the Xperia 10ii and tge Xperia 10iii
The longest time AAS was working after the update was less than 24h. This means that I have to reboot the devices at least once a day.
On my Xperia 10ii AAS stopped working during the night when no Android App was active and I didn’t use the phone (last night and tgis night). AAS apparently is not stable atm. Very hard to track such bug.
Did you try not to reboot the device completely but only restart GUI with Utilities and then restart AAS manually?
TLDR: On my X10, after update at the beginning I also had problems with not stable running / self terminating / not reliable starting AAS, but miraculous this effect disappears a few days later and after some reboots. AAS now running stable. No explanation, only observation.
Thank you for this hint. No, I did not try restarting GUI (instead of rebooting) yet because GUi seemed not to be affected. Next time I will try restarting GUI and report.
I partially share your exprience: the intervall during wich AAS is running properly appears to become longer and longer …
Since yesterday morning, ASS on both of my daily drivers works flawlessly – no stopping of AAS and thus no restart necessary.
Out of curiosity, I stopped AAS manually and opened an Android App thereafter (without restarting AAS manually) and – wonders of wonders – everything works a it should for nor.
Therefore I could not test if restarting GUI with Utilities would break a restart-loop of AAS yet (and hopefully I will never have to)
In fact everything appears more snappy to me now and I start loving the update (after initially hating it)
i have seen this several times, particularly in the first week i was using the phone and installing my apps+microg.
appsupport crashes, and restarting gives ServiceManager: Waiting for service ‘SurfaceFlinger’ on ‘/dev/binder’…. stopping/starting appsupport does not help. stopping/starting lipstick, sadly, does not help. rebooting the phone seems to help, but two times now i had to reboot twice.
given the number of times ive seen this (6 or 7?) its possible that its just a race condition and that appsupport simply fails to start sometimes, and rebooting the phone isnt what fixes it, but random chance is.
I’m running opengapps, but otherwise seeing the same problem when AAS OOMs itself every so often.
As an endless AAS restart loop just happened in an airport, right at pre-boarding, in desperation I tested turning off some new AAS toggles:
(Start AAS on bootup - OFF, previous default due to using X10III camera switch patch)
Allow running microG services - ON (assuming cannot disable, because opengapps)
Show SFOS media in Android Gallery → OFF
Make contacts available to Android apps → OFF
I also switched back to “Camera: front” just in case.
Voila, AAS successfully started up right after this.
its possible that its just a race condition and that appsupport simply fails to start sometimes, and rebooting the phone isnt what fixes it, but random chance is.
Yep, quite possible my toggle fiddle just helped succeed through a race condition, but I’ll take it.
C2 user here. Update seems to have gone smoothly. Had some issues downloading the update. Resolved after uninstalling adblock hosts and a reboot. Adblock hosts reinstalled afterwards, and everything seems to be working. Some host(s) may need whitelisting.
So I’m hereby switching my workaround theory from “new AAS toggles fiddling” to “patient manual Stop / Start”, and at next crash time will evaluate whether restoring toggles to all ON has any effect here.
right now I try the workaround to disable the proximity sensor (which is suboptimal). Without that workaround, active calls cannot be managed. (And reminders and alarms do not work as expected.)
Android app support less stable and starting loop
After two days of usage I can now see that the android app support is less stable. Had a few more stops and twice needed to reboot because of a non-starting android support, it went into a loop trying to start and fail.
how to debug?
If this is potentially caused by some android or other apps, how would someone go about debugging it?
(I do not have 3rd party repos, but a number of android apps. How can I find out, which are attempting to start on a reboot (with autostart allowed)?)
After I failed logging in to recovery mode because I forgot the code I panicked. So all I had in stock was to try to reboot. Did that by hitting Vol Up/Down and Power together. The phone rebooted and asked for drive unlock code. Then it booted normaly. Sony Xperia 10. Thank heavens!
I can confirm that disabling AAS auto-start fixes the audio issues on 10 III (playback and/or recording not working inside of Android apps) as mentioned by @Seven.of.nine and @Trebis
I too did have auto-start enabled before upgrading to 5.0.0.71 @JoOppen
