Related
hi got Tornado imate sp5m i ve flashed the rom with WM6 Perfect English after flashing i seems corrupted it gets freeze if i dont use it for several hours and when use it the screen goes off every 5 seconds with an annoying chime and tried Vanila aswel but getting the same problem.
Note: After Clear Storage it works fine again for sometime. i have T9English and Sp5m Buttons Installed nothing else
Any Solution
i ve format my phone installed GSM update and then WM6 and followed step by step.
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
yes it doesnt care about time management it got its own time well much annoying thing is it hangs sometimes and i found no call is recieved when it seems hang
did u Clear the storage ? the problem seems solve but for a while
Set these registry settings and you'll be fine:
Code:
[HKEY_CURRENT_USER\ControlPanel\Power]
"Display"=dword:0000003C
[HKEY_CURRENT_USER\ControlPanel\Power\LockLevel]
"LockLevel"=dword:00000000
The display will go off after 60".
pauliusba said:
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
Click to expand...
Click to collapse
screen goes off after 7 seconds only after the keypad is locked (that's the best i can do to prevent screen from lighting when the joystick is accidentally toggled inside your pocket for example). but if it is not locked, (in my experience) it corresponds to the timeout set under power management. but still i will check on that.
This display timeout behavior is normal for WM5/6.
In [HKEY_CURRENT_USER\ControlPanel\Power] there is usually only one key when the keypad is unlocked. The "Display" key stores your normal timeout setting in seconds. When you lock the keypad, the "Display" key is set to 7 seconds and your normal timeout setting is set to a new key called "TimeoutSaved". When you unlock the keypad, the "TimeoutSaved" is deleted and the "Display" key is set to your normal timeout setting. So far so good...
But, there's also another key in [HKEY_CURRENT_USER\ControlPanel\Power\LockLevel] called "LockLevel". It seems that it controls the normal Display/TimeoutSaved behavior. It's normal value is "0". But some times it is changed (I think AutoKeyLock and LowLevel have something to do with it) and set to "3" or "4". All you need is reset it to "0".
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Just to point out, Nitro's registry settings appear to be in hex, whereas most ROMs I've used show it to me in normal numbers (is that binary? because I thought binary was only 0 or 1).
Either way, 0 is 0. I wonder if it's possible that this key should be in hex and the keylock programmer used the wrong way to enter info, or maybe vice versa but still wrong data?
pauliusba said:
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Click to expand...
Click to collapse
It's actually 7 seconds and you have to power off your phone, wait a minute (or two) and start it up again.
This is a really common problem/question. If you had used the search you wouldn't have had to post and wait.
Look at this. This is solution for your problem
Possible cause
I think I may have found what is causing this issue. I noticed that if I let the keylock program run, it changes the backlight, etc to timeout and go black in about 5 seconds. I have to go into config and change it to a higher number, then back down to what I want it to be.
It got to the point that just had to disable that keylock program, otherwise, I have to constantly reset the power management settings.
When I don't have the keylock program running, the timeouts all work as advertised. Strange, eh?
Quakie
I had this, I found a solution, delete the LockLevel key with a registry editor, reboot and the problem has never occurred again
When I am on a call the backlight on my Touch Cruise turns off - I don't mind this. The problem is that when I try to turn it back on it is extremely dim (even if the backlight setting is "bright") and I need to use "Adjust backlight" to make it brighter. In sunlight this is almost impossible to do since I cannot read the screen. Even after I readjust the brightness, whenever the backlight turns off and I turn it back on, the backlight is dim again.
I have tried renaming the \HKCU\ControlPanel\Backlight\LockLevel folder to LockLevelx - this has not worked.
I have tried setting \HK:M\Drivers\Builtin\RIL\EnableFastDormantDisplayDuringCall to 0 - this has not worked.
Help please!
Do you have this problem all the time or you can see this misbehaviour just now?
I'm asking, because this could be caused by some other software you installed on your device,
which does some "things" with the backlight or some call manager like PhotoContacts etc.
This happens all the time. It does not happen after I soft reset the device until I use the phone. As soon as I use the phone the backlight turns off and is dim whenever I turn it back on.
- Are you running some "cooked" unofficial ROM?
- if you are using HTC Home, try to deactivate it, just choose some different homescreen schema but not HTCHome, make a soft-reset a try it.
- check HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel\LockLevel - this should have the value 0
- running standard ROM
- deactivating HTC Home doesn't help
- LockLevel is set to 0
This periodically happens on my device too. And it's really, really annoying. I found that one way to make it go back to 'normal' for a while is to change both lock levels (in locklevel and locklevelx to value 1) then back to level 0 (including the waiting and the soft resets) and then it seems to go back to normal again.
what seems to set it off for me is using the call history to dial a number, but this is sporadic.
Thank you Marissa and Hujer. Unfortunately both your suggestions have not worked.
I have had the same problem. What helped in my case is deleting locklevel and locklevelx from the registry and then soft reset. Worked for me!!
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
sclhtc said:
Thanks Tim B but that did not work either. If I soft reset my device OR delete locklevel & locklevelx and soft reset, then the backlight comes back on at the correct level of brightness....until I make and end my first telephone call - then the backlight only comes back on dim. By the way if I delete locklevel, it stays deleted until I make and end my first call - then it's in the registry (with value 0) again.
Click to expand...
Click to collapse
Exact same happens to me, using Bepe 64 rom. Real pain in the neck.
Possible workaround
This sounds very much like the same problem Trinity users have faced since that device was released. Try searching the Trinity Forums. There was a reg fix...something to do with "fast off" or similar.
The workaround there was, after the phone call, to press the power key to put the device into standby, and then when it wakes the next time the backlight is restored. Try that anyway.
No luck with this either.
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Tim B said:
I now have the same problem. My earlier solution (delete locklevel and locklevelx) is not working anymore. There must be someone who knows how to solve this.
I am willing to do a hard reset but then I will have the problem again that after turning the phone on when it is locked the display is not readable.
Any good solutions??
Click to expand...
Click to collapse
Exact same happens to me, using official rom.
I had to do a double reg edit, try this which is what I use:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableFastDormantDisplayDuringCall"=dword:00000000
[HKEY_CURRENT_USER\ControlPanel\Phone]
"Sleep"=dword:00000000
Reboot!
Thanks but that didn't work either.
Just to be clear I do not mind the backlight staying on, dimming or turning off during a call but when I press "Call End", the backlight dims (which I do not want) and if the backlight turns off after a call it is dim when I turn it back on (which I also do not want).
Did anyone find a solution to this?
Have tried all the things on here, and some work for a little while, but then the problem reoccurs
Wow, this is so strange. Mine comes back on at the same brightness level.
You all are experiencing the same thing as Marisa?
It is an odd problem because it seems that it occurrs all of a sudden out of the blue.
One time you make/receive a call and afterwards, even if the call was only a few seconds, you terminate it and the screen either is already dim or then dims and will stay dim unless you hit a backlight changer. Even then, if you lock the phone, or the phone dims after your prescribed time, it then stays dim. The only way to temporarily fix it is to set it to the normal level and then soft reset. It will then behave properly until the next phone call.
It is very inconvenient as if it locks while this is going on, you can hardly see to unlock it.
I have trawled the internet for hours looking for solutions to this. The Kaisertweak does not work for this on this device (don't know why!) Installed Schapps but the very tweaks I need do not appear when installed on my device.
All the registry edits don't work. In fact when I go to do them, the value is already at the recommended value anyway. Renaming locklevel seems to work sometimes for a while, but then reverts back.
I think it is more a problem of undimming than dimming. It dims when I expect it to dim, but does not light up again afterwards. The Kaiser solution of pressing the power button or d-pad to do this does not work on the Orbit.
I have a fairly non scientific feeling that it's something to do with either Shell, Pontui or Co-Pilot. I have uninstalled Shell & Pontui, but it has made no difference. Makes no difference either if HTC Home is/isn't installed/running.
Another strange thing is that when it is in its dimmed state, I only have to touch the page where the backlight slider is for the light to come back up. I don't need to touch the slider at all, it's already where it should be, 3/4 of the way up.
In fact I have done the registry tweak which is supposed to stop it dimming during calls altogether, and checked to see that it 'took' and it is still happening.
Somewhere, there must be a registry key or somesuch which controls what happens after this "temporary" dimming, which says, the call is over/the device is unlocked - go back to prescribed brightness. But I can't find it.
This is a really insidious problem which drives you mad, especially when you are out and working, you don't have time for this nonsense. If all else fails in a week or so I will try a hard reset, i just don't have time right now.
Any help gratefully received.
I have just emailed O2 with this problem. Let's see when/if they reply.
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 tweak my HTC touch HD by change certain registry value for performance purpose. I found that, after changed, my mobile would fail to boot (stop at window green screen). I am not sure whether it takes longer time to boot. However, I used to wait for > 10 mins but still retain at same screen.
I got to soft-reset my mobile again by press the red button under the cover. Usually, only the 3rd soft-reset would be successfully. Once boot ok, the subsequence soft-reset would be fine as well.
Question, is behavour normal, by design or any problem to my mobile?
Please advice. Thank you
You have corrupted your registry it sounds like. Change back the keys to what they were before (if you can remeber), else you need to do a hard reset.
joel2009 said:
You have corrupted your registry it sounds like. Change back the keys to what they were before (if you can remeber), else you need to do a hard reset.
Click to expand...
Click to collapse
Hi,
What do you meant by corrupted? If you are refering to wrong key value, then I can say the value it correct. Even though I change back to original, it still need to reboot for 3 times. The key point here is, whenever that is any change to registry, 3 times reboot would be required, 1st time freeze at window splash screen. 2nd time usually freeze at "Loading TF3D ..."
I was thinking whether WM would cache anything during soft-reset if nothing change. If any, then it need to "clean" and reload everything or ...
Any ideas?
Thank you
Corrupted as in the Registry files where not correctly backed up by Windows Mobile. Not your fault perhaps.
Just be sure not to reset to quickly after aplying changes to registry.
and maybe backup and hard reset to maintain functionality
I hope someone here can help me. I ran App2Date on my HTC HD2 where it became unresponsive, so I killed it. In hindsight, this was a foolish mistake as now the auto keylock on the phone doesn't kick in. If I leave the phone, the screen will dim, but it will stay like that instead of moving on to the lock screen. If I press the lock button, it will do so, but it is a pain that it doesn't do it automatically any more. I have since ran App2Date successfully all the way through, but the autolock problem is still there. I have the following registry settings set, which appear correct to me:
HCU \ ControlPanel \ Keybd
DefaultKeyLock=1
DeviceLockWhenSuspend=1
FrontKeyLEDEvent="IconLedOnEvent"
InitialDelay=375
IsUnicodeFromKeybd=0
LongEndFunction=1
MuteSwitch=1
RepeatRate=8
ShowWarningMsg=1
I have rebooted several times. App2Date must suspend the keylock while it is running, but does anybody know how it does this? I don't really want to have to factory reset to get out of this.
Thanks,
Cosmosmoss.
Just in case somebody has the same problem, it turned out to be a simple case of changing Settings -> Sounds & Display -> "Turn off device if not used for ..."