Database Info

Help..Jasjar going into auto powersave and no response on button press.

Greetings,
I just upgraded to the 2.02.00 ROM last night but still have the occassional lockups. I need to do a soft reboot to get the phone to respond. I believe when it locks up, the radio is still running since I see the blinking Green LED for the GSM. I have to switch off the POWER MANAGEMENT option of "Turn off in x min in not used" for battery power to be able to use the device for calls. The only level of battery saving I am stuck with now is the Backlight auto-off and the beam settings.
Is this something others are having as well or are any applications the culprit?
Thanks in advance for your assistance.
Regards
BHAMEED
------------------------------------------------------------------------
I-Mate JASJAR
--------------
Windiws Mobile 6 (CROSSBOW)Jwright
OS 5.2.318 (Build 15341.0.0.0) AKU 0.0
CE ROM Version : (2.02.00 WWE)
RADIO Version : 1.13.00
ExtROM Version : (2.03.05 WWE) UNLOCKED
Bootloader Version : ver 2.01

Try the power button

All buttons..including the power button...no response.

try holding down the power button
or setting the backlight to atleast one notch.

Urm... uh... ah.... eeee... aaaaaaaaaaaahhhhhhhhhh.

I can confirm this behavior on my MDA Pro (G3).
All ROM versions the same like Bhameed's on my MDA, ...except bootloader of course.
Anyone else noticed this on 2.02.00?

Hold on, can you guys be more specific with this? Are you absolutely sure it doesn't come back on when you PRESS AND HOLD the power button??? Really sorry if I sound like I'm being pedantic, but just from what you've written it sounds like you don't know how to turn on the phone???

hahahaHAHAHA!!! awesome reply spyder
ok, yeah i was thinking this is an issue of not being able to turn on your phone.
yeah what's going on that was different from before?

There have been only few moments where you think "Surely not"... I hate those moments, I'm just hoping this isn't one of them! If it is a genuine problem it's pretty serious and needs to be addressed, but if not.... well, I don't think I should say much more
Please please please say this is all a big joke. I'm tired, please excuse me.

I confirm this behaviour!
And more!
My Qtek freezes... freezes... and then PUFFF. Dead.
I wait some minutes (30 minutes) and I can turn it on again.
I'll send it to qtek.

Mine has a thing sometimes where there will be a pause between pressing the power button and it coming to life... sometimes if I get impatient and press the power button again it will turn it back off before it's come on.
I don't really get it though. Does it freeze while it's still on, or while it's turned off? If it freezes when on, there's plenty of info about how to prevent freezes (mostly 3rd party apps + reg tweaks).
If it really does freeze when off, then please let us know anything more on the issue that you can.

SpyderTracks said:
Mine has a thing sometimes where there will be a pause between pressing the power button and it coming to life... sometimes if I get impatient and press the power button again it will turn it back off before it's come on.
I don't really get it though. Does it freeze while it's still on, or while it's turned off? If it freezes when on, there's plenty of info about how to prevent freezes (mostly 3rd party apps + reg tweaks).
If it really does freeze when off, then please let us know anything more on the issue that you can.
Click to expand...
Click to collapse
Mine freezes everywhere. Bootscreen, Pin code menu (when u type your pin). It depends.
then pda doesn't turn on.
Many problems.
Just go to the assistance. :\

1.Sometimes it freezes while its on. For Instance I had program opened and then whenI tried pressing X to close nothing happened. I had to use the red hardware button to close. Wonder why.
2.I too agree while the phone boots and is searching for network, it takes very long, Meanwhile when the pin enter screen come up, unless the network is fully searched one cannot enter the sim pin code, it has few freezes. or at time the phone signal icon disappears on top bar and again you need to reset the phone.

aniel1 said:
1.Sometimes it freezes while its on. For Instance I had program opened and then whenI tried pressing X to close nothing happened. I had to use the red hardware button to close. Wonder why.
2.I too agree while the phone boots and is searching for network, it takes very long, Meanwhile when the pin enter screen come up, unless the network is fully searched one cannot enter the sim pin code, it has few freezes. or at time the phone signal icon disappears on top bar and again you need to reset the phone.
Click to expand...
Click to collapse
Again, I don't have this problem for some reason... I get very few freezes at all.
I think we're getting away from the original point of the post though... and normal freezing is well documented in most OS threads with means to prevent it.

Same here...Confirmed. Tried all button combinations to get the display back (short presses and long ones), but then end up having to do a soft-reboot to finally get the phone to work properly....

Bhameed said:
Same here...Confirmed. Tried all button combinations to get the display back (short presses and long ones), but then end up having to do a soft-reboot to finally get the phone to work properly....
Click to expand...
Click to collapse
And then you don't have other problems? Like freezes?
EDIT: I flash the original rom but the problem still here

