There is no “new” AAS for 10 IV and V as it existed way before on those. Did AAS worked on your 10 IV before the update?
“New version of AppSupport”, then, because clearly it did get updated.
Sure it worked, though I also used to have a SIM card in the phone. Any chance AAS used it for data transfer despite the phone used to be on wifi otherwise?
That’d suck, if it required a SIM card…
To answer myself… Yes, that single command is all that is needed.
3 Likes
Just checked on my XA2. After updating this morning, Android apps can still play both video and audio (locally and through Bluetooth). Have tried Molly and RedReader.
If it helps in any way, device rebooted twice (the second time by itself). Didn’t notice anything else out of the ordinary. Last time I’ve reflashed with Emma I’ve used Android 9.
3 Likes
Would be great if those with the AppSupport not starting issue could send us some logs.
You can use this gather_logs.sh script.
Download the script on the device and run it like
sh gather_logs.sh
On first run it will prepare the logging. After that reboot the device, try to start AppSupport, and after some time run the script again. It will pack the logs and reset logging configurations back to normal.
And you can send the log package to me as a DM here. The logs may contain personal information, so don’t share them publicly.
6 Likes
I can confirm that AppSupport won’t start if run on device start is enabled on the Xperia 10 iii - on the Xperia 10 ii verything is fine.
I had trouble booting the Xperia 10 iii after the update, maybe because on the Xperia 10 iii “start App Support on device start” was enabled, while it was not enabled on the Xperia 10 ii where I had no such trouble.
Now, “start App Support on device start” worke fine on the Xperai 10 ii and not so on the Xperai 10 iii.
1 Like
Update went well on Xperia 10III and Jolla C2. Devices rebooted twice after install step.
AAS is not set to start on boot and seems functional once started manually.
10III was at approx 30% battery and connected to charger. It exhibited the “minimal brightness on reboot” issue, aka stealth-mode security code entry.
C2 was at approx 75% battery (not charging). It did not exhibit stealth-mode security code entry.
Maybe I can put it more clearly:
The different behaviour of my two daily drivers, i.e. the Xperia 10 ii and the Xperia 10 ii after the update may result from the different AppSupport Settings at the first boot after update.
With the Xperia 10 ii “start App Support at device start” was not enabled, with my Xperia 10 iii “start App Support on device start” was enabled. Consequently, App Support should have started on the Xperia 10 iii with the first boot after update - which failed. Starting App Support on device start now persistently fails on the Xperia 10 iii while it works nicely on the Xperia 10 ii.
This suggests that “start App Support on device start” should be disabled prior to updating. Maybe Jolla should mention this in the instructions.
1 Like
Not sure if this helps, but my 10 III does not have this problem.
AppSupport has always been set to auto start. It (auto) started normally after the upgrade, and now I did a reboot and it also autostarted again
Also don’t see an audio or video bug. Watching youtube videos in android Opera browser works normally, with audio and video.
4 Likes
This seems to rule out the possible cause I had in mind - thank you!
I am now looking for other differences between my two devices
After 3 restarts, audio and video now work with version 5.0.0.71 on the XA2.
App Support on my Xperia iii now is constantly starting and stopping (by itself) It does not run stable anymore - it is de facto useless atm.
On my Xperia 10 ii it is still fine.
I would not worry too much about the audio issue.
I’m using a 10 III as my only phone. Sailfish has lots of problems with audio on that device: Often playing audio from the earpiece rather than from plugged in headphones, sometimes using the wrong microphone during calls, every now and then outputting only (very quiet) crackling noise.
Unfortunately it does not seem that this ever gets fixed.
Thank you, disabling autostart for the app support helped. Xperia 10 III here.
Try disabling starting the app support on boot and start it manually instead (after a reboot). Something definitely went wrong there, but that workaround works for me for now.
1 Like
it works for me too, but only for about 3 or 4 hours. Thereafter, AppSupport constantly stops and restarts and Android Apps are not usable anymore. So far, only rebooting the device stops this behaviour. Therefore it am not starting AppSupport anymore on the Xperia 10 iii even if it works for a few hours
1 Like
Now AppSupport on my Xperia 10 ii behaves like on my Xperia 10iii, i.e. it constantly stops and restarts and thus Android Apps cannot be used anymore. It only took a few hours more to enter this state.
5.0.0.71 effectively killed AppSupport
1 Like
Have you tried uninstall / install ?
not yet - i am afraid it won’t help. For now, I immediately stop AAS manually after having used an Android App. For messenger Apps like Signal this isn’t a good option though
On my C2, the automatic orientation failed after applying the update, but it restart working after multiple attempts, incl. changes in settings (enable/disable/enable screen rotation and others…), restarts, and finally a long night untouched 
I also had to reinstall Patchmanager as patches did not seem to be working any longer.
We have a second C2 which had the “stop/start/stop …” AAS issue. Simple reboot seems to fix it, but issue comes back once in a while (thinking about something is up with home network mesh while moving arround, but zero proof).
Other than that, everything works fine 