Related
I know I know there are tons of topics about this
But here this out. I ve got the problem for about a week and hope some one can help me out.
After 30 secs my screen goes to dimmed-fase ( correctly as I setted )
And after 1 min. it suppose to auto turn it off but, it does try to by it only locks it down so the screen stays dimmed and doesnt go in standby ( total black screen and stuff )
Any one know what this might be?
Ive check the power settings and I have ticked the auto turn off after a ... minutes not used :S
So hope some one can help me out cause it drains my poor battery
sounds like a software issue, perhaps someone here knows the correct registry settings applicable to powersaving
I hope some one knows Cause I thought there were more folks that are looking for this
is it plug in for recharging? if yes, it's normal, during rechargind, it dimms out after 30 mins or so (please check both options, to dim out after 1-2 mins.)
Nope just normal use, so I sure hope some one knows the right registry setting to it
When plugged in USB and sync with PC, the Touch HD stays on with dimmed backlight. No matter how long the settings to turn off the backlight, the backlight still keep on its minimum level.
This is totally different with my Hermes, which the backlight can turn completely off after some time.
ahlok_hk said:
When plugged in USB and sync with PC, the Touch HD stays on with dimmed backlight. No matter how long the settings to turn off the backlight, the backlight still keep on its minimum level.
This is totally different with my Hermes, which the backlight can turn completely off after some time.
Click to expand...
Click to collapse
I noticed that happens even when using a bluetooth to sync. No matter cable or not, connected activesync keeps light on.
Arrggh? Does no one know the right registry key value to it ? its quit annoying
*bump*
Really no one knows anything about this
same problem for me
I use LumOS, are you using it too ?
I removed LumOS, and everything is good now
Do you have MobileMagic installed?
I did and it had 'Stay On' activated in its settings which meant it always stayed on!
Might be the case here too!
koxx said:
I removed LumOS, and everything is good now
Click to expand...
Click to collapse
Even if my HD has no LumOS or Mobile Magic (from hard reset), the problem (backlight stays on during USB sync) still exist.
P.S. My previous X1 has the same behaviour...
koxx said:
I removed LumOS, and everything is good now
Click to expand...
Click to collapse
Well I had it installed but I removed it later one cause I didnt liked it too much
But the problem still occurs so there most be a registry value that didnt change with the install :\ or something
I've looked up some registry value's but really dont know which one i've have to edit
or if I even have looked up the right one
BatteryTimeOut 30
BatteryTimeoutTemp 0
BatteryTimeoutUnchecked 0
Maybe some one that still has the function that the screen goes black after a while.
Can look up the registry value's ? here is the path I dont know if i'm looking at the right point:
HKCU\\ControlPanel\Backlight
Maybe some one is kind enough to list all of there value in this map ?
PS:
My problem is that my blacklight doesnt go fully to black and that's when using it normal. Not connected to anything or something .
It usualy goes to black after a XX amount of time. but that doesnt happen any more :\
Dang no one is offering his self up too look up those registery valves
Guys, the fix is simple. You must have turned on the Autolock feature using HD Tweak or Advanced Config.
If yes, just turn it off.
I have got the autolock function on, did it via HDtweak
Havent check it via Advanced config.
But I dont know what you mean with the last sentence?
Should I turn it on or off?
Edit:
Well dang you were right, i've turned off the autolock function.
And now the display does go to black.
But I find it strange that it worked nicely a few weeks ago and now the problem occurs
so any idea?
*bump*
still no one has found the solution?
wrong reply
Hello! I'm new but I have a big problem. In the enening when I go to bed I often turn off my Experia so I'm not interrupted at night and I can save my baterry. But the problem is that alarm in the morning doesn't want to ring and doesn't want to turn Xperia on back. I found recently the page on the web where somenoe said that it needs to be doen some hidden tweaks so that the WM doesn't try to look how full the baterry is before it sturts up. I can't find that page on the web again so can someone help me with this settings?
Than you.
use flight mode.
x1 cant wake up when off
I don't think any Windows Mobile phone is capable of waking itself up when it's powered down.
you probably use just as much power turning the phone on as you would have used leaving it in stand by..... just sayin'
OK, so I have tried flight mode and it works but anyway does anyone know the hidden settings to change verifiing battery from wm before it turns on again?
Oh, and another problem on my Xperia. I noticed that when I don't use it the screen (backlight) aproximetely every once in 2 minutes turns on again (my power settings are: turn backlight off after 30 sec, standby mode after 1 minute). I think that why battery last only 3 days. Can anyone know how to fix this problem? Thanks.
donci3 said:
OK, so I have tried flight mode and it works but anyway does anyone know the hidden settings to change verifiing battery from wm before it turns on again?
Oh, and another problem on my Xperia. I noticed that when I don't use it the screen (backlight) aproximetely every once in 2 minutes turns on again (my power settings are: turn backlight off after 30 sec, standby mode after 1 minute). I think that why battery last only 3 days. Can anyone know how to fix this problem? Thanks.
Click to expand...
Click to collapse
Change your configuration : Settings / system/ ilumination (check here the items you have enable or disable "enable ilumination".
Well basically, your device is off when you turn turn off the screen.
Not quite. You can always leave a lot of applications running with the screen off.
So what kind of setting to save as much as it can for battery or what kind of app du you recomend?
First, as someone already said, a WM device can not turn itself on when powered down.
To conserve battery... well just make sure no CPU intensive apps are running in the background, wifi, BT, data connection are off and use auto backlight setting.
Most smartphones don't turn themselves on for alarm (WM, UIQ Symbian, S60 Symbians), but i can't tell for all (iPhone does as i've heard, no idea about Android).
PDA is not Mobile Phone.
It has operation system etc.
To run PDA you need about 1 minute for loading all components of OS.
To run Mobile Phone Alarm needs no load components of OS, just display and sound.
In PDA sound can be played with help of driver and so on.
In Mobile Phone just tiny assembler program and clock-chip.
I know my alarm worked before with Touch-It rom. But since I flashed with WM6.5 and my alarm doesn't go off when the screen is off. There's no way around this?
I can't trust the alarm at all, it sometimes works, sometimes doesn't. Same on stock rom and 6.5. G-alarm is much better though..
Are you talking about turning the phone off completely,or turning off to the standby stage ? If you use the standby stage, it works fine, and hardly uses any power in this mode.
Hi to all,
i am running Essential ROM 1.7 (used to run X-Treme before) and on both of them my topaz activates screen every night exactly at 23:59. So it turns on, and go to sleep after 2 minutes (as set in settings). Anyone experienced this? I have bunch of apps installed and don't really want to try uninstalling all of them
Do you use G-Alarm?
Same problem to me and I use galarm.
It is something that G-Alarm does on purpose... If you go to the developer's site, it explains why.
"HKEY_CURRENT_USER\Software\ageye\G-Alarm"
Don't wakeup at midnight
Because of the Windows alarm bug, G-Alarm wakes the device at midnight so Windows Mobile can rebuild its notification queue. If you turn this off by changing or adding following registry value, it may happen that an alarm doesn't go off:
MidnightWakeUp: False
http://www.ageye.de/index.php?s=galarm/support/manual/hidden_options
Glad somebody else asked this, it's been bugging me for a few days but I never got around to posting.
I wouldn't mind the turning on, but mine doesn't turn off! I have my timeouts set to 3 mins for backlight and 4 mins for device (they're high because I use it to play Scrabble!) I've left the midnight thing on for as long as 10 minutes before manually turning it off. Any ideas?
Hi
I think that is poor programming, you can turn the phone on without turning the backlight on and this happens all the time many times a day.
Regards
Phil
Is there something simple that I am missing that someone can point me to? When I use GPS/Google Maps, the screen times out after the set delay (I have it set to 30 seconds) and I have to turn the phone back on again.
This never happened with my G1. When it was in GPS/Map mode, the screen would just automagically stay on.
i still have my eris (1.5) but i use keepscreen...
cliffy15 said:
Is there something simple that I am missing that someone can point me to? When I use GPS/Google Maps, the screen times out after the set delay (I have it set to 30 seconds) and I have to turn the phone back on again.
This never happened with my G1. When it was in GPS/Map mode, the screen would just automagically stay on.
Click to expand...
Click to collapse
didn't want to create a new thread, but did anyone find a solution to this besides keeping the display on when charging?
cliffy15 said:
Is there something simple that I am missing that someone can point me to? When I use GPS/Google Maps, the screen times out after the set delay (I have it set to 30 seconds) and I have to turn the phone back on again.
This never happened with my G1. When it was in GPS/Map mode, the screen would just automagically stay on.
Click to expand...
Click to collapse
Hello,
I've exactly the same problem. I tried keepscreen, it works, but I wanted to know if there was an other solution (without installing an application).
If somebody has a solution, it would be great
Screebl does what you want.
If you use the Navigate function the screen does not timeout. of course you can't be in any other app.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I thank you for your answers.
I've fixed the sod after flashing 2.14 radio on my tmous hd2. However, now when I return from standby, the screen turns on but I can't unlock it using touchscreen. I can unlock it fine if I enable the menu button, after which the touchscreen will still not work but menu button does. Then after about 30 sec everything works.
This problem only happens after being on standby for a long time, ie. 30 min plus. I'm using shubcraft rom.
Is this the freezing error from g sensor or something else?
Sent from my HTC HD2 using XDA App
I had the same problem... for some reason it went away on its own.... which probably means it will Come back on it's own but hey...
I'd look into the g sensor thing though.....
Sent From My Galleon By Trained Seal
Try waking up the phone with the yes/call/send/green key. (Instead of no/hangup/red/power key)
Also if you disable auto rotate from settings display, you won't get touch freezes because of g sensor. You can try it.
You can even disable g sensor completely if you want, but you don't need to as auto rotate fix works.
Please provide feedback.
I've uninstalled some programs and changed the settings and it seems to have gotten better. I put back on the auto rotation settings and so far so good, so I don't know exactly what did it.
Sent from my HTC HD2 using XDA App
You may also take a look at your setcpu profiles is yore using it. My screen off profile was set at 245/245 and I had a lot of wake-problems. I adjusted it to 384/384 and it is 95% better. The battery barely suffers. Just my .02.
Sent from my HTC HD2 using XDA App
Yea I have it at 384-245. It's not too bad lately. I've updated the kernel again, happened once recently.
Sent from my HTC HD2 using XDA App
I've noticed that if your wifi is set to "always on" i get this error consistently. It went away once I disabled that setting.