I’m running /e/ OS 2.9-a14-20250323478433-community on a Pixel 5.
Settings/Display/Screen timeout doesn’t work correctly if Screen Lock is set to None. The screen does timeout but then quickly turns back on. The display then endlessly cycles between off and on. Can anyone confirm this?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
I got Pixel 5 same OS version but I can’t follow your settings. Screen Lock is not just on or off there are several other settings included…
I don’t use screen lock. To me it’s an annoyance.
Ah I see now what you mean.
I have a lock screen, since some apps don’t work without it.
I will try to reproduce your explanation later
I have a OnePlus phone that has problems with screen lock set to none. The screen times out then wakes right back up. The only way I can get it to stay in sleep mode is with a button press.
And yes I agree screen lock is an annoyance. On my OEM Android phones I use it only to secure my Google Account. With /e/os I don’t have to worry about it since /e/os is not tethered to an account. That’s one of the big reasons I’m drawn to /e/os. With OEM Android your phone is an extension of Google Corporation, you’re subjugated by them.
In screen timeout I am offered; 15s or 30s, 1-2-5-10-30 minutes. I do not have the never option.
Running Moto 2021 Edged here.
I have a pattern as a lock and I turned it off and I think I was able to reproduce it. Pattern has a setting which locks the screen after automatically turning off in x seconds. It was set to 5 seconds.
I have set the pattern lock again and set to 0 seconds, disabled again the lock screen and than the screen wouldn’t turn on again.
Could you try that?
The None option is in “screen lock” not “Screen timeout.” The problem is if "screen lock’ is set to None the display doesn’t blank properly.
I much appreciate the pattern response but that seems a workaround. As others can duplicate this should it be reported?
Yeah it is a workaround, I agree.
Yes, should be reported to gitlab
https://doc.e.foundation/support-topics/report-an-issue.html
I can’t change “Screen lock” after setting it to Pattern. If I access Security & privacy and choosing “Device unlock” I see “Screen lock” Pattern. However, choosing the Settings gear doesn’t allow either changing or disabling “Screen lock.” What am I doing wrong?
On another front … I did report the issue using the provided link. Thank you.
Yoean the settings gear to change the amount of seconds, right?
Yes, but what I want is to simply turn Pattern off, not change the timeout. How do I set “Screen lock” to None or something other then Pattern? I no longer see that option.
You touch left from the settings gear
Although I implied so, it struck me I should confirm the quoted workaround above works well for me.
And, should anyone be interested, the progress of the bug report can be found at Issues · e / Backlog · GitLab.
I’ll be interested in whether this is an /e/OS or Android bug.
This issue has nothing to do with screen timeout. It has do with Screen lock set to None. Normally at the least you set a PIN during setup which Screen lock defaults to. In Device unlock settings there’s a Screen lock menu with various settings such as Swipe, Pattern, PIN, etc. There’s a None option there.
Selecting None skips the lock screen and the phone wakes directly to the home screen. This is where the problem occurs. With screen lock set to none, the screen goes to sleep after the selected timeout period, but immediately wakes and stays on until it times out again. So you get a presistent cycle where the screen flashes off for a moment at the timeout frequency.
Thanks very much.
I was wondering about the same. It doesn’t feel like a /e/OS issue but a AOSP thing.
I will compare it at a later point, I got a none /e/OS Smartphone.
@CraigHB I will show you a video of the behavior. Also good for the GitLab.
I’m thinking it’s an AOSP issue. If it doesn’t happen on Lineage OS which is where /e/os forks from, that would tell you for sure. At this point it’s not a huge problem for me since I run a long screen timeout and use the power button to put the phone to sleep.
Also /e/os is not my daily driver and is not going to be until I buy a new phone. The phone /e/os is on right now is pretty old and it’s an entry level model. If I had come across /e/os before I got a new phone and carrier late last year, I would taken a different tack on that. What I should have done was purchase a carrier unlocked /e/os compatible phone off the shelf. What I did was the exact opposite. The carrier gave me a flagship model phone for free with a new sign-up. It was a temptation too great, but then they have you by the short and curlies. I succumbed to the devil.
I could just buy another phone right now, but I can’t bring myself to spend money for a hardware downgrade just to run /e/os. On my own dime a mid-range phone is the best I’ll do. On the bright side this carrier phone is crazy fast even with all the crapware piled on it.
The insane level of garbage software I experienced when I got the new phone was what prompted me to look into /e/os. Google Play is a big part of it, but it’s everywhere from apps to system software. It’s simply not manageable especially the way Google will just do things off the wall without your consent like adding apps and changing settings.
It doesn’t happen on stock… must be LOS or /e/OS resp.