Is it possible to delay post-update app optimisation?

spammy

Given that it's quite the stressor wrt CPU, heat and battery, is it possible to not do it en masse at the start of the next boot and instead perhaps when an app is first opened? Or maybe even in bulk but the next time it's in an idle and charging state?

It makes choosing to reboot post-update a bit of a lottery, as if I do it at the start of the day I can kiss goodbye at least 10% of the remaining battery before I have a chance to get to a charger.

de0u

spammy How many apps are installed? A 10% battery drop is a fair amount.

GrapheneOS

spammy We could add the ability to pause and resume it.

spammy

It says it is optimising 180 or so apps. The mildly annoying thing is that I can go through twice of these optimisations without having used a fair few of them, so it sometimes seems a bit redundant to do them eagerly.

Speeduser7533

Are there any security risks with pausing it until the phone isn't being actively used (i.e. at night)?

GrapheneOS

Speeduser7533 No, the apps just run slower until it's done as they have to be interpreted other than parts which were compiled by the speed-profile compilation during the Finalizing step or during boot for anything installed/updated after that's done. The initial speed-profile compilation only compiles the parts marked as hot by baseline profiles in the APKs and cloud profiles from the Play Store, which is generally a tiny fraction of the app. The compilation after booting the update compiles the whole app with certain exceptions such as skipping one-time initialization code or massive methods.

andrej567

not sure if it is possible to do but if the phone would be attached to charger, the optimization process would have a higher priority.. to have it finished asap.

It looks to me that when the phone is locked and screen off, the progress is much slower than when i try to keep the phone unlocked.

GrapheneOS

andrej567 To avoid wasting power unnecessarily, the optimizing apps process does not keep the device awake with a wake lock. It only runs while the device is awake for other reasons which is mainly when you're using it. It runs with a low priority in the background to avoid interfering with using it and doesn't keep it awake. Each time the device wakes up to do scheduled jobs, etc. it will make some progress.

spammy

GrapheneOS No, the apps just run slower until it's done as they have to be interpreted other than parts which were compiled by the speed-profile compilation during the Finalizing step or during boot for anything installed/updated after that's done. [...] The compilation after booting the update compiles the whole app with certain exceptions such as skipping one-time initialization code or massive methods.

Couldn't it be done on a per-app-first-opened-post-install basis? I wouldn't mind a "optimising app for first use" lag post update.

andrej567

GrapheneOS ok thanks for info. So to get rid of the progress bar asap, it should help to put the phone next to me and occasionally tap it to keep it unlocked and alive

spl4tt

GrapheneOS Omg, that explains why it's taking so long sometimes. If you can add a pause function, I'd rather prefer a "speed up" function, where the device is mainly focusing on that, so I can just leave it on the table for a few minutes instad of 30

Dumdum

andrej567
Its tedious and inconvenient but you can change the screen timeout in the display settings. Just remember to change it back after optimisation.

andrej567

Dumdum yes, I would forget to change it back, I'd do but after hour or two realizing I forgot.

Usually the update works this way for me - i wake up at 6, with update finished, reboot button, battery around 50-60%.
I press reboot and while eating breakfast I am touching the phone while it optimizes. Phone is on charger to get 80% battery when leaving home :-)

andrej567

spl4tt If I leave the cellphone alone, eg like this saturday, it took on pixel 7a with 80 apps around 5 hours