Just upgraded to Windows Mobile 6.1, and for whatever reason, if my phone is unlocked and idle, it no longer goes to "sleep." Instead of the backlight turning off like in WM6, the backlight goes full brightness and displays a white screen. Has anyone seen this before? Any workaround/fix?
Thanks!
Sounds like you got the wrong display driver for your phone. What phone and what ROM are you running ?!
yrsmart said:
Just upgraded to Windows Mobile 6.1, and for whatever reason, if my phone is unlocked and idle, it no longer goes to "sleep." Instead of the backlight turning off like in WM6, the backlight goes full brightness and displays a white screen. Has anyone seen this before? Any workaround/fix?
Thanks!
Click to expand...
Click to collapse
I've had this problem before!
It happened when I was playing with the power management settings in the Registry. I found if I then locked my phone (e.g. long press of hang up button), the screen would time out and go completely white on full brightness.
To fix it was easy enough - just change the power management reg keys.
Once I screwed them up soo much I had to do a hard reset so watch out before playing.
Mine has been doing this also, I believe it may have something to do with the Light Config option in CeleTask. Will test more
uccellino said:
I've had this problem before!
It happened when I was playing with the power management settings in the Registry. I found if I then locked my phone (e.g. long press of hang up button), the screen would time out and go completely white on full brightness.
To fix it was easy enough - just change the power management reg keys.
Once I screwed them up soo much I had to do a hard reset so watch out before playing.
Click to expand...
Click to collapse
And what should I change the power management reg keys to?
Could you give more detailed instructions, including which keys to change, and what to change them to?
Thanks!
theformula said:
Mine has been doing this also, I believe it may have something to do with the Light Config option in CeleTask. Will test more
Click to expand...
Click to collapse
Yes I believe so too because it only happens when I use the low light option as well.
first off try....
go into power management under settings.
1. backlight time out on battery should not be set to never.
2. backlight time out on AC could but it still will turn off after the time period you have set for the next setting.
3. Display timeout- will turn off the display off completely after the time period set here.
1 and 2 low dim the screen prior to setting on 3
turn lowlight off... it hardly ever works. lol
I am running CM 6.1 Stable, and have been for a while, yet this issue just popped up a few days ago.
I cannot get the phone to auto shutoff the screen when idle. I have it set to 5sec off and 1 sec lock, (down from 30 sec off, 5 sec lock before).
I have looked at the stock settings and all are in order.
The only thing different is I was trying to play with the setting on my Alarm Clock Plus regarding screen setup, but have reverted to original settings and even rebooted several times with no success.
Anyone else having issues with this? Any way to enable screen off again without having to flash a recovery?
It's really killing my battery fast!
Thanks for you help!
Crey23 said:
I am running CM 6.1 Stable, and have been for a while, yet this issue just popped up a few days ago.
I cannot get the phone to auto shutoff the screen when idle. I have it set to 5sec off and 1 sec lock, (down from 30 sec off, 5 sec lock before).
I have looked at the stock settings and all are in order.
The only thing different is I was trying to play with the setting on my Alarm Clock Plus regarding screen setup, but have reverted to original settings and even rebooted several times with no success.
Anyone else having issues with this? Any way to enable screen off again without having to flash a recovery?
It's really killing my battery fast!
Thanks for you help!
Click to expand...
Click to collapse
In the android display settings, 15 seconds is the least amount of time to turn off display. how is yours set to 5?
In cyanogenmod settings, theres options to tell the lockscreen to kick in after the screen has automatically turned off and when the user has pushed the power (sleep) button. what is your time set to in the android settings? (settings - display - screen timeout)
Nissan350 said:
In the android display settings, 15 seconds is the least amount of time to turn off display. how is yours set to 5?
In cyanogenmod settings, theres options to tell the lockscreen to kick in after the screen has automatically turned off and when the user has pushed the power (sleep) button. what is your time set to in the android settings? (settings - display - screen timeout)
Click to expand...
Click to collapse
Um....finding rock, and hiding underneath it!!!
Turns out I am a moron that can't read.....but I swore that I had the display set to 30 sec....It was disabled. I will test again, over the next few days if for some reason it reverts to disabled.
Thanks!
Crey23 said:
Um....finding rock, and hiding underneath it!!!
Turns out I am a moron that can't read.....but I swore that I had the display set to 30 sec....It was disabled. I will test again, over the next few days if for some reason it reverts to disabled.
Thanks!
Click to expand...
Click to collapse
Lol no prob. Happens to the best of us!
[Q] [Idea] Overclocked and have the "wake-up and screen stays black" problem?
I'm running CM6.1 and using Pershoot's kernel, and running at 1.5ghz, on-demand. Probably once a day, I have the issue where a call will come in, or I'll press the power button, or I'll slide out the keyboard, and the screen will stay black (though the backlight for the soft-keys does come on).
I noticed that I can appear to interact with the screen still (answer a call by swiping where the answer slider is, even though I can't see it), which indicates that it's simply the backlight not being turned on.
For others that have the same problem, the next time it happens, try pressing your camera button to open the camera application. For me, the screen comes right up as soon as the application opens (the camera application sets your backlight to high while in it). Anyone else?
I'm going to take a look at the wakeup code this afternoon, I have an idea for a _hacky_ fix that can be done.
I also wanted to confirm - do others have the same problem if not overclocked?
I've been getting that a lot too before (more than once a day for 2 weeks) until I got desperate and wipe/reflashed CM6.1.1 and I haven't seen it in the last 3 days.
I don't know anything so maybe its coincidental. My OC settings are the same as before. The only difference this time was i wipe/factory reset before flashing CM6.1.1.
instead of flashing CM6.1.1 on top of CM6.1 which was what i did 3 weeks ago.
What does your setcpu profiles look like? Set a profile for when you turn the screen off to set the cpu to 245/245. Then set a new one at xxx/806 conservative (xxx being the freq you desire)
Test it out and let me know how it works out.
PanCubano,
Others have suspected that it has to do with the CPU being at high speed the split second before you wake the device, and I agree that it's likely the problem.
Unfortunately it's quite hard to prove that the problem has gone away.
Hi everyone!
I've installed Myn's Warm Donut and it works, but when i lock the phone with power button i have white screen! I've tried all panels! What can i do?
Thanks for the answer!
When you lock or when you turn the screen on again?
EVERY android kernel has a bug with screen wake up. If, in your case that happens, its perfectly normal, that white screen stays for like only a second and then android lock screen shows up. Press menu key and ur device will unlock. Sometimes that white screen stays, in that case just press Menu color again if that white screen still stays, you need to change the panel. Its impossible that white screen stays for infinite time. Mind to have a radio version greater than 1.65
dark_prince said:
EVERY android kernel has a bug with screen wake up. If, in your case that happens, its perfectly normal, that white screen stays for like only a second and then android lock screen shows up. Press menu key and ur device will unlock. Sometimes that white screen stays, in that case just press Menu color again if that white screen still stays, you need to change the panel. Its impossible that white screen stays for infinite time. Mind to have a radio version greater than 1.65
Click to expand...
Click to collapse
ah ok...the situation is exactly as you describe! I thought it was an only mine problem! Thanks!
i have the same bug. what panel works fine?
sicstifor said:
i have the same bug. what panel works fine?
Click to expand...
Click to collapse
Colours messed up?
white screen keeps there FOREVER?
Its time to change panel, try using Type 1 first, later try type 2 and type 3 is for exceptional cases
Every kaiser device has different panel type. Mine, HTC TyTn II KAIS130 has panel type 1 and another guy over here has same device he's using Panel 1 too. Warbyte has KAIS130 as well but he's using Panel 2. Its you who figure out that THIS panel is not working fine, lets try another. At maximum u understand it after two tries. And mostly you get a fine screen with fine colours in first try.
Only CHANGE panel if that white gibberish screen stays on for ever.
hi, im running android off my memory card and ive noticed a big battery drain, what do i need to do to fix that.
independent said:
hi, im running android off my memory card and ive noticed a big battery drain, what do i need to do to fix that.
Click to expand...
Click to collapse
Disable Location feature, disable GPS Satellites, set Screen brightness to minimum. Keep Wifi off, disable Automatic sync, keep your memory clean and use a task manager, use 2G mode if you are not using 3G. Disable Data connection and enable it only when needed
I have auto dimness unchecked, and whenever the brightness is set to over 55%, after unlocking the phone it always auto dims byitself.
Is this normal? no other phone does this. Can this be bypassed somehow? It's jarring when you unlock and see a bright vibrant screen and all of a sudden it dims like 10% or so after 5 seconds.
Phone auto dims when it starts to heat up regardless of your settings.
Otherwise it shouldn't as long as it's not set to auto brightness.
nadram said:
Phone auto dims when it starts to heat up regardless of your settings.
Otherwise it shouldn't as long as it's not set to auto brightness.
Click to expand...
Click to collapse
Ok, but when the phone hasn't been used in 30 minutes, and not "hot" at all, this still happens. This also happened with the G3 as well.
Is there a way to turn this off? This post has over 100 views, can everyone please comment if their screen does the same thing? Are there any solutions?
What carrier/model do you have?
I just tried this on mine, Verizon, 611A software.
With Auto Brightness disabled, set to 40%, I powered off, turned it on, then unlocked. The brightness did not change. Then set it to 100% brightness (Auto still disabled), and did the same thing. Again, the brightness did not change.
I have, however, seen the screen brightness reduced when I'm using Auto Brightness. If I turned it off in a bright area, then unlock it in a dim area, the screen will be bright for a moment, then will turn itself down, presumably based on evaluating the current ambient brightness.
RedOCtobyr said:
What carrier/model do you have?
I just tried this on mine, Verizon, 611A software.
With Auto Brightness disabled, set to 40%, I powered off, turned it on, then unlocked. The brightness did not change. Then set it to 100% brightness (Auto still disabled), and did the same thing. Again, the brightness did not change.
I have, however, seen the screen brightness reduced when I'm using Auto Brightness. If I turned it off in a bright area, then unlock it in a dim area, the screen will be bright for a moment, then will turn itself down, presumably based on evaluating the current ambient brightness.
Click to expand...
Click to collapse
auto brightness is always off. It's the AT&T non rooted stock version. I just tuned brightness to 70%, powered off, powered on, and after unlocking and opening chrome it auto dimmed within 5 seconds.
Does it do it if you don't open Chrome?
I've seen apps make their own brightness adjustments (like a camera app that maxes out the screen brightness when it starts up). I want to say that Chrome (on my last phone) is one of them. Alternately, turn it on, unlock, wait 15 seconds, THEN start Chrome. If it still happens right after Chrome loads, then it's a Chrome phenomenon, not a just-turned-on phenomenon., and at least you can isolate what to chase down.
RedOCtobyr said:
Does it do it if you don't open Chrome?
I've seen apps make their own brightness adjustments (like a camera app that maxes out the screen brightness when it starts up). I want to say that Chrome (on my last phone) is one of them. Alternately, turn it on, unlock, wait 15 seconds, THEN start Chrome. If it still happens right after Chrome loads, then it's a Chrome phenomenon, not a just-turned-on phenomenon., and at least you can isolate what to chase down.
Click to expand...
Click to collapse
Yes it dims even if I don't use chrome. No matter whats on the screen it dims a little after 5 seconds.
TheNamelessMan said:
I have auto dimness unchecked, and whenever the brightness is set to over 55%, after unlocking the phone it always auto dims byitself.
Is this normal? no other phone does this. Can this be bypassed somehow? It's jarring when you unlock and see a bright vibrant screen and all of a sudden it dims like 10% or so after 5 seconds.
Click to expand...
Click to collapse
Download LUX (couple of bucks) set it to manual, 100% brightness on all LUX setting areas and it will bypass LG's lame attempt to hide the fact that they can't make a phone that doesn't suffer severe battery drain and overheating.
Your problem is called High Tempurate Thermal Mitigation (throttling). I depise it but with LUX, I tell the phone what is acceptable to me, not the other way around.
If I wanted to be dictated to like a submissive I'd just get an iphone.
I don't doubt that excess temps can cause the phone to adjust its behavior. But that quickly after turning the screen on? That seems really fast for something to go over-temperature, and for a sensor to also detect it that quickly. You may be 100% right, it's just not something I'd expect to happen that quickly.
This is a serious suggestion, despite how it may sound What if you put the phone in the fridge for 15 minutes or so, then do the same test? Does the screen still dim after 5 seconds? Depending on the humidity level, the phone could start to condense after coming out of a cold environment, so use your best judgement.
For a "safer" test, hold it in front of an air conditioner for a few minutes, with the screen off. Then, still at the A/C, turn the screen on, and see if it immediately dims.
If it suddenly runs for a while before dimming, then I'd agree it's likely temperature-related. If it still behaves the same way, then perhaps it's a different cause.
Either way, Lux sounds like a nice addition to these phones, from everything I've read. I've just been too cheap to try it yet But the rather coarse auto-brightness from LG has me curious.
TheNamelessMan said:
Ok, but when the phone hasn't been used in 30 minutes, and not "hot" at all, this still happens. This also happened with the G3 as well.
Is there a way to turn this off? This post has over 100 views, can everyone please comment if their screen does the same thing? Are there any solutions?
Click to expand...
Click to collapse
Have you tried the cool-down suggestions (fridge, A/C,) ?
Try installing ThermoCF to monitor the battery temperature. I find that when used for GPS (mounted on windshield) the screen will dim with direct sunlight. The temperature is in excess of 120 °F when this happens.
I just left the G4 screen on 50% brightness for about 5 minutes and the temperature remained 98 °F (this is on a wireless charger, next to a warm laptop fan exhaust). I switched to 100% brightness and the battery temperature increased to 100 °F over the next five minutes but no dimming has occurred. After a few more minutes the temperature dropped to 99 °F with the screen remaining at 100% brightness.
Different from your problem but: I turned on the developer options and set the screen to "always-on when charging" and have noticed that the screen dims after some amount of time (I haven't timed, maybe 15 minutes or so). I ended up here because I was looking for a way to change that time and may download the LUX app to do it.
Nice to know I am not the only one having this problem. I use my phone to play Ingress and sucks the battery dry faster than anything. The screen kept going dim as I was charging.
I also have this same issue on my G5. I've tried the Lux, free version, and it still dimmed on its own. I wonder if the paid version will help out my situation?
Sent from my LG-H830 using XDA-Developers mobile app
I like the auto-dim, and my phone seems to accept manual "guidance" as to how I prefer the auto-dim to work.
What I mean is that I can manually bump up the brightness slider (while auto-dim is checked/enabled), and the phone will auto-dim using the brighter setting. Or, I can bump the brightness slider down, and auto-dim will remember that and adjust the brightness.
So it's like you can control the baseline setting for auto-dim by using the brightness slider with auto-dim enabled, and then the phone will auto adjust from that baseline. I play ingress and during the day I bump up the slider, but during the night play I'll decrease the slider and still enjoy auto dim both ways, and preserve the most battery that way.
Aint looked to see if g4 has got it. I know g3 you go into hidden menu. And turn the thermal mitigations on and it stopped the throttle down. Lg has an insanley low throttle down temp.
TheMadScientist420 said:
Aint looked to see if g4 has got it. I know g3 you go into hidden menu. And turn the thermal mitigations on and it stopped the throttle down. Lg has an insanley low throttle down temp.
Click to expand...
Click to collapse
Under what setting is it on the G3 so I can check the G5?
Sent from my LG-H830 using XDA-Developers mobile app
dmarco said:
Under what setting is it on the G3 so I can check the G5?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
On the g3 and g4 its under main hiden menu. I use shortcutmaster to get to them all. But the g4 the options not there. Im not sure i dont know anything about the g5. Im not interested in it at all. I am selling my g4. So i can get another g3.
Now i know theres an app 3ctoolbox. And in cpu settings you can modify the unclock temps i dont know if it does the screen.
So, the hidden menu in Marshmallow, here it is folks. Where would I be able to find the option to turn off screen dim do to thermal mitigation? Anyone have any ideas?
Sent from my LG-H830 using XDA-Developers mobile app
Mine also started to auto dim with auto brightness off. I have the H812 from Bell . I'm sure that on mine it's the proximity light sensor that is faulty or in the software. Because when i turn on the phone while blocking completely the proximity sensor it doesn't dim anymore. (knock knock doesn't work while sensor is blocked) but problem comes back if i wake up the phone without blocking the sensor. I have tried it many times and it's the same thing over and over.
Calibration in the hidden menu doesn't fix it, Lux and many other brightness apps iv'e tried don't fix the problem lol
I also use lux with cf.lumen
Lux will manage the auto brightness as per your preferences because i found the stock LG screen was about 15% lower than id like in all environments.
Cf.lumen actually changes the colour of the display rather than applying a dumb screen filter on top for night viewing.
The only thing Lux does for me is dim the screen twice since the phone already dims by itself 3-4 seconds after the screen is turned on. I can guaranty it's not an overheating problem, even after 30 minutes in the fridge it does it. I'm tempted to have the proximity sensor changed but will most likely wait for LG to release 6.0.1 to see if it will fix it.
Nougat 7.0 is days away and still no 6.0.1 MM for the G4. Pardon my language but LG really sucks . This is my first and last LG phone