Does this mean I can delete GCam Services Provider once the update hits the stable channel?

    @Themble @[deleted] Just to reiterate what's already been said on the auto reboot 72 hour default value. Auto reboot only kicks in after the phone has not been successfully unlocked for the set amount of time. In practice, almost nobody is going to leave their phone locked for 3 days straight without ever unlocking it once. If you somehow only check your phone only every 4 days, you can adjust the auto reboot timer or turn it off completely.

    So, while this will realistically affect almost no one's regular usage, it will be very useful for putting all of your data back at rest to protect it in cases where your phone is stolen/seized or anything like that. It is actually a significant security improvement to the defaults of the OS.

      Nice work!

      If we already set a shorter window for the reboot time (under 3-days) ... will this update respect the prior setting? ... or will it overwrite to 72-hours?

        brookie229 If you rotate devices often, I suppose that you turn them off to save energy and respect the environment. So that should present no problem.

        When will be the monthly sec. patch available? Usually it's on the 1st Monday of the month, but since it was delayed on the previous month, maybe it will be delayed again. Any info?

          • [deleted]

          Regarding to this new added feature:

          Dialer: add modernized call recording implementation using modern Android storage (no files permission) and with unnecessary cruft removed including not locking availability or playing a recording tone based on region (users are responsible for respecting regional laws including informing the other party or obtaining explicit consent if required)

          Aren't the audio files playable from the calls history?

            Just got it.

            For giggles, I set auto reboot to 12 hrs, to see if it’s too big a pain in the hoohoo.

            Blastoidea
            I don't think it's released. I'm talking about Pixel security patches by Google.

            dc32f0cfe84def651e0e That is completely expected. eSIM activation is still the same as it was before (requires Sandboxed Google Play in the owner profile as well as the privileged eSIM activation toggle to be enabled).

            The change here is that the eSIM firmware updater app is no longer gated by that toggle and enabled by default with these new improvements, which is important, as it... well, provides firmware updates to those components.

            It is possible that in the future there will be an open source Google-independent way to activate eSIMs as well, at which point the privileged activation toggle would be done away with, but alas, that's not today. :)