5.0.0.71: No Audio or Video playing with any android apps on XA2. With 5.0.0.68 everything works fine for me. Can anyone confirm this?
1 Like
Update went fine on X10iii. No issues as commented above. Patches were removed before the updating process as usual.
Android support worx as expected.
Edit: Patches I do use work too.
Hmm okay, strange then. I did not see any AppSupport packages listed when I updated with ssu.
Xperia 10 III, update runs good from UI. Patchmanager has no Problems. Android App Support dont start after update, can somebody help?
Update: Android App Support dont start if run on device start is enabled. Disabling it and I can start AAS normaly.
Bug report opened: [10 III] [5.0.0.71] Android App Support does not start when “Start Android App Support when device starts” is enabled
Update 2: No Audio in AAS! Will open Bug report soon.
Update 3: Audio in AAS is back; don’t know what happened.Sorry.
1 Like
5.0.0.71, X10III: my AppSupport does start successfully on first app launch, but I did manage to get it into a known Android app hang error state, and it wasn’t able to recover - endless restart cycle, until I rebooted.
I’ve always been able to restart AppSupport on 5.0.0.68. Something is definitely different.
Reflashing 5.0.0.71 on my 10V did not go well.
I can’t log into my Jolla account with this update. I double, triple and quadruple checked my credentials. It tells me there is an error registering this device with this username.
AppSupport on the 10 III working okay for me post update (tapped on Start on the Settings page, not via app launch). I have the ‘Start on bootup’ option turned off, possibly related?
1 Like
Thanks for this update for my C2. The AppSupport connectivity change is a blast.
4 Likes
It is related. Turn it on in case you want your android apps to autorun.
Pretty useful for various messengers.
I probably didn’t word it well–meant possibly related to their issue, if they had it switched on during the update and temporarily disabling then rebooting might fix. It is certainly good to have for messaging apps!
1 Like
Update went smooth on 10III. First start of of Android support also went fine. After a reboot Android support looped and could not come up. Rebooted again with all options exept autostart turned off and it works stable now even after reactivation of the other options.
2 Likes
No problems at all here on my X 10 III.
Thanks for the update!
Thank you, this helped me. AppSupport was stuck in the starting state forever for me too and this helped.
Edit: AppSupport auto-start does not work in 10III - I don’t mind because I rarely reboot the phone but auto-start is defintely broken.
Almost… Rebooted again and Android support autostart did not work. Manual activation works, though.
Installed, phone works, android has connection
So, sudo fastboot flash super fimage.img001 is the one and only flashing command I need to do? I can skip the rest?
Great, had this issue multipletimes and never new why
the failed startup on 10 III has this as a symptom, if not necessarily as a cause:
ServiceManager: Waiting for service ‘SurfaceFlinger’ on ‘/dev/binder’…
also these:
libc : Unable to set property “ctl.interface_start” to “android.hardware.power.stats@1.0::IPowerStats/default”: error code: 0x20
libc : Unable to set property “ctl.interface_start” to “android.hardware.gnss@1.0::IGnss/default”: error code: 0x20
restarting lipstick doesnt help, but a full reboot does. you can start android immediately after lipstick and it will boot just fine. i tried doing it earlier in the boot
also i flashed the full image from the store, not OTA, so its not a lingering old package or something
5 Likes
Android app support did not start. Solved by removing sim card and rebooting, this time appsupport started normally. Then rebooting with simcard also worked.
Got my 10iv without a sim card on the wifi. As sweet as the new AppSupport appears, no internet(!)
I sideloaded the pl.lebiha.network and com.parizene.netmonitor apps and the best I could get was Netmonitor leading me to enable Android WiFi only to say “You don’t have permission to change the Wi-Fi network”
Is there something missing? Used the sfos-upgrade script from olf, any chance it missed a spot?
PS. Because the 10iv is sort of troubled, I think it was cellular internet that was broken, so as a matter of rule I’ve always had this phone on wifi, even if it was my work phone’s tether. This feels like a big regression!