Hello,
I find the Ambient Display option quite nice (even just to check the time) but I have some doubts about how it works in a pocket/bag:
If I get a notification while the phone is in my pocket, will Ambient Display trigger? (It's not about the sensors efficiency.)
I don't think so but I'd like to be sure.
Thanks
The proximity and light sensors should prevent it. You can test it by covering them with your finger.
I tested quickly and it seems you're right.
Thanks
Related
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!
This may be a total noob question, but I was just curious to know the exact location of the light sensor because I cant seem to figure out where it is located.
EricSS619 said:
This may be a total noob question, but I was just curious to know the exact location of the light sensor because I cant seem to figure out where it is located.
Click to expand...
Click to collapse
That dot that looks like a front facing camera (FFC) - that is your sensor there that controls screen on/off on calls and the auto brightness.
riggsandroid said:
That dot that looks like a front facing camera (FFC) - that is your sensor there that controls screen on/off on calls and the auto brightness.
Click to expand...
Click to collapse
Are you sure, because when I ran sensor test that dot did change the proximity sensor values, but the light values wouldnt change even if I covered it completely.
The only way I was able to change the light value was to move the whole phone into a darker or brighter location, but not by finding a pinpoint sensor on the phone.
Edit 2: When I cover the proximity sensor dot (the obvious one) with my finger and shine a light at the phone, nothing happens, and when I remove my finger from the dot and shine a light right on it, the screen gets brighter. I suspect both sensors are in the same spot (the plastic dot you see probably transmits ambient light to the light sensor as well as housing the proximity sensor, in the way many computers use a little clear/frosted plastic piece to indicate the status of an LED that is buried in the chassis.
Try it with a flashlight and see if you get different results.
If you are interested in disabling the light sensor go into settings and manually set your brightness.
I have to say the proximity sensor works much better than on my Hero.
Sent from my HTC Evo Shift 4G
i noticed the proximity sensor responds much faster than the one on my Evo
The light sensor is just to the right of the proximity sensor under the speaker grill. Turn on auto-brightness and test it with your finger.
Sent from my PG06100
BrandoKC said:
If you are interested in disabling the light sensor go into settings and manually set your brightness.
I have to say the proximity sensor works much better than on my Hero.
Sent from my HTC Evo Shift 4G
Click to expand...
Click to collapse
thats because i dont believe there is a proximity sensor on the hero.
karnoff said:
thats because i dont believe there is a proximity sensor on the hero.
Click to expand...
Click to collapse
I guess that's why it would be working better!
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!
Hi
I have noticed that the readings from the ambient light sensor on the HTC One are reported as discrete values (10,40,90,160,225,320,640,1280,2600 and finally 10240). On other devices I have experience with, the readings are often continuous.
An other issue is that the so called "ambient" light sensor on the HTC One works more like a spot light sensor, in my opinion. For example standing below a ceiling down light results in a very hight "ambient" light reading even if the actual light (hence ambient light) in the room are pretty dark. Keeping the phone at the same position just angeling it a few degrees any direction will lead to a dramatical drop in the sensor reading. The intervals in between the reported values doesn't exactly help either.
My point is that the ambient light sensor is influenced to much by direct light sources rather than actually register the ambient light in the surroundings. I have not seen similar behavior in other devices from other manufacturers.
I know that the ambient light sensor for the Galaxy SII reported discrete ambient light values with stock kernel, and continuous values with the CM kernel.
Can the HTC One kernel devs change the behavior of the HTC One ambient light sensor the same way? I'm guessing that the reported values are a result of software (kernel/config/other), rather then the actual sensor itself.
I think the behavior of the sensor can explain why the display backlight control of the HTC One seems to be "less" precise, especially in bright condition, and that the display often feels to bright.
On my Galaxy Tab, the ambient light sensor is also reported in discrete value, and it generally doesn't really work with adjusting screen brightness. tbh, the most responsive ambient light sensor i've seen is on the macbook pros.
I have been googling this looking for a solution but i have not found one. I use Sensor Explorer and it reports back that the HTC One light sensor [cm36282] has a resolution of 1 lux, so it should be able to report continuous values at this resolution. How can we enable this? Is this kernel dependent or OS dependent? I wish this issue got more attention, but as i've noticed through my googling i don't find many threads regarding this issue. I would like to have the ability to fully utilize my sensor.
I have an Huawei Watch 2 with ambient light sensor. Many have watches with this sensor (it controls the screen brightness if you have auto set)
I have noticed that when I wear my watch under my jacket sleeve OR if I cover my watch screen - the screen remains on? Why?
My pixel 2 xl has ambient mode display and ambient light sensor - when it's upside down or in my pocket the screen goes off.
I am trying to work out if the behavior of my watch is working correct, does anyone screen go off when covered? If not are there any ways to achieve this?
mrlb said:
if I cover my watch screen - the screen remains on? Why?
Click to expand...
Click to collapse
Go off if you have not always ON or if you not activate by movement.
If you have ALWAYS ON, then...... it ........ ALWAYS ON