According to the Leo/Linux status wiki (http://htc-linux.org/wiki/index.php?title=Leo/Status) the Ambient Light Sensor is still not working properly.
That would explain why auto backlight adjustment does not work.
However, when in the phone screen the light sensor seems to work in that the screen goes dark when I cover the light sensor, as expected.
So I am curious as to the status of this regarding auto backlight specifically, does anyone have any more concrete info?
Perhaps there are separate light sensors? Or perhaps the light sensor only works in a limited fashion for the time being?
Just curious, not complaining
(P.S. the free "Battery Level" widget from the Market has worked well for me in the absence of auto backlight adjustment, in case others find it useful)
well there's a proximity sensor on the phone that comes into play while you are in an active call. it disables the back as you put the phone to your ear. you were simply simulating that action by covering the sensor with your hand.
Ah ok! Thats what the proximity sensor is. That is indeed marked as working on the status wiki, so that makes sense.
Thanks!
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
I tried with Sensor List and it does indeed show up the sensor, but doesn't seem to be getting any data from it. So it's not just your tablet.
Same thing with "AndroSensor", it shows it but no data change in it either. Hopefully we can figure out what the issues is? Are both of you using the factory install rom? Or a rooted one with a tweaked kernel?
sda.171 said:
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
Click to expand...
Click to collapse
I got Sensorlist and tried it and I do get data from it.
xhz/xxxx or xxxxxms and a red line. The upper limit is 227 and lower limit is -227 and the red checked number changes. It's nowhere as quickscrolling as the other sensors but I get a jagged red line moving across.
okay guyz i think i figured this whole thing out most probably-
I just came back from this electronic store, i closely examined the iconia on display- a500 - noticed the black glass under the volume rocker and rotation lock and THE LIGHT SENSOR WAS THERE! :O - looking like just any ordinary light sensor-
This made me come up to the following conclusions- since i have had another iconia before i returned it for warranty- i was able to identify the following differences-
1st variant-model
Light sensor present
Mic volume low
Volume locker button hard to push
Power button sorta pushed inside
2nd variant model -( the one i currently have)
Light sensor absent? Or hidden under black glass? (Manufacturing defect?)
Loose rotation lock (hardware) toggle
Mic volume high (as in proper)
-(i faced these additional problems)-> glass over the camera came off and the glossy label on the side slipped out.
So if u have the first variant, the one i previously had and the one i examined in the shop today- that should give u data from the light sensor, and the 2nd variant with hidden/absent light sensor won`t.
These are my findings. Feel free to point out and discuss-
What should we do? I m considering a second replacement now -_____-
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
I appear to have what you call the second variant model. I just checked with Androsensor, and the light sensor does appear to be present beneath the black glass, just under the volume up rocker. I agree it does appear to sleep until it senses a light source.
cm0901 said:
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
Click to expand...
Click to collapse
I just downloaded andro sensor-
Under light sensor it sed-waiting for event-
I took my hd2, turned on the flash! Pointed it right above the sensor and no response, it just kept saying waiting for event- so does this mean i have a defective sensor?
Can this be a kernel/rom related issue?
Pls someone try this and let us all noe.
Thanks
It's a long shot but you might attempt flipping the check mark a few times under the brightness setting and "auto adjust" as that probably toggles the sensor as well, though these apps are supposed to do it. Or close and start the app a few times and then check the sensor. I don't know what activates it but I can confirm that it has some kind of threshold where it sleeps or isn't active and another where it is, so you might want to try various things to, as others have mentioned, wake it up.
Are you using any ROMS by any chance or are you on stock? Have you done any sort of modification of the system - rooted and removed things or replaced kernels, etc?
If you are on a ROM or have done any modifications, you may want to try going back to full stock 3.2 or 3.1 and seeing if that helps before you decide it's actually defective.
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
KILLER_K said:
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
Click to expand...
Click to collapse
Same as Killer, seems to be working, rooted 3.2, couldnt see until bright light on it.
Anyone have any idea where the mic(s) are, not really important just wanna know which end to scream into when doing voice search
Mic is located directly in the top center of the front face, in the space between the glass and the bezel. You should be able to see it with just a small amount of light shining on it.
FINALLY!
after various non stop auto brightness toggle on and offs - waiting for event went and 1 lux came xD - i shone light the reading increased - and stopped working agen :|
I dunnu maybe the apps are not fully compatible.
I can say it is working because i changed my brightness to full manually and then turned auto on and the brightness level set itself automatically.
So will we have to wake up the sensor from a state of sleep all the time or is it just for the apps xP - last confusion.
Thanks every1 for ur responses, the mystery is finally coming to an end xD!
I've been having an issue with both the proximity sensor and the light sensor. If I press the phone against my face it'll start pressing numbers or disconnecting calls (screen won't turn off due to the sensor not working) and the light sensor doesn't affect the illumination levels on my screen and buttons; actually the only way to make my buttons light up is manually changing the brightness (both screen and buttons) but after locking the phone and waking it back up the buttons stay unlit.
Has anyone else had this problem? I'm not sure if I've been having it after flashing CM9 or after my phone got a bit wet. I took the phone apart to check if something was wrong with the sensors (obstruction, dirt, corrosion, etc) but couldn't find anything.
Also, I downloaded "Sensors List" from the Play Store and both sensors are not detected.
Any ideas?
Idea...
About button light... Is your display brightness set to Auto? If not, set it to auto and your buttons will be fine.
I just tried doing that and it didn't worked, not even completely removing the screw. I guess the sensors got damaged with water (if they can be damaged that way). Oh, and setting the brightness to Automatic doesn't do anything either.
Thanks a lot though.
The N10 auto-brightness feature doesn't work right, as everyone knows. It randomly dims and brightens in an annoying way. I'd read it was a software issue - something to do with JB 4.2 - so I tried two different auto-brightness apps from Google Play, both of which get good ratings, and to my surprise I had the same problem with both of them. When the brightness depends on my N10's light sensor, the screen keeps dimming and brightening randomly. The app I have installed (but disabled) now is "Custom Auto Brightness". I wish I could use it because it looks very good.
The fact that the problem appears regardless of the software suggests to me that the problem is in the hardware - there's something wrong with the data put out by the light sensor. Does anyone have any info or insight about this? A workaround would be so nice.
On the lock screen and ambient display, the display doesn't respect night mode. It is always in "day" mode. Once it unlocks, it fades to night mode. Has anyone else experienced this? Is there a fix to enable night mode on the lock screen/ambient display?
Bump. Has anybody else noticed this?
rriegner said:
Bump. Has anybody else noticed this?
Click to expand...
Click to collapse
From several reviews Ive seen the fingerprint sensor needs to flash at max brightness to work then the screen will go to whatever brightness you've selected
mpetruzz said:
From several reviews Ive seen the fingerprint sensor needs to flash at max brightness to work then the screen will go to whatever brightness you've selected
Click to expand...
Click to collapse
It's not the brightness that's the issue though, it's the fact that it's not tinted yellow for night mode.
The brightness flash is still unnecessary though. When registering a fingerprint, the rest of the display is dim, while the green circle is full brightness. There's no reason they can't do the same thing on the lock screen.
While verifying that fact though, I noticed that the fingerprint registration page disables night mode as well, so I guess it is a fingerprint thing after all. I still think it could be implemented better. I wonder if it's possible to counteract the tint from night mode on just the fingerprint sensor light.
I've found the same. A bit annoying. There should be an option in night maybe to disable fingerprint when night mode is on