I wonder if this could be a memory leak like someone suggested.... I'm sorry guys, I haven't experienced this problem, and I haven't seen any posts about it until this thread, is there any chance you guys with this issue can keep an eye over your memory status over say a couple of days to see if there's a leek and keep us posted? Once we find out what the problem is it should make a solution easier.

I experienced this problem as well using a cooked WM5 ROM on my HERM200 the only fix I found was migrating to another ROM. I'm currently using CUSTEL_Cing_v1.3, the battery life sucks but I love WM6, it is so much faster, I'm still tweaking and trying to resolve some other issues but other than that I am quite happy with it.
If you are experiencing the lockup I would suggest moving to another ROM as an option, that worked for me. Although a clean install usually fixes a lot of problems.

WM6 screen goes off after 5 Sec

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

Touch Cruise Backlight Problem

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.

Tornado (WM6 Platinum) doesn't start

Hi,
I'm experiencing a strange problem with my Tornado (i-mate SP5, WM6 Platinum Edition). Today it stopped working suddenly, I had to remove the battery. When rebooting, the i-mate sceen appears, then the HTC logo, then Nitrogenius' splashscreen, then a beep sounds, and afterwards the screen is black and nothing happens, no keys are responding. I can "switch off" the phone by long pressing of the power key. Reset with pressing the 2 soft keys and the starting key does not work, the phone starts until the splashscreen and afterwards the screen goes black. Strangely I can connect the phone with activesync, synchronize contacts and calendar and even explore the device with activesync's filemanager; and the battery is charging, too.
Any suggestions except reflashing?
Regards

The same happen to me,backlight doesn't function. Start -- 9 start again 3 ok... flash light is enable ,now i should change home screen settings and power settings... set backlight to 10 minutes or more...
Then it should function

ma3ks said:
The same happen to me,backlight doesn't function. Start -- 9 start again 3 ok... flash light is enable ,now i should change home screen settings and power settings... set backlight to 10 minutes or more...
Then it should function
Click to expand...
Click to collapse
Thanks for the hint, I tried, but unfortunately I seem to miss something. Could you elaborate a bit how you managed to switch on backlight.
Thanks a lot!
EDIT: It worked! You made my day!
After pressing the keys you mentioned (and some others, too) and after rebooting again the backlight is on again. Thanks a lot!

I met the same problem in many cases and I found the culprit, it is tornadolowlight or tornadopowercontrol. while these appli are activating if I soft reset or by force restart (removing battery) then next startup will get a blank screen. But actually in this case the device is on and working only thing is its backlight is off. So, by using a torch light or simply using MyMobiler from a pc you can see the screen, and start that culprit appli then done
OR another thing I have done is I put shortkey for MultiFlashLight and whenever such situation happened I just press the shortkey and activated it and done

TP keeps turning itself off every 30 seconds

Hi
Unless I'm actively using it my TP keeps turns itself off after 30 seconds no matter what power settings I use (and despite a factory reset and SPB restore). This isn't too much of an issue, except when I'm trying to use GPS/Satnav (TT7) whilst driving, where turning itself off is a real pain.
Could anyone please suggest how this issue can be resolved?
Many thanks in advance...

Is it physically turning off, requiring you to press the on key, let it reboot, or,
is it going to sleep, and you press the on key to wake it up?
If it is the latter, go to start>settings>system>power, click on the
advanced tab and change the backlight & power off settings there.
If it actually turning off, sounds like it might be a defective phone.

Thanks for your reply!
I've repeatedly altered the power settings but it makes no difference at all, if I set it to turn off at any given time (or not at all) it'll still turn off after 30 seconds. And to claify, it doesn't reboot, it just turns the screen off. It *feels* like a software issue, because it'll stay working forver as long as I tap the screen occasionally, something somewhere just counts down 30 seconds if i don't and turns off the screen...

The max time you can put on it is 5 min. The default setting out of the box is 30 seconds --which sound like what you currently have.
Set the "On Battery Power: Turn off backlight if device is not used for xxx MIN). Make sure first that that's checked, and select the drop down.
Eventually --to conserve battery power--, it will 'sleep'.
Your NAVIGATION software should have a setting to over-ride this to NEVER TURN OFF DISPLAY WHILE NAVIGATION.
Aside from that, there is no other way to keep the backlight on --unless it's plugged into a power outlet.

