Hey guys,
I've noticed this weird behavior and I was wondering whether anybody else came across this: if the auto brightness is ON and the light sensor is exposed to stronger light, it increases the screen brightness accordingly (so far so good!) - HOWEVER the weird thing is that when the ambient light diminishes (even when the sensor is completely covered) the screen brightness goes down ONLY if/when the phone is tilted back - facing up. The screen (auto) dimming seem to be interlocked with the accelerometer sensor - in other words, it doesn't react to ambient light changes until the phone is tilted back (or by the screen timeout).
To recap: in stronger ambient light, the screen brightness does increase automatically but when the ambient light dims down, the screen brightness gets adjusted (lowered) ONLY if the phone is tilted back (screen facing up).
On the other hand the light sensor test (*#0*#) shows no problems whatsoever - the lux value changes accordingly/dynamically, whether vertical or tilted - everything seems fine.
Even after a factory reset the symptom was still the same - anybody else noticed this?
My environment:
- SGH-I317M
- Stock 4.1.2, rooted
Thanks
PS: Please don't come recommending 3rd party apps that may resolve this issue. I'm interested in tackling THIS very specific occurrence.
-----------------------------------------------------------------------------------------------------------------------------------
EDITED: After some digging, it seems the whole culprit lays with 4.1.2. I reverted to 4.1.1 (clean) and this problem doesn't exist. As soon as I put back 4.1.2 (clean, not from nandroid) the symptom came again as described. Also confirmed by demo models from 3 carriers - being on 4.1.1.
Galaxy S2 with 4.1.2 also seems to be affected (even worse).
Please confirm/comment!
Related
Hi,
My automatic brightness was not working properly so i downloaded sensor test. The sensor works fine but it cuts in and out.
It keeps switching from 10/10 to the real value than back to 10/10.
Any ideas on how to fix this?
Was working fine before i installed cyano
Thanks
Bumping this as I have a similar problem.
The sensor doesn't seem to recognise any light values between 10 and 300-350, it either says it's pitch dark or that I'm outdoors (checked with two different light sensor apps). I'm using the stable release of CM7.
It's causing problems with automatic brightness obviously, as I can only adjust the settings to either have a dimmed screen during the day, or have my eyes burnt out when it's actually pitch dark.
Any ideas?
CM7 has settings for auto brightness and it actually works. They're in the CM settings.
I've got a bog stock Desire running 2.2 and according to Sensor Test, the light sensor doesn't work at all!
Sometimes this has happend to me in CM7... but I reset the levels then it was working gud....
http://forum.xda-developers.com/showthread.php?t=1003592
you can check this thread where all the levels are explained in detail for CM7
CM7 has its own brightness levels... but they are somewhat slow to update. I've tried changing their values - but it only helps a bit.
I must say that I was testing it indoors... not outdoors.
I was wondering if someone has noticed similar behavior on their G3. My G3 is 100% stock and is only a week old. Wherever I wake up my device, about 5 seconds after turning it the screen has a small flicker and the screen seems to auto adjust or calibrate. This only happens once every time I wake up the device. My auto-brightness is set to off and the screen is at 100% brightness. I did some tests and noticed that when I wake up the device with the top sensors covered (proximity, front camera etc), that the screen doesn't have this flick to it. Is there some sort of "outdoor" mode or something on these where the screen will self calibrate when it notices it's in a bright situation?
Please test on your devices and let me know if you see anything similar to this. I tried taking a video but it's so quick and subtle that the video doesn't show it.
mine does same. vzw. covered sensors, still brightness adjustment.
only just now noticed today, but could have been happening all along.
I think it has something do with the proximity sensor. If you cover the sensor with a note pad you cannot turn on the screen, prob a tap to wake feature so it doesn't turn on in your pocket. But if you lift the note pad just enough to turn the screen on and quickly cover it, mine does not flick. I have tried this many times and worked 100% of the times.
My friend who works for at said that his does the same as well as the demo. Must be a weird firmware issue. Hopefully its resolved in the next ota
How many times are you gonna make this thread?
http://forum.xda-developers.com/lg-g3/help/screen-flicker-t2826882
I have this strange issue with the light sensor, the reported lux oscillate to often, it can go from 40lux to 1lux for a split second then jump back to 40lux.
Sometime the sensor remain locked to 0 or 1lux, leading the screen to dim way to much with auto brightness on to a point it become unreadable, so I have to point the light sensor toward the window to unlock the reading, very annoying.
Best solution I found until now is disable auto-brightness, but it's also annoying to have to consistently adjust it manually.
Have the same issue with CM11 and CM12, didn't tested stock firmware though.
Am I the only one facing this issue ?
Hi all, despite 3.2.6 update which has improved auto brightness performance, is still quite far from being good.
The problem is when the phone is unlocked directly under light or in bright environment. After moving to darker environment the display doesn't dim by itself. It has to be turned off and on to successfully adapt. But in opposite way, it works. When turned on in dark, it adapts correctly after going to the light.
It has to be issue within OOS, because on customs roms (cm,aosp based) autobrightness works perfectly. Maybe it is weird but it's bothering me quite a lot
Is there any way how to fix it? Other then install lux, which breaks ability to give permissions due to overlay error.
capt_f0r3st said:
Hi all, despite 3.2.6 update which has improved auto brightness performance, is still quite far from being good.
The problem is when the phone is unlocked directly under light or in bright environment. After moving to darker environment the display doesn't dim by itself. It has to be turned off and on to successfully adapt. But in opposite way, it works. When turned on in dark, it adapts correctly after going to the light.
It has to be issue within OOS, because on customs roms (cm,aosp based) autobrightness works perfectly. Maybe it is weird but it's bothering me quite a lot
Is there any way how to fix it? Other then install lux, which breaks ability to give permissions due to overlay error.
Click to expand...
Click to collapse
According to Carl Pie, OnePlus messed up initially on the auto brightness. However, they have rectified it and the current stock implementation is as follows: when you move to a brighter area and unlock the screen, the screen immediately adjusts for the light making the display brighter. But when you move to a darker area, the adjustment is not immediate but it will darken slowly. This is intentional. After moving to a darker area, leave the screen on for sometime and check whether it darkens. If even after some time it doesn't, then it is an issue.
Got a Pixel 2 xl off ebay and everything seems fine just the ambient display (always on) screen flickers at middle brightness. In the dark it is fine and the bright light it is fine just mid brightness I can notice it. Has anyone else noticed this? Pretty happy with the phone so far and know the camera will make up for anything just find it pretty annoying at times.
Also the fingerprint sensor is random, sometimes it works other times it won't recognize the print others it says the sensor is dirty. Thinking this phone has a couple of hardware faults and that I should sent it back but for £300 I don't know if it was worth it,any thoughts??
Did hard rest no luck with that so going to try development package, then maybe custom rom to see if they can iron out the issues.
I disabled "New Notifications" toggle from the Settings which keeps the ambient display on but does not wake the phone up and show lock screen for new notifications. Seems to work.
I guess the problem is about this new "Silent Notifications". You can not see them but they come and go momentarily waking the phone up.