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
Hi
I recently upgrade my SAGA from CM 7.1 to 7.2, it seems CM team did a great work, less defect, smooth animation and so on. If the Auto Brightness can be as good as which on 7.1, it will be a perfect Rom.
Basically, I use the default setting, except enabled "Allow light decrease" on both version, I found on 7.1, if you move phone from a bright place to a darker place, the screen will get darker gradually, even just from one level to another, it doesn't make you feel flicker. However, on 7.2, it just change the backlight from one level to anther without any transition. I even tried the latest night version built on July 29, same reaction.
Does anyone have the same problem and know why?
Thanks.
Not sure if this is a Nexus5 or Android issue ...
Not sure if this is because I'm moving from an AMOLED to a IPS LCD ...
but I find the Auto-Brightness less of a function and more of a roller coaster ride.
- At home, in a well lit environment, the phone defaults to max brightness, which doesn't seem correct.
- In a dark room, upon wake of the phone, it correctly selects a lower brightness, yet will randomly ping up to max brightness, then settle back down.
The screen on the Nexus5 is absolutely gorgeous, but it just can't seem to select and lock onto the proper brightness level with respect to ambient light.
Is anyone else experiencing auto-brightness wonky-ness? Are there any potential fixes?
Everyone AFAIK suffers from it on nexus 5.
I have a horrible feeling it's a hardware fault, as none of the other Google devices on kitkat have this issue.
yeah the auto brightness seems to be too aggressive, but i'm sure custom roms will have the ability to tweak the auto brightness settings. i think even gravity box has some tweaks for the brightness
If you download Android Sensor Box, you can check the Light sensors. I think it may be bugged with Halogen lighting (correct me if I'm wrong). My home is ~ 18 years old, and we have some bulbs that have not been changed yet (yellow). Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings. I'm not sure if it's a rom issue or hardware issue, but my cousin also has a N5 and his worked fine. I tried flashing a new rom and mine still acted up fresh after boot (1st app installed after fresh flash was Android Sensor Box to test).
As a rule I don't use auto brightness. Just get something like lux or install exposed and enable a mod to let you adjust it by sliding your finger across the notification n shade. Easier and faster.
Sent from my Nexus 5 using Tapatalk
I find that autobrightness will auto-turn on, even when i don't want it to.
There is something funky about it, I can either make the phone too dark (using lux) or too bright (using default settings)
I'm still not happy.
Tried Lux, tried adjusting the brightness tables via Gravity Box, used Twilight (to dim at night), no matter what, N5 just wants to be at full brightness all the time!
I had my Nexus 5 in the cinema the other day. The phone was sat in the cup holder by the chair for the most part of an hour when I quickly replied to a text. On turning the screen on it was on full brightness and what's worst is it took around 10 seconds for it to go down. There is definitely something not quite right with it.
Aria807 said:
Sometimes when I use my N5 under those lighting, the sensors go whack and don't register properly picking up 0lx, then spike up to 30000lx. Once I move to areas in the house with newer bulbs, the sensors work normal, picking up the right readings.
Click to expand...
Click to collapse
Hi, I have been experiencing this as well, so I attempted to fix this at ROM level. The solution requires Xposed framework, so it works only on rooted devices (related discussion).
I'm not sure what it is with this phone's auto brightness but comparing it to my old nexus 5 I can see that this phones screen is always darker. I know autob its working because I sometimes see it change automatically but its just always set to be way too dark. I
f anyone else has this problem or know how to fix it without having to manually adjust the brightness that would help a ton.
Also if you changed your lux levels please post those.
On and also I do have the official screen protector on if that matters.
genardas said:
I'm not sure what it is with this phone's auto brightness but comparing it to my old nexus 5 I can see that this phones screen is always darker. I know autob its working because I sometimes see it change automatically but its just always set to be way too dark. I
f anyone else has this problem or know how to fix it without having to manually adjust the brightness that would help a ton.
Also if you changed your lux levels please post those.
On and also I do have the official screen protector on if that matters.
Click to expand...
Click to collapse
Yes, it is a little dark, you can go to settings/display & light and hit the little gear icon, hit adjust and set up the screen brightness you like depending on the ambient light.
i am facing that some time while scrolling brightness increases for some millisecond and come to normal. i found that is twitter, some huge page in browser page.
can any one tell what could be the issue hardware or just a software bug which can be fixed with other rom installation.