Now maybe I'm missing something here, and after checking all the settings I'm at a loss. When plugged into the charger (wall or whatever) and the screen timeout kicks in, the phone won't go to sleep. Instead it just sits there on the lockscreen unless I physically press the power button and manually put the phone to sleep. This also happens when I press the power button to wake the screen but not unlock the phone to check new notifications. This doesn't occur when the phone isn't plugged in, but seeing as I sometimes leave my phone on charge overnight, I'm concerned about screen burn-in or other damage. Yes, I could unplug the charger but surely this is either a bug or a setting I'm missing. Any insight would be appreciated.
same problem here.
There's still alot of bugs in this phones software. They need to fix stuff like this.
Also the Aussie version reception drops out when connecting Bluetooth in car. That's a wide problem affecting a lot here.
At least I'm not the only one. Perhaps a visit to the official support page with a list of bugs is in order, although I'm sure they must know about some of them.
Same issue, it's so annoying!
Report to ColorOS Forum Community
not on mine! check inside Dev menu
"Settings" -> "Additional settings" -> "Developer options" - > 4th row: "Keep the screen on while charging"
To activate the Developer Options menu, go to:
"Settings" -> "Phone info" -> "Base band and kernel" and tap quickly 5 times on "Build Number"
dgardel said:
not on mine! check inside Dev menu
"Settings" -> "Additional settings" -> "Developer options" - > 4th row: "Keep the screen on while charging"
To activate the Developer Options menu, go to:
"Settings" -> "Phone info" -> "Base band and kernel" and tap quickly 5 times on "Build Number"
Click to expand...
Click to collapse
Thanks for this reply. I'm suffering from the lock screen becoming stuck on whilst charging, so I went through the steps you suggested. Unfortunately, my "Keep the screen on while charging" setting was already switched off.
Try a full reset
Hey guys. Same problem here on X3 Pro.
Anyone find a solution to this issue?
Someone said it would be the clock app from google, I uninstalled it, at the first attempt it seems that was the solution.
So it's long back bug in realme phones
Gt neo 2 same issues
Related
Apologies if this has been answered before, I've done plenty of searches, and can't find out how to do it.
On my stock HTC Touch Pro, if I don't touch the screen or keyboard for about 5 seconds, then the screen goes to a dimmed state. Is there a way to turn this behaviour off?
Cheers,
Steve.
Settings - System - Power - Advanced tab. All of the options are there...
There are no relevant settings there. There's only the "Turn off backlight if device is not used for x min" and "Turn off device if not used for x min" for both battery power, and external power.
I'm not talking about the screen going off all together, I'm just talking about it dropping to minimum brightness after a few seconds of inactivity. I've tried the "Auto adjust backlight" and "Dim the backlight if the device is locked" settings, and they make no difference.
Cheers,
Steve.
Settings>Power>Advanced>Walla
StevePritchard said:
There are no relevant settings there. There's only the "Turn off backlight if device is not used for x min" and "Turn off device if not used for x min" for both battery power, and external power.
I'm not talking about the screen going off all together, I'm just talking about it dropping to minimum brightness after a few seconds of inactivity...
Click to expand...
Click to collapse
Steve,
You should be adjusting the "Turn off backlight if device is not used for..." setting under 'on battery power'. This setting relates to the dimming of the screen (backlight). It's most likely that this is set to 10 seconds or something short on your device. Increase this to the longer duration that you would like.
FYI, the "Turn off device..." setting relates to turning off the screen completely.
Hope that solves your problem.
xzibitB
Thanks for the responses. I was being a little confused by the fact that a) it's not turning off the backlight, it's just dimming it, b) it was doing it while sat in its cradle, and those settings were unchecked, and c) it was doing it after 5 seconds, and not the 1 minute it was set to.
Fiddling with those settings seems to have resulted in the behaviour I'm after.
Thanks again.
Cheers,
Steve.
I have exactly the same issue, as does my g/f's Diamond. The screen dims after 7 seconds of inactivity. I know this because I've timed it. I have all of the advanced settings turned off so the device should not ever turn off the backlight or power off. I'd really like to be able to stop this as it makes reading or watching video on the device extremely annoying.
Steve, what settings did you change?
Thanks.
I *think* what sorted it out was changing the settings to new values, then selecting [OK], and then going back into the Advanced tab, and setting them to what I wanted in the first place - it was almost as if the changing the settings didn't stick until I had changed them to something else, and gone out of the page.
I hope this helps.
Cheers,
Steve.
Having the settings not "stick" is a problem I had with my Apache/XV6700 under WM5. There was a fix out there for this problem that I could never get to work, either. It finally got fixed with a custom ROM and stayed fixed under a WM6 custom ROM.
But now I'm pretty dismayed to see the problem back with the stock Fuze ROM and a slew of tweaks/installs -- just when I got the phone how I wanted it. Anybody have any new ideas on getting the change to stick? A registry edit or something?
i am having the sameissue as leeJS, i had none of the boxes set to dim or turn off, it would dim after 7 seconds. i tried multiple settings even checking all the boxes with over 2 minutes, the screen will still dim. any solutions?
On another fourm I came across a fix that works for me - I had similar frustrating problems
In HKCU\Control Panel\Backlight rename the folder Locklevel to Locklevelx (or something).
System recreates the locklevel folder with the correct locklevel key inside it (and doesn't keep changing it back)
S2U2 has a setting that dims the screen after 7 seconds... Do you have that loaded as well? If so, check you s2u2 settings...
Hi,
I encountered the same problem recently with ICS based roms: after I activate the Developer options / Stay awake option, the lockscreen just goes AWOL. No matter what I do afterwards (reboot, clearing the dalvik cache, unchecking this option), the lockscreen just does not come back. When I press the power button, the screen goes off but the phone is not locked. Any advice on this?
Is it everytime or just when you have recently locked it? Maybe u have got your android timeout function put too high or when you have Cm you put a tick at the Cm settings the part for tablets where you can switch your whole lockscreen off
If its every time then its possibly because the wakelock "keep awake" places may prevent lockscreen from activating as the screen isn't "turned off" as such.
Then turn off the things that prevent it from going to sleep mode
Guys please help me out. After waiting for a long time, I got my OnePlus Invite.
The phone is really good, especially the back, I really love it, specs are good and even battery lasts longer than expected
Everything's great except this one bug, a very annoying bug.
The phone very frequently, let's say, 4-5 times a day, fails to wake up and when I say 4-5 times a day, so believe me it's too much for me as I hardly use my phone.
NO matter what I try, double tap the screen or use the power button. The screen just doesn't response.
I can hear sound when I press volume keys, I hear the ringtones if someone calls me but the stubborn display just doesn't come back from sleep.
Ultimately I have to force restart my phone by holding the power button.
Things already tried
1. Disabled all the developer options, in fact, though I don't know how it happened, developer options are not even shown in my settings menu anymore. But I am getting the usual message "You are now 4 steps away from enabling developer options" when tapping the "build number".
2. Already disabled "Prevent from accidental wake-up".
This is just NOT acceptable on a brand new phone.
Please suggest.
P.S The phone is not even rooted.
Bump!
Anyone?
There are times I want to turn off the screen without stopping the video playing (so audio continues). I used to do this all the time with my Android tablet using bsplayer, but have yet to find a way to do this with the Surface 3. I have tried a couple different ways to do this, and the closest I get is closing the touch cover over the screen while Media Player Classic is playing, but it doesn't actually turn off the screen. It turns the screen off, but almost instantly MPC turns the screen back on, albeit the lockscreen shows. The two problems I have with this is that since the screen is still technically on it is still draining the battery, and after 10 minutes the playback stops completely. If anybody has a workaround that can help with this I would greatly appreciate it.
1. Go to Windows 8 Start Screen
2. Search for "Windows mobility center" and select settings
3. Click on "Windows Mobility Center"
4. There will be an option called "Presentation mode". Turn it off
I found this via a website. Need to go back home to see if it works.
TileCreator said:
1. Go to Windows 8 Start Screen
2. Search for "Windows mobility center" and select settings
3. Click on "Windows Mobility Center"
4. There will be an option called "Presentation mode". Turn it off
I found this via a website. Need to go back home to see if it works.
Click to expand...
Click to collapse
Nope. On my S3 the option isn't there.
TileCreator said:
1. Go to Windows 8 Start Screen
2. Search for "Windows mobility center" and select settings
3. Click on "Windows Mobility Center"
4. There will be an option called "Presentation mode". Turn it off
I found this via a website. Need to go back home to see if it works.
Click to expand...
Click to collapse
I do not think this does what you think it does...
On my Surface RT, turning on "Presentation mode" keeps it from going to sleep or turning the screen off... basically switches it to the equivalent of an always on power profile. Turning presentation mode off resumes the selected profile (in my case I left it with the settings it came with).
Presentation mode is great for doing the opposite of what the OP is trying to accomplish, without having the mess with power profiles.
http://www.howtogeek.com/howto/windows-vista/create-a-shortcut-or-hotkey-to-turn-off-the-monitor/ this helped me. I didn't want to stream video but I wanted to turn off the screen without putting the tablet to sleep when I closed my type cover.
Hi,
Some background :
I bought a used AT&T LG G4 H810 recently.
I've updated it from LP to MM using this method : https://forum.xda-developers.com/att-g4/general/lg-g4-h810-upgrade-to-android-6-0-t3323995
The problem bellow occured. So i then re-flash it with the last rom available using LGUP : http://storagecow.eu/Xda/LG G4/H810/AT&T/LGH810AT-01-V21y-310-410-JUN-20-2016-ARB03+0.rar
Same problem. I Also did full factory reset several time via the recovery menu & the phone menus.
Here are the symptoms :
If I select "Swipe" or "None" in the "Select Screen Lock" menu, I've got the error "Unfortunately, Lock Screen Settings has stopped".
If I select any other method, (Knock code, Pattern, PIN, Password), I can set them up but in the end the option checked is still "Swipe" and no protection on the lock screen.
If I try to access the Security options, I've got "Unfortunately, com.android.settings has stopped"
If I try to setup a "Basic VPN", same error as well (Network > More > VPN > Basic VPN).
If I try to disable "Google Play Games" or "Games Assistant", it prompt me to reset them back to stock version, and then the phone soft-reboot (It starts directly on the AT&T logo, not the LG Electronics logo, so I think it may just be the UI which reboots ?)
It seems to be security or UI-related.
Actually I didn't try these options when the phone was on Lolipop so it may be a hardware issue of some sort ...
I did a "clear cache" on the "Settings" app. I Also tried to "Clear data" on "Settings" aswell, but the button is greyed out and clicking on "Force Stop" closes the actual app manager so ...
Do you guys have any ideas on how to troubleshot these issues ?
Thanks a lot !
dsagilles said:
Hi,
Some background :
I bought a used AT&T LG G4 H810 recently.
I've updated it from LP to MM using this method : https://forum.xda-developers.com/att-g4/general/lg-g4-h810-upgrade-to-android-6-0-t3323995
The problem bellow occured. So i then re-flash it with the last rom available using LGUP : http://storagecow.eu/Xda/LG G4/H810/AT&T/LGH810AT-01-V21y-310-410-JUN-20-2016-ARB03+0.rar
Same problem. I Also did full factory reset several time via the recovery menu & the phone menus.
Here are the symptoms :
If I select "Swipe" or "None" in the "Select Screen Lock" menu, I've got the error "Unfortunately, Lock Screen Settings has stopped".
If I select any other method, (Knock code, Pattern, PIN, Password), I can set them up but in the end the option checked is still "Swipe" and no protection on the lock screen.
If I try to access the Security options, I've got "Unfortunately, com.android.settings has stopped"
If I try to setup a "Basic VPN", same error as well (Network > More > VPN > Basic VPN).
If I try to disable "Google Play Games" or "Games Assistant", it prompt me to reset them back to stock version, and then the phone soft-reboot (It starts directly on the AT&T logo, not the LG Electronics logo, so I think it may just be the UI which reboots ?)
It seems to be security or UI-related.
Actually I didn't try these options when the phone was on Lolipop so it may be a hardware issue of some sort ...
I did a "clear cache" on the "Settings" app. I Also tried to "Clear data" on "Settings" aswell, but the button is greyed out and clicking on "Force Stop" closes the actual app manager so ...
Do you guys have any ideas on how to troubleshot these issues ?
Thanks a lot !
Click to expand...
Click to collapse
I've seen this brought up a few times, Seems the only fix for it is getting a replacement device.
Sent from my iPhone using Tapatalk