• General

  • Screen sporadically doesn´t turn off automatically

BTW, is it possible that some app/service is keeping it on?
Is there some way to debug this.

Yep, updates did not help.

What screen timeout do you guys have? Mine is 15s, I think default was 30s. I switched to 30s now and I cannot reproduce this issue anymore. I will monitor the situation, maybe it shows up again.

    Is the common thread PROFILES? I used them months ago and had this issue too but stopped using profiles (removed them) and the issue stopped... hhmmmm... P7P.

    I also use profiles feature, but very rarely. Most of the time all profiles are shut down (except the main one).

    5 days later

    Lmao, I think I actually found a reason of this behavior without having any knowledge about Android internals:
    https://webcache.googleusercontent.com/search?q=cache:Ozf6weaaGNMJ:https://www.reddit.com/r/LineageOS/comments/uw5d8p/screen_timeout_issue_on_pixels_on_android_12/&cd=15&hl=ru&ct=clnk

    This is due to "ScreenUndimDetector.java" and seems to have started with Android 12 December update.
    If you undim the screen twice within 5 minutes, the screen is then kept on for 10 min.You can test this as follows:
    Set the display timeout to 30s
    Let the screen dim (but not turn off)
    Brighten the screen by touching it
    Let the screen dim again (but not turn off)
    Brighten the screen by touching it
    Now the screen won't time out on its own (for about 10 minutes)

    Could someone confirm? It really behaves like this for me.
    Maybe GOS devs can also take this patch? (Please)
    https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/333526
    Although it looks like useful logic to have, maybe it should be configurable in settings instead of being hardcoded?

    • asd likes this.

    Or actually, maybe it is better if user can just enable some toggle in menu to keep display enabled (on rare occasions when this is needed), without relying on this non-obvious logic.

    It is really surprising that this behavior is not mentioned anywhere else, not explained, has no visual feedback (when this mode is activated). I thought it was just hardware problem. Wtf google.

    2 years later

    Is there a solution for this? I am affected too. Can it be connected to a screen protector that's installed on the screen?

    • de0u replied to this.

      DeletedUser98 Is there a solution for this? I am affected too.

      The information earlier in the thread suggests changing the duration of the timeout setting helps. Is that relevant in your case?

        I will check, if that makes a difference. However, it would be kind of annoying if I can only set certain screen timeouts to get the screen locked reliably. I don't think its a hardware fault but I couldn't find out yet what is causing the issue. I did a factory reset and installed just a few apps after but it happens again. I cannot remember if the phone had this issue before using private spaces but that's just a random guess.

        Hi guys. I asked forum few weeks ago about another thread, reporting this as a bug because I found pattern how to reproduce it. Doesn't matter pixel model, or timeout time set. To reproduce it is this:
        Right before screen timeout, the screen will dimm brightness for short moment right before turn off the screen. In that dimm state, you tap the screen to reset timeout and wait again for timeout to dimm screen again. If you tap again the screen in that dimm state the second time, phone will prolong the screen timeout to 10minutes. This is however crazy. Why the hell is this not managed in settings? Why is this even here and turned on by default without user knowing, I don't know. Is this your issue guys?

          BRNko I can confirm this happening to my P6a exactly as you described. 2025011500 build.
          I would go as far to say this presents a security issue.

          • de0u replied to this.

              BRNko
              Thanks for sharing your findings. I've noticed that for quite some time but also thought it was a bug as I haven't found a way to reproduce it. Now I'm inclined to believe that this is a feature as @de0u pointed out.

              Although I'm used to manually turning off the screen every time instead of waiting for its timeout, as @DeletedUser64 mentioned - in some cases it can pose a security risk and agree it should be present/managed in Settings.

              • de0u replied to this.