3 ms·
They stole the idea from GrapheneOS and shipped a barely half-baked version with hardcoded time. GrapheneOS has configurable time for it since years
by udev4096 2y ago
They stole the idea from GrapheneOS and shipped a barely half-baked version with hardcoded time. GrapheneOS has configurable time for it since years
- surajrmal 2y agoAs the article alludes to, Apple recently shipped the same policy to iOS so this is likely just following the precedent from them. Android developers don't pay attention to community forks.
- throawayonthe 2y ago[dead]
- mcraiha 2y agoCan you set the time to one minute?
- ThePowerOfFuet 2y agoWhy would you want it to auto-reboot after one minute? The minimum on GrapheneOS is 10 min and the maximum is 72 hours. It can also be disabled.
- devrandoom 2y agoNot against it, but I'm genuinely curious what the use case would be for that?
- amelius 2y agoI guess as a prank, just like setting the language to Chinese for English speakers.
- 67593874748 2y agoCould be useful in a scenario where you won't be using your phone often and really want to maximize battery life.
- gf000 2y agoA reboot will eat a lot more energy than a proper suspend.
- udev4096 2y agoNo, that is unrealistic. Please stop trolling
- II2II 2y agoHow so? The system only reboots once it has been locked for a particular duration. Setting it to 1 minute basically says: put the system into a more secure state (e.g. purge unencrypted memory) and ensure that it is ready to go when I next need it. That said, while it is not unrealistic it would be problematic since accidentally letting the phone lock (e.g. input timeout) would result in a time consuming reboot.
- OneDeuxTriSeiGo 2y agoGraphene's autoreboot has 12 different options (excluding disabling it) ranging from 72 hours down to 10 minutes and the timer is reset each time the device is unlocked. Tbh I think a 1 minute setting would actually be nice (for things like when you are going through customs, etc) but I get why they don't provide it.
- iancarroll 2y agoI would guess the more likely inspiration would be Apple recently adding this to iOS, if GrapheneOS had it for years and they didn’t add it...
- lysace 2y agoI'd claim that Microsoft pioneered this time limit security concept with Windows 95 almost 30 years ago. They went with 2^32-1 milliseconds or about 49.7 days. We don't talk enough about Microsoft's strong legacy of security innovations, IMHO.
- yalok 2y agoI’m not sure it was because they cared about security - looks more like accounting for 32-bit timestamp rollover would be very disruptive to the huge (legacy) code base and it was a quick fix to work around the problem :)
- IshKebab 2y agoIt was a joke.
- Dwedit 2y agoTo this day, some programs malfunction after 2^31 milliseconds have passed since bootup, which is the halfway point. Milliseconds since bootup has just become negative, and has not rolled over yet. Just having a negative number of milliseconds is enough to mess with those programs.
- rvba 2y agoMore like "innovation" that makes all those machines in factories break every 49 days.
- philistine 2y agoI'm pretty sure you're joking. Windows 95 crashed if you sneezed in its general direction, I'm pretty sure it would blue screen due to some edge case well before 49 days of runtime.
- lysace 2y agoNo joke. https://web.archive.org/web/20041207171440/http://support.microsoft.com/kb/q216641/ https://web.archive.org/web/20041207171440/http://support.mi... https://web.archive.org/web/20130731171959/https://sites.google.com/site/edmarkovich2/whywindows95andwindows98wouldcrashafter49.7daysofuptime https://web.archive.org/web/20130731171959/https://sites.goo...