REPRODUCIBILITY: No
OS VERSION: 5.0.0.72
HARDWARE: Sony Xperia XA2+
UI LANGUAGE: German
REGRESSION:
DESCRIPTION:
After updating from version 5.0.0.68 to 5.0.0.72, I lose Android app support during standby (I am not actively using an app). The rotating circle is continuously displayed in the AAS settings. Very rarely, the ‘Start’ or ‘Stop’ button flashes. However, most of the time only the rotating circle is displayed.
PRECONDITIONS:
The “Start Android app support when device starts” switch is turned on.
STEPS TO REPRODUCE:
It happens randomly.
EXPECTED RESULT:
Android app support runs after the device starts up and remains active
ACTUAL RESULT:
See description above.
MODIFICATIONS:
no modifications, no patches, no waydroid, no MicroG
No, sometimes it happened during the night and AAS was inactive in the morning, and sometimes it happened immediately after using an app. I wanted to take another quick look at the app, but AAS was no longer there.
Since it was no longer possible to operate the settings page, the only thing that helped was to reboot the hardware, which had always worked satisfactorily up to that point.
Xperia XA2 Plus Dual SIM user here, upgraded to 5.0.0.72 a few weeks ago. Did not experience any noticeable Android AppSupport regressions like this since the upgrade.
I also have the impression, that App Support in Standby or also minimized Android Apps often loose wether internet or App Support connection, probably this is not really stable. And often you are loosing the data you entered or the information you were just on…
I have no idea, as I never actually switch my phone off completely. I’ll check what happens.
To elaborate further: it’s not as if this error occurs every day. Since the launch of .72, I’ve had this bug maybe 4-5 times. Before that, I had never noticed it.
After updating from 5.0.0.68, my AAS crushes when using a specific app (my toilet-companion Angry Birds Journey). 4-5 minutes after playing the game, the whole device becomes unstable and very slow, until I somehow manage (with a lot of patience) to switch off AAS. Not only the AAS part, but the whole OS as well. Without running the specific app, everything works OK.
Maybe, just maybe, the AAS drains the RAM and, in your case, the AAS collapses.
Edit:
Confirmed for my case. App related, since it doesn’t happen with any other app I use.
I tried deactivating the autostart function of AAS for seven days and then switched off my device every evening. After that, I got through the whole day without any problems.
Yesterday, I switched it back to autostart mode and on that day I lost AAS again.
Edit:
Today it happened to me even though AAS autostart mode was disabled. This morning I started my phone without AAS – then when I launched an Android app, AAS started – and at lunchtime (the phone had only been on standby) AAS was gone again.
So it seems that it doesn’t matter whether you run AAS as an autostart or not.
However, this unreliability doesn’t occur as regularly for me as it does for others here. It can happen that I don’t notice this bug for several days in a row.
I can confirm similar behaviour on XA2+ after updating OS 5.0.0.68->5.0.0.72. AAS in autostart.
In the evening AAS OK, status=running, at night the phone in idle, in the morning AAS status in eternal loop, starting, running, starting, running..
Booting the device makes AAS working OK again. This happens occasionally, abt 4..6 times/week.
I do get this issue on my Xperia 10 iii, sometimes very frequently, other times not at all for days. I still have a sneaking suspicion that this is related to the well known 10 iii OOM issue. Unlike my XA2, XA2+ and 10 v, the 10 iii is affected by running apps which just get killed sometimes - presumably when the OS thinks its run out of memory. Why would it not be the same for AAS?
