Database Info

My backlight wont go off since last night.

It wastes lots of battery. I think i might have damaged the light sensor but i've tried turning it off but it doesnt change anything.
Anybody know?

Even if the light sensor is damaged, your backlight will go off after your device idles for some. Check your settings

thanks for the prompt reply.
ive checked all my power managment settings and they're all on the lowest time settings..
i dont understand why it would do this.

Are you using any softwares that manages the backlight timeout? Such as Tweak2k2, etc

it seems to be working fine now after i restarted my phone.
i wasnt using any software.
thanks for your help.

ducamie said:
it seems to be working fine now after i restarted my phone.
i wasnt using any software.
thanks for your help.
Click to expand...
Click to collapse
my phone did this before. but yea just a simple reset fixed it

Maybe you installed maniac's AutoKeyLock, I had the same behavior a couple of time...
It seems like after some time, it overrides by mistake the power mgt values.

Hi!
I have the same problem. Wm6 The back light turn to the dim mode and that"s all. It does switch off the screen. If I connect to the AC power It does the same. When I lock the keypad, every thing seems to be all right. It switches the screen off. Any idea. I restarted the phone, but nothing changed, i didn't install any Autokeylock program.

Hi, this problem exist occasionally after you install some apps (i.e. AutoKeylock). You can fix it easy - enter registry and open key "HKEY_CURRENT_USER\ControlPanel\Power" then modify value in key "Display".

Thanks, it is working.

WM6 Backlight issue

I am not sure if this is a bug in the rom or something I need to configure somewhere but....
I have adjusted my backlight settings such that when the device is on battery the backlight stays on for 30 seconds.... work fine, no big deal...
However, if my device is "locked" (i.e. hit lock on today screen) and I press a button to look at the today screen,time,weather or whatever the backlight will always turn off in about 5 seconds.
Is this something I can configure somewhere?
Thanks....

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

Black screen & no recovery!!!!

Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73

the android laying on its back IS the atock recovery.

simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:

Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.

RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.

republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!