Perhaps is supposed to be this way, but I have noticed that my backlight won't turn off when plugged in - even though set to turn off after 2 minutes when plugged in. Instead of turning off, it seems to revert to a dim mode - but the light still remains on. I have to manually turn it off. Any thoughts?
That's what it does. Unless the phone is off, the display can't be turned completely off. This is because the screen is not transreflective.
I understand that, but the trouble is that the backlight remains on. Surely that's not supposed to happen, right?
no, thats not normal behaviour.
do you have anything running in the background? its sometimes a good idea to go into the settings and untick the boxes, soft reset the device, then put the settings back the way you want them. This has worked for me in the past.
Are you talking when the device is plugged into the USB port w/ ActiveSync running? If so that is how it works - device will stay on.
If you are talking about plugged into AC then it should power off after x amount of minutes.
To be clear, if the phone is ON, the backlight will always be ON. This is different from the previous Hermes/8525 that had a transreflective screen which could be seen in bright light with the backlight off.
The Kaiser/Tilt's don't have transreflective displays so they changed the backlight control to dim instead of OFF. When the display brightness slider is put to minimum or the display timer expires the display just dims.
Pressing the power button and going to standby is the only way to turn off the display that I'm aware of.
Now, Auto Power off after a timer expire is different. If you set the power settings to turn off after 2 minutes while on A/C, the Kaiser will turn off, IF it's not connected to Active Sync, and IF there isn't some other application keeping the phone alive (Apps like iNav keep the phone alive).
Related
Both with the default ATT ROM as well as with the TILT AKU.0.7.0 ROM my phone will not turn the screen off when docked.
I have the backlight and power settings adjusted to allow the phone to turn off the screen after 1 minute and turn off after 5 minutes.
When docked, instead of going dark and powering off per my settings, the screen drops to about a 20-30% brightness level and the phone never turns off.
I supsect some app may be keeping the phone awake, but disabling my plugins did not make a difference.
Anyone else experience this behavior?
I have an unlocked TyTN II, with stock HTC ROM, and thats how it's always been out of the box.
Maybe I'm just used to how my old Hermes behaved.
I noticed this too. Now if someone knew how this could be deactivated so the screen was completely off, that would be nice.
-James
The Kaiser's screen, unlike Hermes, is not transreflective and if the backlight is off, the display is completely blank. HTC elected to have the display stay ON at a minimal brightness when the timer runs out.
At first I wasn't happy but at night, navigating, I like the fact that it auto-dims while attached to a charge cord.
As topic says, how can you make the screen dim itself during navigating with tomtom 7.
I don't have a car charger yet and the screen is constantly on when I'm using tomtom, which drains the battery.
Any ideas on how to change this?
You could always turn on the automatic backlight feature which will automatically turn the brightness up in bright light and dim it when in the shade.
Start, settings, power, backlight tab. Saves a lot of power when on the battery.
I've allready turned on that feature, but the screen won't dim at all when I'm using tomtom.
I notice that my X1 backlight won't turn off.
Even if I set backlight to off after some time, the light just become less bright but not totally off as compared with my HTC Hermes/Tytn.
Is it a "feature" for X1? Will it hurt the LCD if the backlight not turn off, especially that I usually leave it on while charging with USB of my PC?
The backlight dims to minimum instead of turning off completely. If you are connected to a PC it won't turn the screen off, despite the setting in power management. If it is charged with a charger (not PC connected) it will turn the screen off if it is set up to do so.
Tap the power button to turn the screen off and disable the touch feature... key's remain unlocked and apps keep running
I am having a similar issue, if I push the power button to turn off the screen, it turns off, but then 5-6 seconds later it comes back on, this is after a hard reset and no other programs. Any idea what could be causing this?
Hey I just started having the exact same problem today. Turn off backlight with the power button, moments later it comes back on. This 'ghost' activation is inconsistent. Sometimes it doesn't come on for a while, but it will eventually come on.
About 2 weeks ago I spilled some water on it. I dried it out with a hair dryer and all seemed fine but now I'm wondering. It's almost like the power button is shorting out, turning the darn thing on. Any clues or solutions out there?http://forum.xda-developers.com/images/smilies/confused.gif
I never noticed this before tonight. I have the Samsung wireless charger so I assumed the light I was seeing from behind me (I have it on my bookcase headboard and the base lights up in blue while charging and turns green when done) was from that. Tonight, I have the phone physically plugged in and sitting on the coffee table next to me. The screen won't stay off while charging. I push the power button to turn it off, it goes off for a few seconds and then comes back on.
Is this normal? I have the screen timeout set to 30 seconds, don't have Daydream turned on (anymore) and Stay Awake is turned off in Developer Options.
I went and put it back on the wireless charger and confirmed that the light won't stay off there either.
If it matters, I'm running Rapture 2.1 (COF8/5.1.1)
Disregard. It was caused by Cellmapper.
This has happened to me a few times where the screen will dim as if it's about to turn off but does not. The only way to fix it is to restart the phone. I've checked developer options and stay awake is checked off (doesn't matter though because it will stay on regardless of charging or not). Has this been happening to anyone?
Bump