Main question: is the light sensor always on even if I turn off the "automatic brightness" in Display settings?
If the answer is no, I might have to reconsider the usage about light sensor lock.
(I thought the sensor is working at all time, so add the light sensor lock would not draing the battery faster)
Is there a way to change where the light sensor readings trigger a change in brightness level?
Currently the phone change from lowest brightness to higher when reads 30lux and change to lowest brightness when reads 10lux.
It's annoying for the phone to change to lowest brightness when i still in a light up room but just pointed away from light sources. And also it's also not switching to higher brightness when i need it in a dim environment.
So, anyone know of some app that can adjust these values? Or point me some direction to work on it.
Light Sensor is Ok, but...
Using z-device test I compared the light sensor readings between SGS2 and the NS. The light sensor seems to be correct. Still, at 10 lux, the SGS2 is setting the brightness value to its lowest and the NS, not.
I'm starting to believe that there is a a problem between the mapping from the light sensor and the brightness level. If I'm not mistaken this can only be fixed/adapted within the ROM.
DoomFragger said:
Using z-device test I compared the light sensor readings between SGS2 and the NS. The light sensor seems to be correct. Still, at 10 lux, the SGS2 is setting the brightness value to its lowest and the NS, not.
I'm starting to believe that there is a a problem between the mapping from the light sensor and the brightness level. If I'm not mistaken this can only be fixed/adapted within the ROM.
Click to expand...
Click to collapse
As from what i read, S2 seems to divide the screen brightness into 5 level
http://forum.xda-developers.com/showthread.php?t=1235212&highlight=auto+brightness
However, the mapping of these five level to it's correspondence light sensors reading seems to be odd.
let's just call lowest brightness as lv1 and highest as lv5,
The phone will stay on lv1 whenever the sensors read from 0-30lux
The phone will drop to lv1 whenever the sensors read 10lux.
The gaps is just too wide to give a pleasant viewing experiences, often stay on lv1 brightness while i'm no longer in pitch black area.
if there is a way to change this, i would prefer to set it as
stay on lv1 whenever sensors read 0-5lux
drop to lv1 whenever sensors read 2lux (the lowest brightness lv is only feasible for me when inside a pitch black environment)
Since there is a file determine it's brightness value for each lv, so i'm thinking there should also one for it's mapping.
hi all, I noticed that light sensor doesnt work properly, when I go from dark to light area, the brightness increases but when I go from light to dark area the brightness wont decrease, on honeycomb it worked properly, anybody else experiences this problem?
Same here, it goes bright but does not decrease.
I use the app https://play.google.com/store/apps/details?id=rubberbigpepper.DisplayBrightness&feature=search_result#?t=W251bGwsMSwxLDEsInJ1YmJlcmJpZ3BlcHBlci5EaXNwbGF5QnJpZ2h0bmVzcyJd
make an invisible slider on the edge of screen to adjust brightness.
is there any way to make it work properly?
Don't think so. Its pretty much unusable now.
Sent from my HUAWEI MediaPad using Tapatalk 2
There are lots of negative comments about light sensor, but i have to say it works well to me on ICS. Could be possibly massive amount of defected devices.
Lightsensor doesn't work for me either - too bad, hope it will be corrected.
Perhaps it's because I'm running ICS "General Channel".
HUAWEI MediaPad FIRMWARE(S7-301u,android4.0,C232B002,General Channel)
Do the sensor dim the light in the same session for you?
Here it turns up the light but not down again.
Sent from my U8800 using Tapatalk 2
Same here, adjusting upwards works fine, but it doesn't adjust downwards in low light conditions.
I have tried two apps that turns the light down again, custom auto brightness and lux auto brightness.
One small problem. The pad will crash on pattern unlock after sleep. I Also the light sensor will not work s after wake up sometimes.
Sent from my HUAWEI MediaPad using Tapatalk 2
mangoman said:
I have tried two apps that turns the light down again, custom auto brightness and lux auto brightness.
One small problem. The pad will crash on pattern unlock after sleep. I Also the light sensor will not work s after wake up sometimes.
Sent from my HUAWEI MediaPad using Tapatalk 2
Click to expand...
Click to collapse
I'm guessing no one has had any luck with this issue but I figure I'd necro the thread anyways. My light sensor sucks also. I used 'Android Sensor Box' to get the values coming out of the sensor. It only displays either 40 lux or 280 lux which is obviously not right. This is on Cyanogen 9, stock t-mobile ICS and the rooted international gingerbread(can't remember which one exactly).
So I was wondering if anyone who owns one of these has ever gotten a sensor value that makes any sense.
thanks
nope,
I use instead display brightness https://play.google.com/store/apps/details?id=rubberbigpepper.DisplayBrightness&hl=no
create an invisible brightness slider on theedge of the screen.
Try using custom auto brightness with the auto brightness on (there's a setting in that app that disabled the system auto brightness at screen on. Turn it off).
The original kernel only recognized 3 light levels. If you use bart's kernel it will recognize 6 levels.
Yes, I think there's a software problem because both app (lux and cua) crash hard in HMP, but I don't think fixing it is a priority.
Sent from my HTC Glacier using Tapatalk 2
How to use custom auto brightness without crashing the tablet.
There are 2 options that should be followed, other settings can be adjusted to your liking.
1. In preferences, Check Use pulsed sensor mode. Basically this option will make the app read the sensor itself instead of listening the sensor value given from the system.
2. In advanced preferences, set the sensor update speed to either half sec or 1 sec. I tried normal, but the app won't read the sensor value, so probably the slow normal maximum setting only works if you get the sensor value from the system.
You can set disable system auto brightness. I recommend it before because the setting was a "hack" which was making the system read the brightness value thus the app can get that value. Right now it's recommended that you check the disable system auto brightness.
The Auto Brightness works well during day time.
It is observed that in low light or total darkness it suddenly becomes zero.
After a couple of screen off/on the Auto brightness works in low light.
Anybody facing this problem??
chet13 said:
The Auto Brightness works well during day time.
It is observed that in low light or total darkness it suddenly becomes zero.
After a couple of screen off/on the Auto brightness works in low light.
Anybody facing this problem??
Click to expand...
Click to collapse
Reboot device or calibrate proximity sensor in phone manager once. Check update and stay updated.
The phone manager has all tests but there is no calibration option.
Did the sensory test and the test result are good.
But the issue is still there , the brightness does not increase in dark/low light
The phone is updated with latest patches.
chet13 said:
The phone manager has all tests but there is no calibration option.
Did the sensory test and the test result are good.
But the issue is still there , the brightness does not increase in dark/low light
The phone is updated with latest patches.
Click to expand...
Click to collapse
Me too experiencing the same thing, I just tried auto brightness off. Seems like a poor calibration.
Hello, I'm using a Samsung Galaxy S7 Edge and I've had this annoying problem ever since I got this phone in 2017. The screen brightness keeps changing automatically even though I turned off auto brightness.
https://streamable.com/c5q9w
Here is a video example. As you can see, the brightness changes by itself when covering the light sensor, even though auto brightness is set to off. It might be hard to see the difference in the video but it's quite noticeable in real life.
Is there a way to fix this?