Related
Anyone else's auto-brightness not working? Mine doesn't
how?
How do you know? Or what have you noticed?
Rio
I don't think that mine works either, one of the first things I noticed.
Sent from my Transformer TF101 using Tapatalk
rio911 said:
How do you know? Or what have you noticed?
Rio
Click to expand...
Click to collapse
Well it never seems to change. To confirm I put it on the lowest and then on auto, it stayed on the lowest. I then tried putting it on the highest setting and then putting it on auto but again it stayed the same.
Surprised it took me so long to realise..
It takes an average reading of the light it senses over about 30-45 seconds when it's on auto and responds accordingly on mine. To check yours put a torch on over the sensor for about 30 secs and if nothing changes yours definitely isnt working properly. However I normally have it set to a manual amount instead of auto to save on battery etc.
Edit: Just tested again with a torch and this time it took 45 seconds to change... odd.
Where is the sensor located? Does it use the front camera?
Sent from my Transformer TF101 using Tapatalk
brachiopod said:
Where is the sensor located? Does it use the front camera?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It's the thing just over an inch to the left of the front camera.
I see it now. I put a bright LED flashlight over it while in a darkened room for a couple minutes and the screen did not change brightness. However, it does appear to have an IR filter over it, so maybe it is mostly sensitive
Sent from my Transformer TF101 using Tapatalk
Oops not used to the kb, sensitive to Sunlight.
Sent from my Transformer TF101 using Tapatalk
With it on full brightness (before changing to auto) I had my finger over it for a while but it didn't change. Then I left it on full brightness for about 10 minutes in a fairly dim room and no change either.
Just tried with an led torch here as well and it did sod all this time. Nothing changed. Try with another light source if you get the chance. The update rate on the auto setting is too slow really tbh. There are loads of apps in the market to test the sensors too btw.
@Case0
If it's not on auto mode it wont change at all.
Possibly it only checks at certain times, such as when an app starts. I bet that it reads IR so only certain light sources might work.
Sent from my Transformer TF101 using Tapatalk
I installed a couple of sensor tester applications, and none of them can report a value from the sensor. Sensor list 2.1 detects the sensor as a lite-on al3000a ambient light sensor, but no value is returned. Not sure if this means that it is not working, or if these apps just can't read that particular sensor.
It doesn't work for me either, although I haven't tested it since the new firmware upgrade. Maybe we have a bad batch.
I never was a fan from autobrightness. I always set it to middle.
Until I got a Nexus S and noticed how awesome it is that it changes the brightness, since otherwise you can not read the display outside. It also changes instantly.
Try this. Download and install Advanced Task Killer, then Sensor Test by Atmoworker. Kill all processes to make sure the sensor isnt in use by something else. Then run the sensor test. If your value for the light meter doent move, then there's something wrong for sure, or it's in use by some process that wasnt killed by the task killer.
stuntdouble said:
Try this. Download and install Advanced Task Killer, then Sensor Test by Atmoworker. Kill all processes to make sure the sensor isnt in use by something else. Then run the sensor test. If your value for the light meter doent move, then there's something wrong for sure, or it's in use by some process that wasnt killed by the task killer.
Click to expand...
Click to collapse
OK. That app does seem to read the sensor, and it does change. I didn't have to kill any tasks for it to work. It gives three readings labeled 0, 1 and 2.
0 changes from 1.0 to over 100 outside. Probably some log scale. 1 changes from -27 to over 100. 2 sits at a very small number, about 10^-45
So the sensor does work, the tablet just isn't using it properly it appears. Or something.
Ok well yeah sounds like it does work, just doesnt function the way you want it to. There are lots of apps to deal with screen brightness on the market, some free, some not so. And then there are also a few which lets it change using the camera instead of light meter. Here's a link to one to show you what I mean. https://market.android.com/details?id=org.pbxes.light2&feature=search_result I'm sure there are free versions available if you do choose this option. Good luck in finding one you like.
Well, if by "just doesnt function the way you want it to" you mean does not do anything at all ever no matter what, then yeah, it isn't working the way I want it to. Thanks for the tip, I'll see if I can find an app that works.
OK, auto brightness DOES work. I spent some time messing with it to figure it out. The auto routine started working after I did the 10 second power button off on my machine.
1) The level that you set with the slider becomes the minimum level for the brightness under auto. That's also why I didn't think that it was working, I had brightness up all the way.
2) The auto routine will adjust brightness UP within a short period of time, 10-15 seconds, if you move into bright light.
3) The routine will NOT adjust brightness down (you move into dim light) except at three points a) right before the screen saver kicks in (goes blank) or b) right after returning from the screen saver. c) you power cycle the tablet.
This means that it is quick to respond to ambient light and increase brightness, but if you have your screen timeout set long, or you keep using the tablet, the brightness will be very reluctant to adjust down. The brightness will never be adjusted lower than you set with the slider though, but it can go up all the way.
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.
If any of you other users out there feel that the whites on this thing are too awesome for super late at night like I do, I found a app when searching for a f.lux type alternative for android. I have been using this app to help ease the stress on my eye late at night. I dont know about the techical side of what it does, or any of the jargon involved, but it applies a filter of sorts to dim the screen further than what the phone allows. I been using it a lot lately and figure I would share with you guys. If anyone has any recommendations for other similar apps, please share.
Tl:dr
Screen Filter
https://play.google.com/store/apps/details?id=com.haxor
Sent from my SCH-I535 using Tapatalk 2
enomele said:
If any of you other users out there feel that the whites on this thing are too awesome for super late at night like I do, I found a app when searching for a f.lux type alternative for android. I have been using this app to help ease the stress on my eye late at night. I dont know about the techical side of what it does, or any of the jargon involved, but it applies a filter of sorts to dim the screen further than what the phone allows. I been using it a lot lately and figure I would share with you guys. If anyone has any recommendations for other similar apps, please share.
Tl:dr
Screen Filter
https://play.google.com/store/apps/details?id=com.haxor
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Or just turn on "Background Color" in Power Saving Settings.
Or if you want the screen brightness itself to be lower than what most ROMs allow, you can use this app called RootDim. It worked amazing on my xoom, not sure if it works on the SGSIII yet..
It requires root though..
yosterwp said:
Or if you want the screen brightness itself to be lower than what most ROMs allow, you can use this app called RootDim. It worked amazing on my xoom, not sure if it works on the SGSIII yet..
It requires root though..
Click to expand...
Click to collapse
Screen filter does the same and doesn't require root. On our AMOLED screens this can save battery.
Also you can turn off those damn capacitive key lights by going to Settings>display>"touch Key light duration"> Always off.
I can confirm that Root dim does work for the SGS3 I use it on my phone.
Current~Samsung Galaxy S3 SynergyRom 1.3 & Imo's Lean Kernel v12 Oc'd @ 1.9ghz
~Acer Iconia A500 Stock
Past~Droid X Gummy ICS 1.2
Lux is an amazing auto brightness app and setting it up for your tastes is incredibly simple.
Go out in the sun and turn brightness up all the way using the app then "link" that setting, go in complete darkness and set it to your taste and link it, then indoor lighting, set it, link it. It then uses just those 3 settings to create a smooth graph of brightness values that are all perfect. You can have as many links as you want but i find the less settings you put in that app the better.
I tried all the suggested ones in here btw.
Sent from my SCH-I535 using xda app-developers app
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
noingwhat said:
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
Click to expand...
Click to collapse
Try setting it to be always active in the task bar, that prevents it from being killed. Also try setting it to not use raw values for light sensor readings, this gives you a simple scale of 0-10 for readings and total darkness always reads as 0.
Edit: oops reread your post. That's weird that it is reading indoor light at 1. I usually get around 2 or 3. I used to have a screen protector on that covered the light sensor and that put it all over the place. Maybe that is what's causing it?
noingwhat said:
I've tried and really like Lux (in fact I'm considering purchasing it soon) but I've noticed two issues. First is that sometimes it will not refresh itself and I have to open up the lux dash to get the brightness to change. It doesn't happen often, but it happens often enough to be annoying, and I have it set to automatically.
Click to expand...
Click to collapse
I noticed the same behavior with the free version. In my case, the lowest value the HTC Desire S can reach with its default Android auto brightness is in fact about 15%.
In LUX settings you can configure the "0" value to be lower and "bypass" the freeware limitation (you can't configure sub-zero levels in the free version). This will work when you test it in the dashboard, but during regular use the light level never goes below the 15% limit already set by the OS.
What I did was purchase the full version (to get astronomer mode along with all the settings unlocked) so I was able to leave the 0 level at its default 15% but link some light intensity values to sub-zero percentages. Guess what? It works great! Once you go into a very dark room, the display dims as far as you set it to.
Another problem with the free version was that a few times I unlocked the phone outside in full sunlight and LUX did not increase the brightness. It appeared almost completely black because the light level was at about 15-25% (the same level it would be inside a low lit room).
Again, with the full version I did not notice this problem (I've used the free version for 1 day and the paid version for 1 day but running tests in different light levels inside and outside).
It's like the free version is a bit buggy on purpose, and I remember uninstalling LUX free about 2 months because of this; I was thinking that if the free version does not work OK, I shouldn't buy the full version. Apparently this is not the case (touch wood).
Just for the record, it's on "dynamically adjust".
noingwhat said:
Also, (and this may simply be an issue with the S3 and not lux itself) but sometimes I will be in a decently lit room and be at 1 lux, while lights out is 0. Not a lot of variance unless it's really bright outside. Have you found anyway to increase the light sensors sensitivity?
Click to expand...
Click to collapse
If the display is a bit dirty (oily, dusty, etc) around the light sensor, you can try to clean it. If this is not the case, open the dashboard, let it determine the light level or hit "auto" a few times and make sure the reading is correct. Then just slide your finger along the yellow line to find the appropriate brightness level and long press the chain to link. Go to a brighter lit room then go back to the first room and see how LUX behaves. Also lock/unlock the phone a few times and see how it goes.
If you still have problems running LUX, disable it and check the default Android auto brightness to make sure it's not a sensor issue.
LUX also has the possibility to set the response delay under Settings -> Advanced -> Developer Settings (the last to just on the bottom, but for this you would need to buy the full version.
Inginerul said:
If the display is a bit dirty (oily, dusty, etc) around the light sensor, you can try to clean it. If this is not the case, open the dashboard, let it determine the light level or hit "auto" a few times and make sure the reading is correct. Then just slide your finger along the yellow line to find the appropriate brightness level and long press the chain to link. Go to a brighter lit room then go back to the first room and see how LUX behaves. Also lock/unlock the phone a few times and see how it goes.
If you still have problems running LUX, disable it and check the default Android auto brightness to make sure it's not a sensor issue.
LUX also has the possibility to set the response delay under Settings -> Advanced -> Developer Settings (the last to just on the bottom, but for this you would need to buy the full version.
Click to expand...
Click to collapse
Thanks, but I think it is more of an issue of the sensor not being sensitive enough. I'm not sure if this is anything you can change in lux or if it would have to be edited in the kernel (or if it is fault of the hardware) but I just feel like the sensor doesn't go down low enough. As I said, I can get down to 1 or 0 in a decently lit room, and yes I have tried cleaning the screen. It's not like it jumps around or anything so it's not like I would notice anything in default auto brightness, it's just that it doesn't seem to be sensitive enough.
Screen filter is great!! I use as well!!!
Sent from my SCH-I535 using Tapatalk 2
Well for my Desire S, the lowest light level that the sensor can read is 160 lux (raw value). You can try and set LUX to use raw values because this is more accurate in my oppinion.
Another +1 for Screen filter here
Does anyone know how to use "luma" values for automatic adjustment in Lux instead of "lux" values?
noingwhat said:
Does anyone know how to use "luma" values for automatic adjustment in Lux instead of "lux" values?
Click to expand...
Click to collapse
What I have noticed on my phone is that "luma" readings are taken from the front facing camera, while "lux" readings are taken from the ambient light sensor (you can chose which one to use in the settings).
I suppose the front facing camera uses more battery than the light sensor; it also appears to be more sensitive because it can read more light levels.
Inginerul said:
What I have noticed on my phone is that "luma" readings are taken from the front facing camera, while "lux" readings are taken from the ambient light sensor (you can chose which one to use in the settings).
I suppose the front facing camera uses more battery than the light sensor; it also appears to be more sensitive because it can read more light levels.
Click to expand...
Click to collapse
I guess so. Thanks! But doesn't that kinda defeat the whole purpose of Lux? Because you can't use automatic mode with the camera(s).... so then what's it good for?
Well even if you don't have an ambient light sensor, you can still use the camera to check the light level when you unlock the phone and let LUX adjust the brightness level. Of course it's not dynamic but it's still better than having the brightness at 50% the whole time or changing brightness levels through a widget..
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 assume this is a feature and not a bug (and not a problem with my Mate 8). When I open the Messaging App, Chrome App or some other apps it would appear the screen brightness is reduced within that app. This has nothing to do with the normal Auto Brightness settings but appears backed into the phone's software.
Has anyone else noticed this?
UPDATE: Setting the Power Plan to Performance changes this behaviour! Wonder what my absolutely Amazing battery life will be like now?
For me it's the converse. When I open Whatsapp after unlocking the phone, increases the brightness. I'm not using auto brightness and use only performance mode
Huawei Mate 8 NXT-L29 with Tapatalk
I have same problem, in messanging app, dialer or browser display brightness is reduced noticeably. Tried with different themes, power plans and brightness settings.
i noticed it happening but i couldnt care less as long as everything is readable
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
I have this issue and after updating to Android 7.0 Nougat i can't find Power Plans anymore. How can i set it to performance?
Change to performance power plan. Smart plan does stupid things. Not that smart huh..
Anyone? This happens on my Mate 9 pro as well...
It did happen after updating to nougat , plus a strange YouTube issue when playing in 480p and less the video appears stripped , and these strips disappear after switching to 720p