Optimizing Apps during update takes very long time

spiral

I'm on TQ1A.230105.001.A2.2023010300

I first noticed a few weeks ago that during the update, "optimizing Apps" takes a very long time, much longer than it used to. It says I have approximately 300 apps and it takes perhaps 20 minutes to optimize for them.

This used to be a much quicker process. Did something change? Is this expected behavior or no?

Oggyo

spiral It happened twice for me so far. Can't find any pattern, tho.
Did it recently with the last update but not with the previous one.
https://discuss.grapheneos.org/d/418-special-permissions-and-battery-optimizations-reset-after-update/59

MetropleX

spiral GrapheneOS uses ahead-of-time compilation instead of just-in-time compilation the Finalizing step of the update process is supposed to compile apps you've installed and non-pre-compiled OS components (which are rare and have to do with upstream regressions in AOT precompilation support) but it regressed upstream and doesn't fully do it so we re-enabled the UI for showing users apps are being recompiled on first boot of a new OS version / after factory reset.

spiral

MetropleX
Thanks for the info!

hemlockiv

This might be a silly question, but why do apps have to be recompiled with every system update? This isn't something I've seen other (stock) OSes do, unless they do or completely silently, in which case itwould be nice if Graphene did that too...

matchboxbananasynergy

hemlockiv This way of doing it is more secure than the alternative. It also makes apps faster when you're actually using them.

hemlockiv

matchboxbananasynergy I like fast and secure apps. I wish Graphene could use the A/B update partition to optimize the apps. It might require an extra reboot during the update process, but on the bright side it would be completely silent and wouldn't make the phone busy for a long time.

Alternatively, let users delay and then manually start the app optimization process, so we could choose to let it run overnight.