Why haven’t you updated yet ? If it doesn’t appear do it manually, download this, brax3/iode-7.2-20260131-brax3-ota.zip · master · ota / release · GitLab and do a local update.
I installed the 7.2 update a few days ago and have not noticed the phone prompting me for my password which is what it does after it shuts down and restarts.
Maybe the update fixed it.
I hope that too! I upgraded to 7.2 on Thursday and my uptime says it’s been going 38 hours now!![]()
[deleted as redundant]
You may be reading much more into my statement than what I was trying to say.
I use a fingerprint to unlock my phone.
After a restart, it will not let me use a fingerprint to unlock the phone.
It requires a pin.
The phone has not prompted me for a pin (that I can remember) since the 7.2 update.
Also, I do not use a SIM in my phone.
[deleted as redundant]
You are completely misunderstanding me.
I do not have an issue.
7.2 seems to have fixed the phone randomly shutting down and restarting.
Ahh, I get you now, misread your prior post…
You can’t compose ideas on text, you start like having a problem and then you end up that you don’t have a problem but the way you phrase it seems like the problem is that it doesn’t ask you for a PIN.
The last senetece seems like you give extra information for your problem.
The way to do it is to clearly state initially that the problem was solved and then describe the situation, the information about the SIM is irrelevant.
Wow that’s great have you noticed any other down sides to upgrading I know @george above basically said it’s a no brainier to download especially if you had the problem of reboots but have you seen any other errors since upgrading? Did the Iode OS team release anything about if the reboot issue causes DM-verity corruption or was it another problem altogether?
The 7.2 upgrade seems good and stable-I’m almost at 4 days now since the upgrade and my phone hasn’t spontaneously rebooted. Uptime shows 90 hours.
this is normal and expected behaviour. After a reboot Android always asks for a pin / passcode, rather than biometrics, for security reasons. If it’s NOT asking your pin (both SIM and OS pins), then that means it’s not really rebooting, but doing something else, which would be troubling, if that’s what you mean..
Yes, exactly ![]()
Yep, mine is doing the OS PIN okay, but hasn’t done the SIM PIN since 7.0, when rebooting. Only a full shutdown will trigger the SIM PIN lock. Hasn’t changed with 7.2…
FYI…
I was having random Brax3 reboots until I updated to iode 7.2. I’ve gone a full week without a random reboot. Hope I didn’t jinx myself! ![]()
I don’t recall having a random reboot since updating, but I just checked my uptime and it says 22 hours. I don’t recall rebooting manually yesterday so I’m not so sure the problem is solved for me. I’ll have to pay closer attention. Unfortunately android periodically requires re-entering your pin if you normally rely on fingerprint so that makes it a little harder to notice if a reboot happens when you’re not paying attention.
I’ve been off the forum for quite a while, and have been experiencing the lockup/reboot issue described in this thread - although not when it’s sleeping. Issue started with v7.1 and has continued with 7.2. I listen to pre-downloaded podcasts while driving and it will just freeze, diagonal screen images as described above accompanied by a ‘pop’ in the speaker, and then reboots. Daily occurrence. No app changes since before 7.1 (other than regular app updates) and apps worked fine previously. I first thought that the next OS update would fix whatever was exposed, so I waited w/o commenting. Worse, new with 7.2 my tuta mail app will no longer run at all and the phone won’t even let me post an error log to tuta. @plamen, has your side discussion with iode yielded any insights? Any suggested fixes available? I’m a simple user and I respect all here who dive into the weeds to find solutions and workarounds, but I don’t aspire to that sustained level of engagement. My hope is to just have a device that reliably makes calls, plays podcasts, and allows occasional web browsing, privately.
Try a factory reset. It can be a hardware issue because the problems have disappeared for most users.
It seems the 7.2 fix made improvements that reduced the amount of reboots, but didn’t fix it entirely.
A new fix is coming in 7.3
