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.
Related
Hi,
My automatic brightness setting just leaves the brightness exactly on what it was before. E.g If I manually put slider to max, and turn on automatic brightness it stays on max (even if in a dark room), and if I put it minimum and go outside or shine a torch on it, it doesn't go higher at all.
I'm not sure when this first started happening, it always used to, I'm running ARHD 5.1.11 (a ginger-sense rom), with golauncher ex. I can't think what's causing it. Elixir says that the sensor is working (the numbers adjust as I put light on the sensor).
Any ideas would be much appreciated.
Not a direct fix for your problem but I downloaded OnOff Widget Pack. This has a great brightness control. Running Auto Brightness for most situations seems to be a drain on the battery.
I've never been happy with the way the autobrightness works on my phone, and after checking with AndroSensor and the calibration in Total Screen Control, it seems the ambient light sensor doesn't read anything below 160 lux in sense roms, and 320 lux in CM7.
Is there anything that I can do regarding drivers, settings etc. , or is a replacement my only option?
I don't really want to go there, because I paid for a SIM unlock code and everything else is working perfectly, but it annoys me that I have to use workarounds to deal with the brightness, and I always find myself get stuck with an unreadable screen (too dark), when out and about, because I forget to set the brightness higher before leaving.
Can anyone tell me where I can find the relevant files for the ambient light sensor on the Dinc2?
This is where it's at on a Desire, for example:
/sys/devices/i2c-0/0-0066/ls_adc
And what would be a good stock rom to see if it happens with that one, too?
I Honestly just use the quick settings slider to adjust screen brightness
I do, too, but it doesn't do me any good, when I have to use the phone outdoors, and have forgotten to set it to full brightness, before leaving the house!
That happens to me frequently, and the screen is unreadable then, so I can't find the brightness settings.
go to Setting,display.
Well, yes, but if my screen is too dark to see anything, I can't navigate there.
That's why I'm trying to pinpoint the sensor problem, so I can use AutoBrightness.
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!
Well the autobrightness wasn't working as I wanted it to. Never had issues with it before on other devices.
So I downloaded Velis auto brightness
I noticed the sharp brightness sensor was sometimes juming between 2 values like 552 lux and 12 lux causing a constant change off brightness. (flikkering)
Could someone check the brightness sensor, and check if it also fluctuate? My S3 keeps steady values...
I had a faulty pro8.4 (dead pixels) on the first day and the auto focus was also not working properly.So I would like to know wheter I have an other faulty tablet or it is just the sensor that reacts differently.
thanks in advance
I have noticed the same thing. When I am scrolling through a website I notice the flickering brightness. I ended up turning the auto brightness off.
My auto brightness just doesn't seem to work at all. It just defaults to lowest brightness. Funny thing is it worked on first boot, but stopped after the very first time I turned the screen off then back on.
Sent from my Slim Nexus 5 with smoothness by Faux.
I installed CM today and using auto brightness, I can confirm it just goes up and down, dim-bright-dim-bright. It's disappointing that such a nice tablet has a piss-poor brightness sensor.
From my Pro Tab 8.4
My Lux values were all over the place too. Luckily there's an application on the Play Store called Lux which fixes everything. Just set it to adaptive. That's what worked for me.
JaylanPHNX said:
I installed CM today and using auto brightness, I can confirm it just goes up and down, dim-bright-dim-bright. It's disappointing that such a nice tablet has a piss-poor brightness sensor.
From my Pro Tab 8.4
Click to expand...
Click to collapse
Can you go to Settings >> Display >> Brightness and then click the settings icon and then the Adjust button. That should tell you the value of the sensor as seen by CM.
Does it really fluctuate there? If so, can you maybe take a quick video so I can see what you are seeing?
I'm pretty sure this is a hardware issue. My sensor flips +/-1 when I leave the tablet sitting there. Covering the sensor drops in down to about 0 and then it bounces right back to the same value when I uncover the sensor.
mattskr said:
My Lux values were all over the place too. Luckily there's an application on the Play Store called Lux which fixes everything. Just set it to adaptive. That's what worked for me.
Click to expand...
Click to collapse
Wow Thanks so much for suggesting the Lux app. The stock auto brightness jitter was driving me crazy, especially when scrolling around in the playstore.
On a side note, samsung screens are hella bright when viewing at night. Going to put Lux on my phone too lol.
A autobrightness mod I use on my Nexus 10 is the XPosed framework and Gravity box module. Your can set the brightness and lux pair values then reboot. On my Nexus 10 it took three days (night/day) conditions of tuning values until I found the sweet spot. It was not too much of a bother and I've not had to make any adjustments since. Look in Gravity box for display tweaks then all settings can be modified but the pair values mentioned above are under autobrightness levels.
Sent from my Nexus 10 using XDA Premium HD app
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.