ieure All of us on the stable channel owe a debt to the intrepid volunteers who run alpha or beta to protect us from a bunch of bugs and a bunch more updates.

Thanks, alpha and beta users! What you do really helps the GrapheneOS team improve the user experience.

Stephan-P Only a few days later 20241104 comes along and the user base is presented with the first update fixing a couple of inhibiting bugs in AOSP plus some more.

It also bumped the security patch level which is significant.

I am very grateful to the devs to be so active in having the OS follow the pace of security updates and evolve in order to provide us with a more secure / more privacy-friendly device.

it is normal the phone is updated whenever there are new patches.
you can mitigate that if you want.. by :

only updating on unmetered networks but never connect to unmetered networks
only updating while changing but never charge
disabling auto reboot and reboot when you are free so it does not happen in the middle of a call or important game or whatever.

In my honest opinion, if u use GraoheneOS, part of it's strenght lies in updating asap when a update reaches stable...

ieure What's with "Optimizing apps," anyway? I don't recall any other Android install doing that. I don't understand what it's doing, or why it needs to optimize the same apps as it did 2-3 days ago.

A quick search on this forum brought this up: https://discuss.grapheneos.org/d/16429-what-does-optimizing-apps-do

An explanation as to what "Optimizing apps" is can be found here: https://nitter.poast.org/GrapheneOS/status/1845094724694073671#m

ieure while I personally share the opinion of pretty much everyone else that's commented (I always update my phone ASAP), I'm going to offer an alternative. It's your phone, use it how you want. You think the updates are too often? Disable automatic updates and check in whenever you like.

The best security advise is to keep your phone up to date always, but use it however you like. Realistically, even if you're one or two updates behind the rest of us, you're still better off than most.

If you enable 'Require device to be charging' and 'Automatic reboot' then you'll likely never see updates. Your phone will update itself while you sleep at night, assuming you charge your phone at night.

Viewpoint0232 Stupid question but if you enable "automatic reboot", will the alarm still go off in the morning?

grapheneos-enthusiast the alarm won't work if your phone is in BFU state (after reboot), that's why is not advisable to enable auto reboot if you rely on your phone for morning alarms

Yes it does, assuming you're using the included clock app and the owner profile to set it. Third party clocks can do it too, they just need to support direct boot. Secondary profiles are not suitable for this because they can't be started separately from the owner.

    spring-onion

    Thanks! Also, with automatic reboot enabled, what is meant with "automatically reboot once the device is idle"? For example, I'm using Foldersync to sync a couple of folders every night (or actually: when it's charging and connected to Wifi). Would that prevent it from rebooting because it's not "idle"? Or does idle basically just mean the screen is off and there's been no user interaction for a few minutes?

    Adding my 2 cents:

    GrapheneOS has 3 update channels, the "stable" channel normally gets an update roughly twice a month. I am on Beta, only Alpha updates every day.

    You can set automatic reboots and requirements for updates, so you could totally wait to reboot once the update is installed, and then the process starts if you dont need your phon.

    "Require the device to be charging" could be useful here.

    GrapheneOS ships updates like they are important, unlike nearly all other Android vendors. This is great.

    The optimization of apps after the update is (afaik) because Android apps use Java (not sure if exclusively, afaik there are rust apps) which is an interpreted language. That interpretation takes time and resources, so the apps are precompiled for your device which makes stuff smoother.

    The playstore does this too when installing apps, but only for code pages that are used very often, afaik.

    You dont need to restart the apps once they are precompiled. You can, but you can also totally wait until you want to.

    The "getting hot" must be a Google Tensor thing. My 7pro got incredibly hot too, my 6a doesnt. I hope they have fixed their chips when the 6a gets EOL 🥲

      My phone does not get hot at all while optimizing.
      Perhaps it depends on how many apps one has, and how bloated those apps are.

      I've never ever noticed mine being warm, with <90 apps (including stock apps) that are mostly lightweight and FOSS (minimal megacorp bloat) on a P7.

      missing-root . I am on Beta, only Alpha updates every day.

      Under normal circumstances, the betas and stable come at the same frequency as the alphas, but with a time delay.
      As they are the same updates and go through the release channels

      missing-root only Alpha updates every day.

      Not sure if I'm following you here. The alpha channel doesn't get updates every day.

      Maybe you mean that only the alpha channel may get multiple updates in a day or once a day for brief periods when the developers are busy updating and testing new OS releases, especially bigger updates? If that's what you meant, yes, that does sometimes happen. Anyone who has their phones set to the alpha and (sometimes) the beta channel, may get way more updates if there's a new release and an issue is found during testing and the release is cancelled and the issue fixed.

      missing-root The optimization of apps after the update is (afaik) because Android apps use Java (not sure if exclusively, afaik there are rust apps) which is an interpreted language. That interpretation takes time and resources, so the apps are precompiled for your device which makes stuff smoother.

      Here's a quote from the website about this:

      Android Runtime Just-In-Time (JIT) compilation/profiling is fully disabled and replaced with full ahead-of-time (AOT) compilation. The only JIT compilation in the base OS is the V8 JavaScript JIT which is disabled by default for the Vanadium browser with per-site exception support.

      It's not to make apps run faster, it's to make GrapheneOS more secure.

      missing-root The playstore does this too when installing apps, but only for code pages that are used very often, afaik.

      I'm not sure this is correct? GrapheneOS still "optimizes" apps when they're installed too, I don't know of Google Play doing anything like this.

        ieure

        im not a hacker, but let's say I were and wanted to compromise you

        this is how i would do it:

        1) social engineer you to open something to corrupt your system

        or

        2) look for either a 0day exploit (an unpublished software or os or firmware vulnerability) or unpatched vulnerability to hack you

        0day exploits are hard to find and cost money. governments hoard these when they can find them so their teams can hack people. most hackers don't have those or use them on high value targets

        unpatched vulnerabilites are easier

        you hack the published vulnerabilities that the developers openly say are dangerous and could lead to hacking and hack the person to too lazy to update their system

        patching vulnerabilities constantly and quickly makes #3 harder

        which means regular non-government hackers will have a harder time hacking you

        most hacking is done the first way these days it but 3 tends to be used for high value targets

        this is a lot of extra work for the developers to be always patching so fast btw