I prefer to update manually, and not super often. That means I usually have a screenful of apps to download when I do.
When I get started, there’s an “Update all” button. I tap it and they start downloading and installing, one by one (there is no parallelism as there is when updating from Oogle store and I see no option to enable it – are there any plans to provide this? Anyway, this is just apropos).
Then my screen sleeps – it’s bound to happen with the download size – and when I wake it up, there’s the same list of (remaining) apps, but no more Update All. Best I can do is to tap on each one in turn.
Am I doing something wrong? Or is this a work in progress?
Basically as LK mentions, the difference lies in an app being under /system/app or /system/priv-app and being in a user folder. System apps by default (most and foogle ones too) have all sorts of access and permissions. So they run even if your phone battery is dying to give you an updated app before your phone does a shut eye.
User apps may or may not have those built in. Especially F-Droid.
Along with battery optimization screen off settings are also there which affect few apps behaviour.
But again, as LK mentions, there is unfortunately nothing we can do about this.
I’m not sure if I wrote clearly enough: I have no objection to the nap itself. The problem as I see it is that Update All disappears in the process. If the Fdroid app can show an Update All button at the start, surely it can also do it when woken up?
