[C2]Android App Support autostarts despite being disabled

Bug Reports
,
#1

REPRODUCIBILITY: 100% (always)
OSVERSION: 5.0.0.21
HARDWARE: Reeder S19 Max Pro S - s19mps - s19mps - 1.0.0.15 - aarch64
UI LANGUAGE: Svenska (user: sv_SE, os: sv_SE.utf8)
REGRESSION: yes (since: n/a - n/a)

DESCRIPTION:

Android App Support starts automatically on power on, despite being disabled in Settings.

PRECONDITIONS:

No Android apps installed, except F-droid

STEPS TO REPRODUCE:

  1. Go to Settings | Android App Support
  2. Uncheck Start AAS on boot
  3. Reboot

EXPECTED RESULTS:

Phone should boot with AAS stopped

ACTUAL RESULTS:

Phone boots with AAS started

MODIFICATIONS:

  • Patchmanager: no
  • OpenRepos: no
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

Edit to add more info from replies below:

Starting AAS during boot takes longer than when device is up and running
From visible Home screen until App Support runs takes about 2 minutes. The Top menu toggle flashes the AAS icon once during this time, then goes back to filled circle until the process is completed.

Once phone has completed startup (and of course having stopped AAS) it takes just half a minute for AppSupport to start again.

Is AAS starting or is status just incorrectly reported?
I waited until the Top menu item was a steady Android icon. Then I started F-Droid, which appeared immediately and without any extra notifications.

After stopping AAS, and again waiting until the Top manu item was steady, I started F-droid anew. This time I get a message saying “F-Droid will be started as soon as AppSupport is ready” (or similar wording) plus a noticable delay.

So I do think it is AAS actually autostarting on boot, rather than some internal state mismatch.

the initial version of this bug report was created using Bugger 0.9.10+git6
1 Like
AppSupports disabled still restarts on bootup (duplicate of 20633)
#2

Also reported by @pmelas with the following additional info:

1 Like
#3

Feedback in Top menu

  1. After the phone boots, but before App Support is running, the Top menu just shows a filled circle where the App support toggle is located.
  2. Edit: About half a minute before App Support is ready, the Top menu toggle briefly shows the AAS icon, then goes back to filled circle.
  3. Once running, the toggle shows the App support icon as expected.

Trigger from Settings?

I booted and did not open Settings, so I’m sure I didn’t trigger App Support to start that way. (Just opening the Top menu wouldn’t start anything, would it?)

Performance impact
It seems the phone is sluggish while App Support gets up to speed - and that takes a while. (edit:) From visible Home screen until App Support runs takes about 2 minutes. The Top menu toggle flashes the AAS icon once during this time, then goes back to filled circle until the process is completed.

1 Like
Feedback on Jolla C2
#4

I was about to post that bug when I saw this one. My impression is that it is not really starting but the status of AAS is still showing that it is starting. Probably some conflicting flags in different places…

#5

To try to find out, I waited until the Top menu item was a steady Android icon. Then I started F-Droid, which appeared immediately.

On my other devices, if AAS isn’t running, I get a message saying “F-Droid will be started as soon as AppSupport is ready” (or similar wording) plus a noticable delay.

So I do think it is AAS actually autostarting on boot, rather than some internal state mismatch.

1 Like
#6

Stopping AppSupport and then starting an Android app gives the expected “App will start when AAS is ready”.

The curious thing is, that it now takes just half a minute for AppSupport to start.