[10 III] [5.0.0.71] Android App Support does not start when “Start Android App Support when device starts” is enabled

Bug Reports
,
42

What is the default setting for power saving in sailfishOS? I never changed something there. I don’t tweak anything. I still don’t have any troubles with my 10 iii.

1 Like
43

My settings in Settings/System/System/Akku is displayed now - (after attaching the mcetool tweak yesterday):

Energy saving mode:
Activation level: not used

Use energy saving mode until a charger is connected: not checked

Battery aging protection:
Charging mode: Use limit
Stop charging at: 80%

Sorry for my translation to English, my system is running in German. Hoping it’s understandable.

44

I imagine “Settings/System/System/Akku” should be replaced by “Settings/System/System/Battery”, right? (I’m in French, I’m trying to transpose… :slight_smile: )

45

Yes. It’s the same thing. But in my german SFOS translation in fact the menu item is called “Akku”.
Akku is short for accumulator, that’s a rechargable battery.

46

Akku is also finnish and means rechargeable battery

47

I’m currently getting quite a lot of Firefox crashes and then the AAS start loop.
I suspect the root cause is a network switch, and then AAS going into the start loop - Firefox is probably only how I notice it because of my habit of listening to steamed audio books.

1 Like
48

Is it possible the issue is just Appsupport not restarting correctly after a crash?

When looking into a high CPU usage issue, I killed the zygote64 process, which took down Appsupport with it, and a reboot was required to get it running again.

Killing zygote64 on version 5.0.0.68 also crashes Appsupport, but it starts up again when loading an Android app.

1 Like
49

You mean switching between networks e.g. from WiFi to LTE or between different WiFi SSIDs?

50

You might be onto something, I was getting crashes within minutes of starting appsupport. I tried turning off all my mesh wifi points except the main one and so far no crash.

Now I have to choose between shitty internet or constant reboots. Or I could simply never leave living room, I guess.

2 Likes
51

Yes, when I’m jumping between LTE and WiFi.
Just happened again, while being in the garden (on the edge of my WiFi range) and trying to get into rope flow.
BTW, I got it to work again by disabling the WiFi, ending FireFox, waiting for the stop button in the AAS settings and start it again. Had fun and can recommend the video: https://www.youtube.com/watch?v=3bNPNmgWu4o

52

I’ll have a look at the video later but for the switch between networks I recommend to switch mobile network and WiFi explicitly on and off.

What you will loose in convenience you will win in battery savings and privacy.

Happy new year.

3 Likes
53

With my 10 II on .71 when stuck with aas not starting when crashed after a few days of running fine - it seems to be fixed by disabling sharing media.
My guess, seeing some fix it by disabling autostart or crashes happening at issues with networking, is something has been changed in how aas reacts to system configuration. Probably to resolve the network issues?

54

My Xperia XA2 H3113 on 5.0.0.72 is also affected by this issue

1 Like
55

So far, I’ve only had the problem with the xa2 when switching from Wi-Fi to mobile data, not the other way around. From what you’ve written, it sounds like you’ve also had difficulties in the other direction?

56

Y’all might be interested in recent findings from this :thread: discovery props to @paulvt via @rainemak.

3 Likes
57

i can confirm that restarting apkd-bridge service FIXES the bug that makes me restart my whole phone to fix AAS.

specifically, for me:

  • appsupport crashes about 1.5x per day, and restarting appsupport does not work
  • logcat shows SurfaceFlinger failed to start repeatedly, on each AAS startup
  • no amount of reattempts or waiting seems to fix it, only cure is to reboot the phone
  • running systemctl --user restart apkd-bridge and then restarting appsupport fixes it instantly
5 Likes
58

[Release notes] Tampella 5.0.0.73 - Early Access claims this is fixed. On my device, I’ll maybe know later tonight. How about y’all?

1 Like
59

For me it’s fixed with .73 EA .

60

Have you tried turning on/off the wifi/data etc.? I’m not sure whether to update, especially because I have a freshly reinstalled phone and stopped before .72, so I don’t have the bug currently. Would hate to reintroduce it by updating.

61

So far stable, no issues.
I never faced a particular AAS problem when when moving in/out of WiFi coverage.
This update didn’t break anything for me, so far :slight_smile: