matchboxbananasynergy on Nostr: npub1ndrz9…ckalv If you are referring to the auto-reboot feature, it's not a ...
npub1ndrz95w58vvrxc0j4q3svmxhz8xev53zn55wq6qwd96mdd4eyvasackalv (npub1ndr…kalv) If you are referring to the auto-reboot feature, it's not a feature that's implemented as a security feature in most other cases.
On GrapheneOS, the auto reboot feature kicks in after a predetermined amount of time (18 hours by default, but can be adjusted by the user or disabled if wanted) without a successful unlock. That puts a timer on the attacker before the phone is at rest, which makes exploitation basically moot.
Samsung and some other OEMs have features that reboot the device, but it's not implemented as a security feature. It only kicks in when the device meets specific requirements such as being idle etc., which an attacker could easily prevent. With GrapheneOS' feature, if they don't know the password to unlock the device, they can't prevent the reboot unless they have an OS exploit.
On GrapheneOS, the auto reboot feature kicks in after a predetermined amount of time (18 hours by default, but can be adjusted by the user or disabled if wanted) without a successful unlock. That puts a timer on the attacker before the phone is at rest, which makes exploitation basically moot.
Samsung and some other OEMs have features that reboot the device, but it's not implemented as a security feature. It only kicks in when the device meets specific requirements such as being idle etc., which an attacker could easily prevent. With GrapheneOS' feature, if they don't know the password to unlock the device, they can't prevent the reboot unless they have an OS exploit.