Related
Hey guys
I have this weird problem with the LCD backlight since I upgraded to the new AT&T stock ROM (5.11.502.2 WWE)
Usually the backlight is supposed to dim down after 30sec and then turn off after the specified time set in (start/settings/system/power/advanced). Now suddenly this stopped working correctly. The screen just turns off completely after 30sec, no matter what I change the control panel settings to.
I found the registry key (HKCU/ControlPanel/Power/Display) which is set to 30 seconds so yeah, I can increase that to make the screen turn off later, but I want the dimming back!
Where is it defined *WHAT* is supposed to happen after these 30 seconds?
No one?
Am I the only one here with a stock rom? LOL
My Fuze light sensor doesn't seem to be working correctly either. It's not the same problem, though. And I'm not really sure if mine stopped working right after the new ROM or after I installed Diamond Tweak and Advanced Config.
There used to be a noticeable change in the backlighting when moving between different ambient lighting conditions but now I don't notice anything. If I cup my hand over the light sensor, the backlight stays the same whereas before it would dim a little and then brighten up again after removing my hand.
Can anyone tell me what the default registry settings for it are so I can see if either DT or AC did something?
Thanks.
RootDim (formerly known as ScreenDim) lets you set the screen brightness on backlit screens below what the OS normally allows, which is handy for amateur astronomy where the lowest normal OS backlight setting (even with a red nightmode) leaks enough through the black pixels to damage night vision. Moreover, SuperDim lets have several brightness profiles, and to include nightmode settings (enabled by ChainFire3D or Cyanogenmod's render fx) as part of the brightness profile.
Needs root.
Public domain, source code available. In Market (search for RootDim).
Now in Market (free, no ads).
I just uploaded version 1.10, which restores low brightness settings after the screen is turned off and back on (the OS normally was restoring its brighter screen).
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
bobtentpeg said:
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
Click to expand...
Click to collapse
I assume this is when you use the other lights option to toggle these lights, or when you restore a profile, right?
In version 1.11 (just uploaded), I no longer restore other lights when a profile is loaded--this should help with your problem, as long as you don't touch the other lights. Eventually, I may add an option to choose which lights get restored from a profile.
I originally made SuperDim for setting very low backlight settings on LCDs, and so I made it not work on non-LCD screens (e.g., OLED). But I've since realized that the profile feature might be useful for non-LCD users as well, so I've released version 1.20 that supports non-LCD screens. It's in Market. While I was at it, I cleaned up the code a little, made it more javaish (I'm new to java).
My MyTouch 4G just seems to turn the screen off totally if i go below 20 brightness, it dims but then shuts off.
Doesn't work at all with Dell Streak 5
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Awesome, thanks for the Advise!
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Screen filter merely adds a black semi-transparent overlay across the screen, making it look dimmer.
This app adjusts the backlight, which means darker black levels on the screen.
Frosty666 said:
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
Click to expand...
Click to collapse
My eyes don't care. +1 Screen Filter
lownox said:
My eyes don't care. +1 Screen Filter
Click to expand...
Click to collapse
Your eyes would probably care if you were doing amateur astronomy under a dark sky (which is the primary purpose for SuperDim). Screen Filter doesn't turn down the backlight, and on a lot of devices there is enough backlight leaking through even completely black pixels to damage night vision. You can try this experiment. Turn a backlit device to a completely black screen (maybe view a black jpg) and take it to a completely dark room. Let your eyes dark adapt. The "black" screen will in fact probably be quite grey. (If it's really black, that's probably because you have an OLED device.)
When I do amateur astronomy, I am not infrequently looking to see objects way dimmer than backlit black pixels.
I'd like to do something about the screen turning completely off issue.
To that end, I need people to do some experiments for me, and I will be very grateful (I'll also give a free full version of Force2SD as compensation for the first couple of experimenters, if you want it--just email me). The first experiment is this. Download SuperDim 1.22, now up in the Market. Press the menu key, and choose "Turn on safe mode" (you can tell safe mode is on, because next time you pull up the menu, it says "Turn off safe mode"). Now, turn brightness down to 10. Does your screen turn off?
I should warn that very low brightness levels can be very low indeed. For instance, if I am outdoors on a sunny day, I have trouble telling the difference between brightness 4 and off. So you need to be in a dark area--I recommend a room without windows and with the lights off.
If the screen does not turn off at 10, turn it down to 5, and then 1. Let me know if it ever turns off.
I am guessing that in safe mode, it doesn't turn off at all.
What safe mode does is it makes very low brightness settings not persist. So if you are in safe mode and leave SuperDim, you lose your low brightness setting.
I'd also appreciate it if people who can normally turn their brightness down to 1 could do some experiments with safe mode. Specifically, I'd like to know if moving the slider to 1 in safe mode has the same effect on screen brightness as moving the slider to 1 in non-safe mode has. (Again, if you're one of the first few experimenters and want a free copy of Force2SD, email me.)
On my Archos 43, brightness 1 is very, very dim, but the screen is still on. And I can't tell the difference between safe mode and non-safe mode, except that in safe mode, the settings don't persist after I leave SuperDim.
Tried this app on my desire HD.
Great idea, but when I reach 10 and below, the backlight doesn't get lower.
If I use the adb method (don't remember the command), I can set the backlight manually all the way down to 0.
There is no difference with or without safe mode on.
inspire 4g with coredroid V7.0 doesnt work
elmanortega said:
inspire 4g with coredroid V7.0 doesnt work
Click to expand...
Click to collapse
What happens? And does safe mode work?
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
kamranh3 said:
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
Click to expand...
Click to collapse
I found a bug. In fact, the bug is such that I have no idea how it was managing to work on my device at all! In any case, I think I fixed it. Try 1.23 (should be in Market or here) and see if it does the job. If not, I have some more ideas.
I've looked at past threads, but found no resolution to this.
I'm running voodoo colour with deep black settings and everything looks great, except right before the screen times out it will dim to its lowest setting and force the amoled panel to turn a sickly yellow/green hue.
I would like to disable the dim aspect and just let the screen time out by shutting off completely. Is there anyway to do this? I'm running the latest version of Pixel Rom with Air Kernel 4.2. I don't have auto-brightness enabled.
i am having the same issu i dont have to yellow tint in low light
but still i whould like to disable the dim it is disturbing my daily use of the device
i too dont see any point for this time out before the screen turns of
and i cant understand why when plying a game i need to touch the screen every 25 sec to get rid of the dim
thanks
I remember seeing something about auto-brightness light sensor tweaking back when I was using NV rom last year but I don't know if that would apply or not.
Does anyone know if the custom apps on the market avoid this?
edit: Tried Tasker for a full screen-off solution, and a bunch of other apps. Wasn't able to get the results I wanted :I
I have a Samsung Captivate and I am running a kernel with voodoo color support with this same issue.
The first post of this thread shows a possible solution - http://forum.xda-developers.com/showthread.php?t=1002090
I flashed the pixel os android 10 in my redmi note 7 and now i am facing screen lock issue my phone does not accept any screen lock that i am trying to apply on it plzz help me
I've been digging into the "touchkey backlight issue" and would appreciate some help understanding how it worked (or didn't) on GB-based ROMs. If you are running GB (rather than "I remember..."), understanding how the proprietary Samsung code handled the backlight, both in auto- and manual-brightness mode, under a variety of screen timeouts, USB plugged, AC plugged, etc., would be great. Information like this can also help me guess where Samsung has their proprietary code, rather than wading through 150 MB of ROM.
Reports like,
The backlights go out after a couple seconds
Click to expand...
Click to collapse
aren't terribly helpful.
The backlights turn on when I tap the screen anywhere, then turn off after a second or two (it seems to vary from time to time), when I'm running on batttery, with auto-brightness on, and in normal indoor home lighting. They don't turn on with the same settings if I am outside.
Click to expand...
Click to collapse
or the like is much more helpful.
(I made that stuff up. I don't remember how they worked under GB.)
Oh, let me know which ROM you are running as well.
No promises, but knowing where we came from can help determine where we might go.
Thanks!
P.S. This is a common problem with Samsung phones -- You'd be amazed at the number of inquiries about the touchkey backlight.
I can check these later again a stock S4G I have still on GB, but on my flashed one with FB's AOKP using your brightness for the screen fixes, this is what I just tested.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 30%, backlights stay on for the whole 5 mins.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 100%, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 34/34, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 2000/2000, backlights go out as soon as the raw value hits past 150, your default to turn them off.
When I remove it from a bright light and the raw goes back down to below 50 though, the autobrightness does not dim the screen, I have to put it to sleep and wake it up to get it to actually drop the brightness..
Moving the phone between bright light and dim light, the buttons do go on and off corresponding to the 150, but the screen doesn't dim or go brighter.
If the buttons are off from being in bright light, and I press one, they go on and stay on and moving out and back into bright light, they seem to stay on most of the time.
So it seems your code for the autobrightness can turn the buttons on and off, by the 0 value for the correct RAW value. It's spotty though and the autobrightness doesn't adjust itself to the correct level until I sleep/wakeup again. I can have autobrightness on and move my phone from dark to light and the buttons go on and off by the brightness of the light but the screen doesn't.
I will check this same test against a stock GB and see what happens.
This is for gingerbread:
Sometimes the key lights don't turn on at all while using the keyboard, and even when you are pressing keys in the keyboard. It might not even be caused by the keyboard being out, maybe it's the way I hold my phone while I'm typing that causes the auto brightness to go down.
This doesn't occur all the time though. Also, sometimes it doesn't turn on at all even when touching the screen (maybe for a minute) then they turn back on.
It seems that the key lights have some situations where they decide to ignore touches and stay off, I'm still trying to figure out when this is. Again, it mostly happens when the keyboard is out. Maybe it has something to do with auto brightness. When toggling auto brightness on and off, the key lights immediately turn off and stay off for about 30 seconds. This makes me think that the soft key lights even on stock are buggy
Thanks getochkn; great report for ICS!
That pretty much agrees with what I am seeing on ICS and what I would expect from the code.
The buttons "don't play nice" with the Android world as it seems they turn themselves on when you touch them (probably hardware control), and the present TeamAcid ICS driver turns them on when it (re-)initializes. The Android world won't change the brightness of any of the "lights" if it thinks that the level is already set. For example, if it thinks the buttons are off, it won't try to turn them off again. I believe this is why with auto-brightness on the buttons sometimes won't turn off. I'm still wading through PowerManager service to understand how the code is trying to handle them when in "manual" brightness mode.
Definitely looking forward to your results for GB, though pisherthefisher's report that they seem "buggy" on "stock" for him suggests that Samsung might not have gotten it right even there.
Seems to be no way to fully disable them eh? Then we could just use the JB style nav bar like already in FB's AOKP which lets us set color, brightness, custom icon, etc but with the other buttons still working physically, lights on or not, it seems not worth it as you will still hit the sammy buttons, especially if the light is off but the buttons still physically work.
I can "hack" them off, but I'm trying to solve the problem more generally and in a way that keeps the TeamAcid framework able to easily track the CyanogenMod upstream. I might build a "Hefe Kernel Of Darkness" if I can't find something this week.
Posted from my SGS4G, thanks to Team Acid development
Ah. Might be an option, go all softkeys via the ROM instead.
I know OT, but any idea why the autobrightness doesn't seem to fully kick in sometimes either? I can be in the custom screen to view the raw values and see the numbers drop but not the screen brightness until i sleep/wakeup. The backlights will go on/off according to the raw value but not the screen brightness. lol.
Going to go see how my stock one works and I'll report back.
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
jeffsf said:
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
Click to expand...
Click to collapse
Thanks. I forgot the settings after reinstall.
On GB, the lights seem to go out at some value (no custom, can't tell) but do come back on when you press them and then seem to stay on randomly. lol.
FB's AOKP comes with BLN control which does seem to use the lights as an indicator light for lockscreen notifications, so they seem to be able to be controlled from that SW. Not sure if that helps or not?
Hefe kernel of darkness sounds awesome, it would be cool to use the sgs4g like a galaxy nexus
Setting the backlights to 0 on all light settings, the backlights go out, but as soon as you go to sleep, and wake up, the lights come back on and don't go out even though the custom panel shows the state of them at 0. Turning auto-brightness off/on then turns the lights off, so the state is not being restored at wake. Of course touching one of them turns them on and they stay on again unless i toggle off/on again.
Yes, right now driver resume turns on the backlights, but Android thinks they are already off, so it doesn't turn them off based on the auto-brightness settings. Touching the keys is similar, but it seems to be hardware that is turning them on.
Posted from my SGS4G, thanks to Team Acid development
Well I'll test a darkness kernel if you get one going. lol. Use the softkey feature in AOKP. I've already been playing with and have it setup, I just don't want to hit the sammy buttons which I brush sometimes by accident, nor have the lights come back on after wake up, so if can disable them fully in the kernel, that would be cool.
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
jeffsf said:
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
Click to expand...
Click to collapse
no wifi. lol. Doesn't even turn on.
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
jeffsf said:
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Works good other than that.
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
m4127440 said:
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
The best we can do right is only have them turned on while pressed with the hefe kernel of darkness. Check out the hefe kernel thread in the development section, second post
Sent from my SGH-T959V using xda app-developers app
We?
The current rom im running that has the problem is cleanrom ultralight, I have had it before on cleanrom and i think some builds of stock roms, dont think CM10 ever gave me this problem.
When I run lux auto brightness and set the slider to a subzero setting, when I run most apps (but not all) the screen goes totally black. One example is setcpu, and it also happens when I launch lux settings. One example where it works fine is nova launcher. If I press the screen on top where the status bar is, and "grab" the status bar, screen reappears until I let status bar go, where screen goes black again.
Basically on most apps using lux in subzero setting causes screen to be totally black but still clickable. Any ideas?
Screen filter app doesnt cause this problem, but lux serves my needs better.
Sent from my SCH-I535 using xda premium
Hey sfetaz,
This is the first I've heard of this issue. It sounds like transparency is being lost somehow. I'd take this issue up with the Cleanrom devs, chances are they changed something they shouldn't have.
Hi,
I have the same issue as described by sfetaz. If I set the brightness to sub-zero (-1 is sufficent), the screen goes to minimum sub-zero brightness (-90) after a few moments in most apps. Sometimes it looks like this happens only if screen content doesn't change for a while. This does not happen if brightness is set to 1 or higher.
I use Lux Lite on a Motorola RAZR HD (XT925) running CyanogenMod 10.2. The issue exists since CyanogenMod 10.2 nightly build 2013-10-19. On 2013-10-18 everything is OK for me.
BBQLog (changelog.bbqdroid.org) shows some display related changes in CyanogenMod on 2013-10-18 and 2013-10-19.
I know 10/20 there was an update for the display. I ran it on PACman with no issues, and I am now on the 10/25 Vanir. No issues with either. I did notice this morning that when I load the default values, that I only load the 2 setting gs I have set, 0 and 2000 or 20000 can't remember off hand. I have my 0 set for -40 and it dims the screen correctly.
This post was made by Vanlandi.
On my RAZR HD (XT925), the problem persisted upto CM-10.2 Snapshot-M1 (2013-11-02).
After flashing CM-10.2 Nightly 2013-11-06, overlays (sub-zero, night/astronomer) mode are functional again.
It had something to do with the overlay. Normal brightness adjustments (>=1) worked as expected. Going to sub-zero or enabling Night/Astronomer Mode, screen content got barely visible after some seconds. When I enabled alternative overlay, the screen went totaly black (sub-zero) or red (night mode). (havn't tried astronomer mode with alternative overlay)
For me, this issue is resolved on the current CM Nightlys for XT925.