Is there a hack to not have the backlight automatically dim out when screen locking the phone? Any help appreciated on this. Thanks.
Yeah, use search. There's a quick & dirty fix that helps until HTC wakes up. It's in this thread somewhere.
Thanks,
I did search quite a bit. The fix I found was to diable the screen shutting off during a phone call. I haven't been able to find the fix for the backlight dimming out when screen locking the device.
Search
Hmmmm... Sorry you missed it. I went back a couple of pages and found ur answer; there are two:
1) Easiest remains to switch off-on your TyTN II after call. Ur back to normal then.
2) Option is a small app, written by Magxs that wakes the baby up after disconnect. See more here: link.
Hope this is of use.
edit: by the way, this only seems to happen to password protected systems. That is an option - switch off the PW. Lot of us can't due to corporate (exchange or goodlink) security pollicy.
Thanks Nukenine, however, this is not the issue I am questioning. Regarding the issue that you are speaking about, the following is the fix:
Modifying the DWORD stored in:
Code:
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
from "1" to "0" will leave the screen on and will fall back to the backlight/power settings
My question is when I key lock my device (the action that we can have on our today screen which says "Device Locked" or "Device Unlocked"), the screen automatically dims out. And when I tap on the screen, it stays dim, it does NOT become bright again. So, I am asking if anyone knows the registry hack on this issue. I hope I clarified what I am trying to find. Thanks again.
Sorry for misunderstanding.
It is a very easy fix.
HKCU\ControlPanel\BackLight\LockLevel\
Change LockLevel to something other than 0. I use 4. The number indicates now many notches you have the slider moved up in the back light control panel.
Jason Lee said:
It is a very easy fix.
HKCU\ControlPanel\BackLight\LockLevel\
Change LockLevel to something other than 0. I use 4. The number indicates now many notches you have the slider moved up in the back light control panel.
Click to expand...
Click to collapse
Hey Jason,
Thanks for the info. However, when I change the number to 4 (I even tried 9), and then I screen lock my device, my original Backlight setting (set to turn off in 30 Seconds) changes to 10 seconds. When I unlock it, go to the backlight settings, change it back to 30 seconds and then lock it, it changes automatically back to 10 seconds. So the hack works, but it gets rid of the backlight settings and changes them to the ones mentioned above.
The more serious issue is when I soft reset the device. It seems that the number I entered into the registry path goes back to the default "0" automatically. I tried this three times and it always goes back to the "0" default, rendering the hack useless.
Any advice?
Thanks again.
Jason, any advice on the above? Is it possible it is because of the registry editor I am using (Resco Registry)?
Sorry it took so ling, been busy.
That is odd.. I guess i hadn't rebooted in some time.. Mine goes back to 0 as well. It doesn't have anything to do with your registry editor. Something is changing it back on boot. Probably one of the HTC services or something. So there may be no good fix for this.. Other than someone writing a program that will change it back after start up.
I don't have my back light ever set to go off after a time.. It seems pointless to me.. Just have the device power off after a time. Saves more power than just dimming the back light.
anyway.. i have not seen the issues you describe with that but i don't have it set that way.
Jason Lee said:
Sorry it took so ling, been busy.
That is odd.. I guess i hadn't rebooted in some time.. Mine goes back to 0 as well. It doesn't have anything to do with your registry editor. Something is changing it back on boot. Probably one of the HTC services or something. So there may be no good fix for this.. Other than someone writing a program that will change it back after start up.
I don't have my back light ever set to go off after a time.. It seems pointless to me.. Just have the device power off after a time. Saves more power than just dimming the back light.
anyway.. i have not seen the issues you describe with that but i don't have it set that way.
Click to expand...
Click to collapse
Thanks Jason, I appreciate the reply and feedback.
This is bugging me too. I hope we find a solution for it soon. Is there a place in registry where startup programs can be defined? If yes, is there a silent tool we can use to import a reg file in the background at startup?
Just took my LCD density from 160 to 220 (just messing with it) and when i get past the boot screen i get a black screen, the backlights on but no display. Any ideas how to fix this? I just rooted and installed 1.1 and dont wanna lose everything!
You used LCDDensity from the Market I imagine? Just do a full reboot. On a reboot the setting is lost, so it'll be set back to normal.
I've held power down and rebooted, is there a more official method?
Hey all. I just installed V21a, and i can't STAND the DPI at 240. i tried setting it to 180, and reboot. when it starts back up, the lock screen loads, and when i go to unlock it, the phone restarts...
I've tried using different launchers, using different DPI numbers, and i haven't had any luck. anyone else have any similar problems?
So I have an XT1064 that I just updated to lollipop 5.0.1 (22.21.25 build ). Phone is completely stock,. Anyways I was messing around with the settings and I was adjusting the screen brightness. I lowered it to the lowest setting and the screen turned completely black. Can't see anything. I already tried rebooting the phone but as soon as it boots the screen turns black. Any ideas on how to fix it.
ImperiousRex89 said:
So I have an XT1064 that I just updated to lollipop 5.0.1 (22.21.25 build ). Phone is completely stock,. Anyways I was messing around with the settings and I was adjusting the screen brightness. I lowered it to the lowest setting and the screen turned completely black. Can't see anything. I already tried rebooting the phone but as soon as it boots the screen turns black. Any ideas on how to fix it.
Click to expand...
Click to collapse
Factory reset
The purpose of this question is related to an intermittent problem that I experience on my Eonon with the Malaysk 444 rom, which results in the screen going blank. I suspect that it is "stuck" in auto brightness mode, and as a result some of the auto brightness values, for whatever reason, do not register for my device and result in a blank screen.
My temporary solution to this problem is to rekey a physical button using MTC-Keys as event 85 (event_44=85). This works to move the brightness value from 0 to 100% with a few steps in between. My results are that I go from 0% which is a blank screen, then get 25% brightness, then 50% results in a blank screen, then I see 75% and 100% as expected. Does anyone know where the predefined sequence values for event 85 are stored? I'd like to play with setting different brightness values (0-255) for the various steps to see if I can find values that work at each stage. I suspect this might fix the auto-brightness values as well.
Thanks in advance.
Hans
hans109h said:
The purpose of this question is related to an intermittent problem that I experience on my Eonon with the Malaysk 444 rom, which results in the screen going blank. I suspect that it is "stuck" in auto brightness mode, and as a result some of the auto brightness values, for whatever reason, do not register for my device and result in a blank screen.
My temporary solution to this problem is to rekey a physical button using MTC-Keys as event 85 (event_44=85). This works to move the brightness value from 0 to 100% with a few steps in between. My results are that I go from 0% which is a blank screen, then get 25% brightness, then 50% results in a blank screen, then I see 75% and 100% as expected. Does anyone know where the predefined sequence values for event 85 are stored? I'd like to play with setting different brightness values (0-255) for the various steps to see if I can find values that work at each stage. I suspect this might fix the auto-brightness values as well.
Thanks in advance.
Hans
Click to expand...
Click to collapse
Do you still have this problem if you temporarily turn off the CAN bus in factory settings? We noticed the same problem on devices with the factory MCU software that have random brightness levels. For us, going into the Android settings, then selecting another brightness option seems to temporarily fix the issue.
I haven't tried that yet and today I upgraded to 5.1.1 and the problem hasn't shown itself yet.
Before I upgraded I set the brightness mode to auto as a test. I discovered that my fix didn't work anyways.