This is doing my head in! I have the very same issue noted in this thread http://forum.xda-developers.com/showthread.php?t=901998.
A lot of the times I press the power button to wake the device it will show the unlock slider for a very brief second then the screen goes black (not off, it is on but black). Other times, when I press the power button to wake the screen will turn on and off a second after that. This leads to a very frustrating series of button presses until I can actually unlock the phone.
I tried setting the screen timeout delay to immediate as suggested in the other thread but that did nothing.
FWIW SetCPU will lock the processor between 125 and 245MHz when the screen is off, using a scaling of Powersave.
Any help?
Set the minimum frequency to 245MHz.
I have experienced severeal problems getting out of standby when having 128MHz as minimum. Plus, You don't really save anything on going to 128MHz.
That pretty much did it. Thanks.
end_of_message / COMPUTOR4500
Related
Hi, i have just got a new xda orbit and noticed that when the backlight goes off after a set period (30 secs), it seems to be still lit but only very slighty, so at night you still see the today screen etc. But if i press the power button then the display goes off. Is this correct ?
The reason im asking as i have been using an xda mini s for over a year and when the backlight times out the display is not visible at all in the dark. You have to press the power button to see the screen again.
Hope this makes sense
Yes, that is fine. The dim backlight will go out in time too.
MaskedMarauder is 100% right. It will go out eventually.
Ok thanks guys for the quick reply, just obsevered it last night and noticed it was different.
Thanks again...
I've tried posting about this before, but it never gets answered - i've got a mda III, and that dims to brightness 1 (from within the registry), but will never go out - regardless of what rom i've tried.
I've also noticed that i can force set it to 0 in the registry, but thats the overall screen brightness. None of the other reg keys (putting bkl1:, etc in the various power keys) seem to work.
Any one got any ideas or utils to sort this? I'd try to code this as there are some code samples which allow you to force this, but i've not got VS
Like you i've tried all the registry edits i can think off to no avail. I too have a wizard and find this irritating - plus backllight stays on when media player on etc.. No difference with wm6 so i guess it maybe a hardware issue. I use a small app to turn off display when apps are running and i want the display off.
I use backlight time of 30 secs and power of 1 minute - so overall similar to my wizards backlight time of 1 minute.
why not..
why not just pres the I/O button on the side to turn off the backlight when u don't want it on? obviosuly a bit of a hassle, but if u get into the habit of doing it, no problems
Because that puts the device into standby and turns everything else off too (except the phone etc.) So if your listening to music your plunged into silence.
I had an XDA2i (Alpine) previous to my Orbit and I actually prefer the dimmed screen.
A brief press on the 1/0 power button WILL make the device go into standby.... BUT...
press and HOLD the power button for LONGER than 2-3 seconds and it toggles the backlight on and off, whilst STILL keeping the device on!
hope this helps
Joe
I'm on a g2, running cm7.. when ever I hit power button to put phone to sleep, the phone light goes black.. that's normal, obviously... but when ever I tick power button to awaken it, the home menu back and search keys light up but the screen goes black. Ill have to press power off and on button like 6 times for the screen to actually show up.. each time, quite annoying..
Any idea y? Thanks guys!
are you overclocked?
screen on/off animations?
using setcpu?
I've had some issues with screen on not responding as it should, and this is what fixed it for me:
-lower overclock (I was at ~1.3 ghz, went down to ~1.0ghz)
-disable screen on/off animations
-change setCPU from ondemand to interactive
obviously, what worked for me may not work for you.. but you might give that a shot.
I have mine set to performance? I don't really know the difference.
However, I don't use setcpu, I use cm7 settings the one that gives you the "warning this may cause blah blah blah when changing settings)
But I have it set to 1ghz.. ill test it though thanks!
I have almost the same problem but mine does that once in a while. The phone is not rooted. So I don't use set cpu or anything like that. The problem that I am having is when I turn the phone on (after it is shut down) it does not display the htc logo, then when it gets to the g2 it does not display that either. When the finishes turning on the screen is still black. I can press the digitizer where I know the unlock is and I can feel it vibrate then when I unlock it I can still feel it vibrate when it unlocks and it takes about 2 to get the screen on from this just pressing the on and off power button. Some1 please help.
Sent from my T-Mobile G2 using XDA Premium App
Well it turns out it was because I set it to powersaver, I set it to interactive and it works great now! I noticed my web browsing speed increased to. No more slightly lag scrolling/zooming... maybe perfomance govern is to fast?
I notice performance made quadrant skip cpu and go straight to graphics and data write and scrdw up the test, and even youtube videos would play like 2 seconds, to 8 seconds, and skip all the way to the end, with choppy playback..
Emulators ran flawless at 1.3ghz hooked up with wii remote.. dk country 2 is epic
This is something I've had pretty much since day one from what I can remember. Basically, sometimes the screen won't come on but the buttons light up. I press the power button again to 'lock' the screen, give the screen a hardish smack and then press power as normal to wake the screen and it comes on fine.
Is this SD card related or something else?
No suggestions??
I had it a while ago, where the SetCPU was set on smartass and minimum frequency to 128 MHz. Sometimes it did not turn on. Other than that, no idea.
Don't use SetCPU or anything like that, does it when stock as well...got a new SD card on order so will give that a go
hi, as described, it happens to me... annoying a resolve this with spare parts by enabling "animation windows" from off to all
hope this help
i have the same problem...i can't even reboot when it happens, have to take the battery out
I fixed this by rebooting or flashing the rom again.
Sent from RCMixS
Anyone experiencing this? I had the setting to be 30 minutes of idle would lock the phone (using the pattern lock).
After 4.1 my phone now locks whenever I use the power button with the same 30 minute idle setting. It's really annoying and defeats the purpose of having a timer lock the phone. The only option would be to let the phone screen timer idle out every time.
Not sure why this would change or if my phone is bugged.
There's a setting (in Security if memory serves) to lock the phone instantly if the power button is used. Did that get set during the update, perhaps?
smelenchuk said:
There's a setting (in Security if memory serves) to lock the phone instantly if the power button is used. Did that get set during the update, perhaps?
Click to expand...
Click to collapse
that options doesn't seem to have its own setting any more. It is however built into the lock screen timer - the top option is to have it lock at idle out or power button. From there it goes down in increments like 1m, 2m, 5m, 20m, 30m.
I have it set to 30minutes and also checked the security options - there isn't a separate option to lock with power button that I can find anymore.
Hi guys, I bought a new zenwatch and am experiencing a weird issue. Occasionally, when the watch is in ambient mode, it is not responsive to touch. I turned off wrist gestures to wake up the device, and need to tap it to wake up. Sometimes I tap it and nothing happens at all, it stays in ambient mode. Pressing the power button at the back will wake up the device and it will function normally. It is just slightly annoying to have to press the power button which is on the back a few times a day. Any input to why this might be happening is appreciated.
I have the same problem, but sadly no solution. I've had the watch since Jan and it only recently started doing it, last month or so
At least its good to know I'm not the only one, probably a software bug.
Mine does that occasionally. I find that rotating it back and forth a couple of times (even though Tilt to Wake is switched off) before touching the screen clears it.
Mine did that just a little while ago. I do still have tilt to wake turned on, though, and after waking once that way, it's back to responding to taps now.
Also, selecting a different watchface from the phone seems to clear it.
Pretty sure it has something do to with the latest update. Maybe they are using more aggressive power saving settings on the cpu governor, making it take longer to ramp up clock speed and be responsive.