Google rolling out auto-restart security feature to Android

You say security, I say memory leak fixer

CalyxOS has this too. Choose between 1 and 72 hours.
- GrapheneOS has had it at least a year or so. For that matter it could be pulled from there.
- Ive got mine set to 8, so it usually does it while I'm asleeo
  
  Yeah, I have mine set to 12 to be a little less tight. Not so short that it reboots on a regular basis, but I think 12 hours would be pretty short for a thief to get my phone to a cracker in time. (assuming they even have access to tools to crack modern calyxos) I always power off my phone off going through customs.

Already a thing on my phone, update happens and i wake up to my apps not being open.

Use "free" Google services so that any pseudo-governmental entity can get full access to your mails, backups, photos, contacts, location ... but worry about stuff in device memory. Yes. A sane approach.
- Google is one of the most security focused companies believe it or not.
  
  If you chose to trust them. Here's a dum-dum, kid. Enjoy your mama's cookies.

This sounds less like security
And more like a backdoor
- Leaving your keys in memory is the weakness that could potentially let authorities into your phone. This could harm people. If your phone has rebooted, and you haven't logged in yet, there are no keys in memory. That means your data is encrypted at rest.
  For the sake of comparison, this was also implemented in iOS 18.
  
  Thanks for the voice of sanity. There are so many people freaked out by basic security measures that it boggles the mind.
- The before first unlocked state is considered more secure, file/disk encryption keys are in a hardware security module and services aren't running so there is less surface for an attack . When a phone is taken for evidence, it gets plugged into power and goes in a faraday bag. This keeps the phone in an after first unlock state where the encryption keys are in memory and more services that can be attacked are running to gain access.
  
  So hourly reboot is what you're saying
- GrapheneOS has had this feature. Unlocking after a reboot is only possible with PIN. Also the RAM is wiped. This increases security and lowers the risk of attackers gaining access. Be it physically or not.
- Google can already push apps to your phone at will via their remote installation service. How does this create or open a backdoor?
- It's more like security theater if the phone doesn't have the latest OS and doesn't have the necessary hardware to block cellbrite in the BFU state
  
  What hardware do android phones not have making them vulnerable to cellbrite?
- I dump memory more often than you would think. It's usually not obfuscated or encrypted in any meaningful way even though it is fairly trivial to do so.
  It's good practice to scour through any bloatware installed on windows laptops. Since bloatware is generally written by the lowest bidder, you can find all kinds of keys and phone-home urls (sometimes with all the parameters) and other weird things. Just fire up a decent hex editor and search for strings in the dump file. You don't need to know jack about reverse engineering either.
  
  I am often working as reverse engineer professionally and I also feel that mindset is half the battle--a willingness to see everything as data and to look inside to see what is there. Like digital spelunking.