Completeness of protection, and usability tradeoffs for GrapheneOS

Because they want to receive notifications and calls from instant messengers / VOIP providers, or price alerts from stock trading apps, or calendar reminders, etc.?

I wonder what makes you think average Joes needs to get themselves ready to be raided and device seized for “cracking” by adversaries.

Reboot timer is good feature, it is good to ensure your device runs smoothly, it is good to mitigate firmware exploit, it is also good to protect your data in case of device loss / seizure, but that’s the final line of defense and whether it could save you depends on the situation, if you were contained by adversaries, it prob. won’t help you because the adversaries won’t need to break the device security, they only need to break you.

(relevant XKCD…)

And depending on the key disclosure laws in your country, you may not have a choice anyway.

An 18 hour reboot period is reasonable for people who use their phones once a day, and 12 hours is good for people using it all the time (accounting for sleep). Anything lower will just lead to inconvenience unless you ignore your calls/messages for hours anyway. If you don’t use your phone for days on end, 3 days is a good limit.

If you want to make sure your device reboots once a day then 8hours is a good idea, it would usually reboot while you are asleep. (I set to 8, but it reboots only once a week as I dont sleep well, might change to 4 to make sure it reboots. :rofl:)

Wish we could customise the time, i want it to be 6 hours.

Or it might be nice if you could set a schedule separately or in addition. For example, maybe one could keep a reboot timer for 4 hours but also force it to reboot at midnight as well.