It's good to have an option like that, even being a default, but there definitively need a switch to disable that if it is your own will.<p>It's not even necessarily that good enough against cops, because in a lot of shitty countries, even some pretending to be democratics, not disclosing or at least inputting your password might be a crime severely punished.
If I'm not wrong, there was a guy that had to stay years in jail until he would comply with the judge order to unlock his device.
This is a Google Play Services update. For GrapheneOS users without GApps wondering: A similar feature is already built-in:
<a href="https://grapheneos.org/features#auto-reboot" rel="nofollow">https://grapheneos.org/features#auto-reboot</a>
Not bad. If I could make a feature request it would be something like, <i>After 3 days of being idle:</i><p>- [ ] Reboot<p>- [ ] Power Off<p>- [X] WIPE <i>triple opt-in</i><p>Maybe there is a custom phone OS for this that makes the phone act more ephemeral and network boot off my self hosted iPXE/immich server? A dumb smart phone so to speak. An ephemeral diskless phone.
Mine randomly reboots semi-periodically already, even when it hasn't been shown as having downloaded an update.<p>That said, I think this is a fairly good idea, although with the encryption stuff they do, this will cause people who rarely use their phones to miss calls and alarms.
I found that this saves a lot of battery. My old Motorola G5G is now sitting idle, and I had to charge it every 4-5 days. I found that if the phone is restarted and <i>NOT unlocked</i>, it will stay charged for more than 10 days. My best guess is that a screen unlock is required to start many of the OS-level services, which takes up all the battery.<p>If this is true, then the new update will save a lot of battery for those phones that are sitting idle.
> ...the new Play Services will limit that exposure to three days, even if it's plugged in.<p>This will be fun to track down after a long weekend in embedded devices once this android patch number is old enough to be baked into crappy payment terminals and mall kiosks.<p>Probably overall a good thing though.
The Ars article seems to be inaccurate. Here is what the release notes say:<p>> Security & Privacy<p>> [Phone] Enables a future optional security feature, which will automatically restart your device if locked for 3 consecutive days.<p>So it only "enables" a "future" "optional" feature.
So the phone will reboot it self, but...<p>1) There is no developer accessible API to allow app developers to create an app to allow me to script power options (example, as an end user I want to script a restart or shut down my phone nightly).<p>2) Asking Google Assistant will not restart or shut down the phone.<p>3) Apple and Android have made it harder to shut down the phone, requiring double key press kung fu to even bring up the power menu.
Samsung phones have had this feature for years. But it’s not what you think. Samsung phones gave you the option to reboot at various intervals because their phones would slow down over time and their solution was to allow the user to schedule a reboot. Now it’s.a security feature.
I just want software that will do nothing user-observable without me explicitly asking it to. No pop-ups, no suggestions, no automatic anything.<p>I don't know if it'll take a fancy buzzword or what. Unobtrusive software? Silent Software?
I'm surprised this is something taken seriously only now by stock android. Isn't it known universally that AFU devices are insecure? What's the point of adding strict password policies, biometrics etc, if data from a stolen phone can be (relatively) trivially be exfiltrated unencrypted?<p>Samsung's have had some feature that lets you set days of the week for the phone to restart (IME during early morning hours) automatically. It's not perfect but it's something. iOS seems to have some unclear logic to either restart or re-request password (not biometrics).<p>This should be standard
This feature is optional: <a href="https://support.google.com/product-documentation/answer/14343500#:~:text=%5BPhone%5D%20Enables%20a%20future%20optional%20security%20feature%2C%20which%20will%20automatically%20restart%20your%20device%20if%20locked%20for%203%20consecutive%20days." rel="nofollow">https://support.google.com/product-documentation/answer/1434...</a>
"unused"<p>firstly how about fixing software which forces 'inactive hours' yet reboots even when cpu is at 100% utilisation, and software which dims or locks a mobile screen during video playback, and soft/hardware which doesn't respect user-supplied suspend/standby timeouts in their power plans, and ....
« This actually caused some annoyance among law enforcement officials who believed they had suspects' phones stored in a readable state, only to find they were rebooting and becoming harder to access due to this feature. »<p>Wouldn't the phones run out of battery after a few days anyway?
Or do they keep them plugged in?
Can I configure this? In some cases I'd want the auto-reboot to be more aggressive (for example: after 3 hours). In other cases I'd want to disable the auto-reboot entirely.
> This actually caused some annoyance among law enforcement officials who believed they had suspects' phones stored in a readable state, only to find they were rebooting and becoming harder to access due to this feature.<p>Lmao.<p>> The early sluggishness of Android system updates prompted Google to begin moving parts of the OS to Google Play Services. This collection of background services and libraries can be updated by Google automatically in the background as long as your phone is certified for Google services (which almost all are). That's why the inactivity reboot will just show up on your phone in the coming weeks with no notification. There are definitely reasons to be wary of the control Google has over Android with elements like Play Services, but it does pay off when the company can enhance everyone's security without delay.<p>All the more reasons to move to AOSP forks.
Another shitty idea that makes life harder:<p>If you are in a hospital- your phone will reboot to pin level. So you need to unlcok it few times and wait 3 minutes before it becomes reactive.<p>Then all your alarms will not work.<p>They add crap like this, yet the stock calendar app needs a separate appto play music to warn you. This of course breaksafter a reboot..<p>My grandma has a second phone as backup - it will constantly reboot and will never be ready to be used the time it is needed - as a backup. Since it will keep rebooting and requiring a pin.<p>Who comes up with those anti user ideas?<p>That we will probably
be unable to turn off (or the option to turn off will disappear after few months). Also old people will not know how to turn it off
What if just while that occurs I need to make or receive an emergency call?<p>Sometimes it feels like tech is going backwards. Rather than rebooting, just develop a proper method to unload/uncache, without making a device useless while that happens. Or use that multicore arch to swap the “dirty” instance with a clean one, in realtime.
uhh, that's going to disrupt Briar Mailbox, which relies on an Android device to act as an always-on node. I really hope there is a way to toggle this.<p><a href="https://briarproject.org/download-briar-mailbox/" rel="nofollow">https://briarproject.org/download-briar-mailbox/</a>
More "security" bullshit when all they want to do is secure their control over us.<p>Not falling for it anymore. Fuck Google and the rest of Big Tech.
Wait, why is this presented as a good thing?<p>Why would I want my phone to auto reboot without my intervention? Never mind that it’ll never make three days on a single charge even if I don’t touch it.
Isn't this stupid?<p>Why not flush something properly in the RAM instead to wipe the "cached" secrets?<p>A full restart feels like an overkill.