WM6 screen goes off after 5 Sec

[orexio8]

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.

[pauliusba]

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.

[orexio8]

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

[NiTroGenious]

Set these registry settings and you'll be fine:
[HKEY_CURRENT_USER\ControlPanel\Power]
"Display"=dword:0000003C

[HKEY_CURRENT_USER\ControlPanel\Power\LockLevel]
"LockLevel"=dword:00000000
The display will go off after 60". :)

[ericjm]

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.

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. :)

[NiTroGenious]

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". :)

[pauliusba]

That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...

[Exitao]

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?

[Exitao]

That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...

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.

[maciek1]

Look at this (http://forum.xda-developers.com/showpost.php?p=1430924&postcount=404). This is solution for your problem;)

[Quakie]

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?

:cool: Quakie

[qwsoftware]

I had this, I found a solution, delete the LockLevel key with a registry editor, reboot and the problem has never occurred again :)