Many thanks again for your reply; As I mentioned previously I've already changed the power settings settings (frequently) and I'm definitely not on the 30-second default, no setting appears to make any difference, be it 5 minutes or 'never turn off'. It also happens when the 'phone is plugged into a power source too.
(And I have got the 'don't turn off whilst navigating' box ticked for the satnav but the issue applies generally, not just to the satnav, that's just where it's most irritating).
Is there any possibility something has changed in the registry to over-ride the control panel settings in this way?

How about doing a hard reset and not doing a spb restore? You realize that all you did when you restored the phone was restore the bug, right?
Edit: I doubt it will work, but you can try the backlight cab. It will restore all the stock backlight reg settings if yours are messed up.

timpollard said:
Hi
Unless I'm actively using it my TP keeps turns itself off after 30 seconds no matter what power settings I use (and despite a factory reset and SPB restore). This isn't too much of an issue, except when I'm trying to use GPS/Satnav (TT7) whilst driving, where turning itself off is a real pain.
Could anyone please suggest how this issue can be resolved?
Many thanks in advance...
Click to expand...
Click to collapse
Hi,
I have same problem as you. TP keeps turns itself off after 30 sec!!
And I am using TT7. So this problem is so annoying.
I tried hard resetting and install programs one by one. and check if TP is keeping backlight on or not. And I installed TT7 and worked perfect.( display is always on)
That was yesterday.
Today I was using TP, it happened again.
The registry setting is still 3min on battery, uncheck on AC power.
30 sec problem happens both status.
This thing did not happen before Raphael_Cingular_US_5.11.502.2_Radio_Sign.
TP worked fine for a while on this radio.
Now even I check " NEVER TURN OFF DISPLAY WHILE NAVIGATION" box in some apps. TP turn off backlight.
I tried backlight.cab, that did not work and still turning off.
(thanks anyway )
ATT Fuze
Raphael_Cingular_US_5.11.502.2_Radio_Sign
Added Japanese IME
Resco Explorer, regedit
Resco Today Plugin
Spb time, Today plugin
TT7
TomTom 7 - v7.910.9185
I will try hard reset again.
Somebody please help us out.

Did you try the cab? If that doesn't work, just flash another rom.

I am also having this problem. I did get it to stop once by going in to the registry and actually editing it. But it started to do it again after a wile. I am trying it again today and see if it work. I am using a trial version of BestRegEdit and was wonder if it could have changed it back because it was a trial. So if some one elce wants to give it a shot it us under HKey_Current_user\ControlPanel\Power\Display and you will change that 30 to what ever amount of time you want. I pick 0 because i never want it to turn off. Hope this helps Oyeah, does anyone know of a free resitry editor? This is my last day on the BestRegEdit Thanks

Uh, total commander, regedit, dotfred's task manager and probably a few more.

Farmer Ted said:
Did you try the cab? If that doesn't work, just flash another rom.
Click to expand...
Click to collapse
Thanx,
I tried cab, and did not work. So I installed test rom and works fine now. NO 30 seconds backlight off now.
[March 1st] New ATT test rom Radio 1.12.25.19 OS AKU 1.4.6 Build 20771
I will use this until new "Signed" and Works Ok radio comes.
* Recently I use resco explorer and regedit addon. Free app: regedit.Mrln works fine, I think. I have been using these for keyboard layout section.

Glad you solved it, I had an interesting problem, similar to the screen issue, wonder it it might be related. I flashed to a new rom over the weekend, and no matter what I did, the backlight would turn off after 10 seconds. You could reset it to 30 in the power profile, but after a reboot, it would revert back to 10 seconds. Reflahsed it, and after the flash, when it starts loading the customizations, it would freeze. Flashed again, and it hung at customization again! Downloaded the rom again, deleted the old one, and flashed and it worked and the backlight would stay put!
Maybe the one you downloaded was corrupt?
Anyway, glad you got it working.
P.S. The rom isn't an "official" that I downloaded, it was one of the 6.5 that the cooks on the rom page whipped up. I think it was just a corrupted download.

This issue has happened to me a few times. even while i'm still using the phone and typing the screen goes off.
very annoying.
I found it only happened to me using EnergyROM. when I flashed to a different rom the problem was solved.
recently I flashed back to the newest version of EnergyROM again (after the previous ROM decided to hard reset all by itself) and this issue happened again in the first hour!
I really wish I could find a usable ROM for once and for all

My Case: WMWifiRouter was it!
This happend even when TP under Test rom env. I just gave up and installed latest version cause this ver is less stressfull.
Luckly 30 sec issue did not happend for a while until I installed WMWifiRouter.
Just after I install V1.50 30 sec thing and happend.
KB0907027: [BUG] v1.50 backlight timeout issue
http://support.wmwifirouter.com/knowledge/KB0907027/
I Installed V1.52 and now works fine and no backlight problem.
If you installed WMWifirouter check the link.

I use EnergyROM as well and i noticed that right after a fresh flash, if you tried to modify certain settings using the gui (i.e. alarm times, connection settings etc) they wouldnt stick - perhaps a direct registry edit using one of the tools previously mentioned might force the device to remember the changes? this worked for me when i had trouble with my alarm times not being saved.
ive also heard that sometimes a soft-reset isnt enough to commit changes to the registry - i.e. once making a reg edit, cold boot the device - that is press and hold the power button and turn it entirely off.
hope this helps