Password Timeout Bypass?

ZeptoBizmall

I set a strong passphrase for my second profile (I can access owner still) and promptly forgot it two days later. By yesterday I'd reached ₁₃₁,000 sec time out, BUT because of the automatic restart every 12 hours, I realized that the second profile was letting me try sooner than two days!
Following that, I thought maybe I could time travel and figured out that if I turn off all connections, turn off auto date/time sync, and restart the phone, the second profile allows me to try again and again and after guessing wrong, only going back to 131000ish secs for a time out which is circumvented by restarting the phone.

So, since I have not unlocked the profile still, my question is: is the mechanism to decrypt the profile already decoupled and the phrases I guess go nowhere or am I [very slowly] brute forcing my way through?

GrapheneOS

ZeptoBizmall You're wrong about what's happening and you aren't bypassing anything. This is not implemented by the OS but rather the secure element and has nothing to do with the real time kept by the device and synced with network time. Your attempt at unlocking after reboot is being rejected and you're being shown how long it will take before you can try again. You should read the relevant information in https://grapheneos.org/faq#encryption.

ZeptoBizmall

GrapheneOS That's what I figured regarding the clock sync. Thanks for confirming that. However, I still didn't find anything regarding this type of inputting password without it being used to authenticate (other than the min/max length that is mentioned).

So I'm confused about why/how it resets back to ₁₃₀₀₀₀ seconds? if this happens every time the phone restarts, then my previous tries that have timed me out more than 12 hours have been useless.

and why would the text box open to input after a restart if the system knows it's in time-out? Is this just a quirk?