other8026 I'm going to have to ask you to please stop being rude to other community members.
OK, I agree and take these remarks back. Those were not intended to be rude as they can look, more like trying to convince. Sorry @nologo anyway.
other8026 You decided it's "not good" for yourself. Other people have mentioned unlocking with the primary unlock method once daily, which leads me to believe they're: not bothered by it, unaffected because they end up using their primary unlock method once daily for some reason, or are affected but are fine with working around the timeout.
Or they have short password. Or no password at all, like 4-6 digit pins instead.
The main problem that people like @nologo talk about some workaroundS, but none of them named any except manually daily entering password for no other reason than suppressing and avoiding this 48 timer. I ask several people and none of them named those "workaroundS". That is not a fair statements by them.
other8026 You have described the timeout as a "bug" when it isn't.
Well, for me it's the same as upsteam 8/16 char max length limitation for password. Is it a feature? Is it a security problem? Is it a bug? Chose yourself. I consider it to be a disaster. It was fixed by GrapheneOS, I hope the timer also would.
other8026 You've described the timing of the timeout as "random" when it isn't even after you were told how it works.
No, after the first post that stated that it's 48 hours - I agreed to believe in it and said about 48 hours a million times. But IT LOOKS random to the users. It's also a fact, because it happens at seemingly random moments (often when it is less convenient and safe to enter password). Why should it matter how it works inside, if for average user the moment is unpredictable (almost the same as random)?
other8026 It's considered "not good" by whom?
By me, and a few users just in this thread. People have changed the length of the password to shorter one due to this useless timer. It's a fact, we have such cases even in this topic.
other8026 you don't want to use it seemingly ever
No, not true.
I want it to use in cases:
- Getting from reboot (when data is at rest).
- When GrapheneOS auto-reboot timer works and saves my data by putting it at rest. It's a security measure.
Well, it's how it should work, this 48 hour timer is just a security problem that happens unpredictably for users.
other8026 you're unwilling to take a small and simple step to unlock your device with the secure and complex passphrase at least once every 48 hours
It would be even harder to keep track of 48 hours, so once 24 hours.
Yes, asking entering long password on awful android small keyboard is something I would love to avoid especially when it's COMPLETELY pointless from any security perspective. Is it not?
And yes, I would save 1-2 minutes a day, it's the same time we spend on our teeth each morning, it's a big deal not to be annoyed, knowing that this actions are made COMPLETELY FOR NOTHING.
other8026 you claim that using this long and secure password is so difficult that you and others may decide to make their long and secure passphrase shorter to to make it easier to enter
No, not "may decide", but "did decide": there are my and other examples in this thread.
Why "may", if it's a fact?
other8026 I'm not saying you're the only person who doesn't like it
Of course not the only one, there are a people just in thread.
Quantum In my country the police can force you to use your fingerprint to unlock your phone after a court has approved it.
So, set auto-reboot to 10 hours. It would be better in any possible manner. And you also can keep 48 hours timeout if you want (I propose toggle). But it does not mean that other people should be not able to disable timeout.