Does Cyanogenmod modify how the ambient light sensor works? My E4GT sucks at adjusting because it does it to often to drastically and to quickly. I have a touchpad that when running webos it controls ambient light sensor very different than the cyanogenmod does.
If that is not part of the rom is there a way to modify/improve how the sensor works?
PS i know there is an alpha.
Should I take that as a no?
If its a no is there something I can do to improve the way the sensor responds?
My main reason is when holding the phone horizontally and my hand goes slightly over the sensor it darkens so quickly, its just annoying.
Related
I couldn't find the original thread about this, so I'm making a new one
http://dl.dropbox.com/u/71410276/VIDEO0004.3gp
Theres a video where i film after the 1.28 patch, and as you can see the top isnt making that weird thing anymore, Its just the screen flickering or how i should call it.
You barely see it, but you can see in the video that theres something happening when im moving up and down.
i think the problem is by the ambient light sensor beside the hTC logo
so when your fingertip pass thru the sensor, the light enter reduce so it become brighter...
_______________________________________
What is an ambient light sensor on a monitor?
It Is A Sensor That Detect Light So If Its Dark Your Screen Monitor Brightness Will dim down so you're not looking at one source of extreme bright light, When Its Bright The Screen Monitor Will go up to compensate for the extra light around you so you can still see the monitor comfortably
Reference from http://wiki.answers.com/Q/What_is_an_ambient_light_sensor_on_a_monitor
tabobaby said:
i think the problem is by the ambient light sensor beside the hTC logo
so when your fingertip pass thru the sensor, the light enter reduce so it become brighter...
_______________________________________
What is an ambient light sensor on a monitor?
It Is A Sensor That Detect Light So If Its Dark Your Screen Monitor Brightness Will dim down so you're not looking at one source of extreme bright light, When Its Bright The Screen Monitor Will go up to compensate for the extra light around you so you can still see the monitor comfortably
Reference from http://wiki.answers.com/Q/What_is_an_ambient_light_sensor_on_a_monitor
Click to expand...
Click to collapse
No, that's not it. It's a software bug, the fixed it just a little. It's probably driver problems still. If it was the light sensor it would just dim, not blink.
still the bug is there.. but less than before.. mine screen flickers (not the screen flicking bug) when the bug hits.. just in an instance.. and distorted the date a little than before.. updated to 1.28.415.9 Arabic version
Well mine still makes the thing where everything in the bar gets all blurry.
Just not as often.
So the bug is still there but they sure did something to improve it
Edit: yeah ayan15 did a good description of my bug
Sent from my HTC One X using XDA
Is there any way to calibrate the light sensor? It works when under direct light from a strong lightsource.
Sometimes when im getting calls, it just get stuck, and keep locking the screen.
And it never works other then under a lamp, for example.
If its not possible, can i turn it off permanently?
you are confusing Ambient light sensor with proximity sensor. (they are both built into the same unit)
They are both located approximately 1cm left of the htc-logo-right-under-the-earpiece
Ambient light sensor is responsible for autobrightness.
Proximity sensor is responsible for checking if anything is close to the earpiece(your ears during calls)
proximity sensor turns on an extremely dull-red light(infra-red) which may not be visible to some people (you can see it clearly through another phone camera)
About your first problem you can simply look in the market for an Autobrightness app and turn off system autobrightness(you can choose what brightness at what sensor reading)
About your second problem it seems its a bug, probably in most cases i've seen in this forum caused by Viber app (or any other data-calling apps), either try uninstalling those apps or choose in their settings not to control normal phone calls and proximity sensor.
Give feedback if it works
O and yeah, this have been "working" with venomrom, simply pressing power button, to turn screen on, mostly,
But now when i installed CM10, I simply cant turn screen on, by pressing the power button, so i have to turn off the device.
There are 2 different sensors that you're talking about. Ambient light sensor and proximity sensor. The proximity sensor turns off the screen completely when you're in a call and it senses your head up against the phone. The ambient light sensor will only chance the screen brightness. You can tweak values for the screen brightness but not that I'm aware for the proximity sensor (turning the screen off completely).
---------- Post added at 03:08 AM ---------- Previous post was at 03:06 AM ----------
That "screen of death" problem is only with the latest builds of CM10 as far as i know. If you go back to a beta / sense ROM you should stop getting these. Nightlies will always have these kind of bugs.
Alright, what im meant is the Proximity sensor. This happend after my phone got a new screen from repairment. (Dont wanna sent it back, way to slow)
When i start a phonecall, the screen goes off, and during that call i cant get the screen back on. Have to longpress the power button, to reboot the device
And now the device is completely fresh installed with CM10
I had the same problem after a repair. Thought it was just a bad install but the problem was persistent. Even on other Roms. It was a hw problem. Hopefully for you its not that.
Sent from my HTC One X using xda app-developers app
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!
Hi Guys I just wanted to know if Ambient Light Sensor is working or Not, As I have enabled Developer Options and in that when I press Manufacturer Tab then I see the Hardware Testing.
When I press Ambient Light Sensor it shows 0.0 , is it same for everyone or just me?
Also How can I test that Ambient Light Sensor is working or not?
Thanks and Regards
abbychauhan said:
Hi Guys I just wanted to know if Ambient Light Sensor is working or Not, As I have enabled Developer Options and in that when I press Manufacturer Tab then I see the Hardware Testing.
When I press Ambient Light Sensor it shows 0.0 , is it same for everyone or just me?
Also How can I test that Ambient Light Sensor is working or not?
Thanks and Regards
Click to expand...
Click to collapse
It's highly directional. If you're in a dim room, it will sit at zero until you aim it at a light. It's not very sensitive in low light, but past some threshold it will jump up. If you can't get it to change when you shine a light on it, I think you've got a problem.
Working for me in my office ...depending on whether I cover the light/lamp or not the ambient light sensor reading is changing...even when I just tilt the watch a bit....I am on 5.0.2...never checked before...
The notification led is connected to the ambient light sensor so in a dark room the led is dim, in a light room the led is bright.
However if you're out and about in even a slightly bright day and take your phone out of your pocket (which is dark) you can barely see the led because it's been in your dark pocket.
This isn't a hardware limitation, if you install Resurrection Remix or Liniage OS the led is bright all the time.
I'm running a stock based custom os because of the camera quality.
I just wondered if anybody has worked out a way to either disconnect the led from the ambient light sensor or even disable the light sensor all together... I don't use it.
I've tried the Xposed Sensor disabled but it didn't work on either BRF5 or ARC5
batfink1 said:
The notification led is connected to the ambient light sensor so in a dark room the led is dim, in a light room the led is bright.
However if you're out and about in even a slightly bright day and take your phone out of your pocket (which is dark) you can barely see the led because it's been in your dark pocket.
This isn't a hardware limitation, if you install Resurrection Remix or Liniage OS the led is bright all the time.
I'm running a stock based custom os because of the camera quality.
I just wondered if anybody has worked out a way to either disconnect the led from the ambient light sensor or even disable the light sensor all together... I don't use it.
I've tried the Xposed Sensor disabled but it didn't work on either BRF5 or ARC5
Click to expand...
Click to collapse
Turn off Automatic screen brightness? Is the LED not connected to the screens brightness level?
Ummm, actually when I said I don't use the light sensor, I figured it was obvious that I don't use automatic screen brightness (since it uses the ambient light sensor).
Anyway, no.. The led isn't connected to the screen, it's connected to the same sensor as the screen... The ambient light sensor.
You can tell the screen to ignore the ambient light sensor by turning off automatic screen brightness, that however doesn't turn off the sensor.. So the notification led is still controlled by the light sensor.
Have you tried any of the notification apps on Play or Samsung Appstore? There's quite a few free ones available on Play but I've never had the need to try any on this phone.
I've tried them all, I like lightflow the best.
They let you control the brightness up to 100%, but that's 100% of the brightness controlled by the ambient light sensor which in turn answers to the Samsung software.
*Sigh*, if I can't find an answer, I might take my balls in my hand and open one of the phones and physically disconnect the sensor.. It's only a cable with a plug.
I also have an S8+ and it does the same thing.
batfink1 said:
I've tried them all, I like lightflow the best.
They let you control the brightness up to 100%, but that's 100% of the brightness controlled by the ambient light sensor which in turn answers to the Samsung software.
*Sigh*, if I can't find an answer, I might take my balls in my hand and open one of the phones and physically disconnect the sensor.. It's only a cable with a plug.
I also have an S8+ and it does the same thing.
Click to expand...
Click to collapse
LOL, if you do let us know how it comes out.....the sensor not the balls.
Has anyone solved the troublesome problem?