Screen Randomly Stays On Ignoring Lock

TestyYuba385

I have an intermittent problem where my phone, Pixel 6A, will keep the screen on despite me having a screen lock set at 15 seconds and not touching the device. It doesn't really seem to matter what I am doing, but I'll set my phone down and look at it a minute later and the screen is still on and unlocked. This doesn't seem to happen on any particular app, as its intermittent. I've had it lock and not lock on the same app seemingly under the same conditions, like having my keyboard open ready to type in a chat app. I recently factory reset my phone and didn't see the issue until I installed OpenVPN from F-Droid and then clicked a little banner in the app that said "Enable Notifications". That was the only thing I can think of that I did before this issue started again on a fresh install. Anyone have this issue, or any tips on how to figure out what is causing the screen to stay on?

de0u

TestyYuba385 I believe I heard here that if you use 30 seconds instead it works better.

csis01

Its definitely finnicky.

TestyYuba385

Thanks, I'll try setting it to 30 seconds or 1 minute, the way it is set by default. I think for a ROM whos sole purpose is security, this is a pretty big issue.

matchboxbananasynergy

It sounds like this is what you're experiencing, which seems to be an upstream issue not just affecting GrapheneOS:

https://github.com/GrapheneOS/os-issue-tracker/issues/1268

TestyYuba385

matchboxbananasynergy That's it exactly! So upstream means the issue is within Android and not graphene? Thanks for finding that, I searched a bunch and then came here as a last resort. Glad it's known and getting attention. I really appreciate the help!

matchboxbananasynergy

TestyYuba385 Correct, upstream means that it is an issue which also affects Stock OS, as a result of being an issue in AOSP (Android Open Source Project), which both Stock OS and GrapheneOS are based on.

GrapheneOS sometimes addresses upstream issues downstream (in some cases months before they're addressed upstream), but there's too many for our team to address, in addition to them being things that will eventually be addressed by the Android team, meaning that it is not the most ideal use of the project's development resources.

TestyYuba385

matchboxbananasynergy Gotcha! Thanks for your help and time, I love graphene. This is really the only issue I've ever had.