Related
Well i am very confused whether our phone has a light sensor or not. In the official user manual of I5801 (English-India), at page number 17, its clearly stated that the left one of the two sensors on top left side of our phone is proximity sensor and the right one is light sensor. If there is one, then why is there not any option for automatic brightness? and what its use is? And if its not there, then why is it given in the User's manual ?
Does anyone have any information on this at all? Was/is there any rom that supported automatic brighness via the light sensor?
So why isn't it included in Samsung' Stock Rom ?
Do you think really that no-one ever try to use it .
nishant_713 said:
Well i am very confused whether our phone has a light sensor or not. In the official user manual of I5801 (English-India), at page number 17, its clearly stated that the left one of the two sensors on top left side of our phone is proximity sensor and the right one is light sensor. If there is one, then why is there not any option for automatic brightness? and what its use is? And if its not there, then why is it given in the User's manual ?
Click to expand...
Click to collapse
There is no light sensor on Galaxy I5800/5801. The proximity sensor is actually a pair of sensors, one sends an electromagnetic/Infrared radiation while the other one is to receive it back for the sensor to get activated.
nsm1234 said:
There is no light sensor on Galaxy I5800/5801. The proximity sensor is actually a pair of sensors, one sends an electromagnetic/Infrared radiation while the other one is to receive it back for the sensor to get activated.
Click to expand...
Click to collapse
Wow, this is kinda shocking news!
is there anyway to calibrate the proximity sensor on the sensation, not 100% sure thats my problem but worth a try if poss
bradmax57 said:
is there anyway to calibrate the proximity sensor on the sensation, not 100% sure thats my problem but worth a try if poss
Click to expand...
Click to collapse
Would like to know this as well.Proximity and light sensors not working properly on my Sensation (only occasionally).
I'd like to know how to recalibrate / get it functioning again.
Yes,i like to know that to.
Still having problems with both proximity and light sensors...
The proximity and light sensors cannot be calibrated, as they put off specific amounts of voltages based on results from the input. It is up to the ROM/Kernel to interpret the voltages from the sensors as usable values to produced the desired results. If you wish, you can download a testing program such as AndroSensor to view the interpreted sensor readings.
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
I noticed the other night as I was using my pixel 2 and viewing a security camera monitor when it's infra-red/night vision was active that the IR beacon on the front of my phone pulses regularly even when I am not using the front camera of my phone, and don't have a camera app running at the time. Does anyone know why the phone is using the IR light and sensor when I'm not using the phones front camera?
I don't think the pixel 2 has an ir on it.
leveleyed said:
I noticed the other night as I was using my pixel 2 and viewing a security camera monitor when it's infra-red/night vision was active that the IR beacon on the front of my phone pulses regularly even when I am not using the front camera of my phone, and don't have a camera app running at the time. Does anyone know why the phone is using the IR light and sensor when I'm not using the phones front camera?
Click to expand...
Click to collapse
Are you talking about the notification LED that sits in the top left hand corner or the camera LED flash? Your confusing me with this infrared/IR business. The pixel 2 doesnt have infrared.
enzyne said:
Are you talking about the notification LED that sits in the top left hand corner or the camera LED flash? Your confusing me with this infrared/IR business. The pixel 2 doesnt have infrared.
Click to expand...
Click to collapse
No, I am certain it is not the notification LED. That is visible in normal lighting conditions. What I am referring to is only visible in night vision, which uses an infrared light and sensor. So this is clearly a blinking infrared light on the top of the front/face of the phone. I believe it is normally used to detect the distance of subject matter to help adjust the front camera focus depth.
Also, I don't know how the "n" in infrared got deleted after I finished typing in the rest of the title for this post, but I assure you that when I typed the word it showed up as "infrared" not "I frared". And now I can't seem to figure out how to edit the title of the post, so I guess it's stuck like this.
I'm starting to wonder if I've stumbled upon something that may be evidence that the phone is always using the front-facing camera - even when the user isn't using the camera or any app that uses the camera. I had my fiancée also come into the room so I could see if the same happened with her iPhone 6. On hers, no light on the front was active until she unlocked the phone. But as soon as she did, an infrared light on the face of it stayed illuminated *constantly*, whereas the one on my pixel 2 just flashes periodically.
My inner conspiracy theorist is starting to wonder WTF is going on here, and why these sensor arrays are active even when the front camera isn't in use.
I'm hoping a well-informed Android or Pixel 2 developer will see this and respond to address these concerns.
leveleyed said:
No, I am certain it is not the notification LED. That is visible in normal lighting conditions. What I am referring to is only visible in night vision, which uses an infrared light and sensor. So this is clearly a blinking infrared light on the top of the front/face of the phone. I believe it is normally used to detect the distance of subject matter to help adjust the front camera focus depth.
Also, I don't know how the "n" in infrared got deleted after I finished typing in the rest of the title for this post, but I assure you that when I typed the word it showed up as "infrared" not "I frared". And now I can't seem to figure out how to edit the title of the post, so I guess it's stuck like this.
I'm starting to wonder if I've stumbled upon something that may be evidence that the phone is always using the front-facing camera - even when the user isn't using the camera or any app that uses the camera. I had my fiancée also come into the room so I could see if the same happened with her iPhone 6. On hers, no light on the front was active until she unlocked the phone. But as soon as she did, an infrared light on the face of it stayed illuminated *constantly*, whereas the one on my pixel 2 just flashes periodically.
My inner conspiracy theorist is starting to wonder WTF is going on here, and why these sensor arrays are active even when the front camera isn't in use.
I'm hoping a well-informed Android or Pixel 2 developer will see this and respond to address these concerns.
Click to expand...
Click to collapse
That's interesting. I will try with my phone and nest camera and see if it acts the same on mine.
I just tested it again, holding the phone at varying angles from the security camera, activating and deactivating its night vision/IR mode to see the difference. I recorded a video of it and will post a link tomorrow. When infrared is active, there is a clearly visible blinking light located in the center of the top of the phone just above the speaker bar (the one to the right of the front camera).
I'm really curious to get to the bottom of this so that I can dismiss the paranoia that big brother is constantly watching me through my phone's camera.
leveleyed said:
I just tested it again, holding the phone at varying angles from the security camera, activating and deactivating its night vision/IR mode to see the difference. I recorded a video of it and will post a link tomorrow. When infrared is active, there is a clearly visible blinking light located in the center of the top of the phone just above the speaker bar (the one to the right of the front camera).
I'm really curious to get to the bottom of this so that I can dismiss the paranoia that big brother is constantly watching me through my phone's camera.
Click to expand...
Click to collapse
?It's the proximity sensor.
ajrty33 said:
?It's the proximity sensor.
Click to expand...
Click to collapse
Exactly!!
But why is the proximity sensory active all the time? Is it so the Ambient display doesn't turn on when face down?
oSandmaNo said:
Exactly!!
But why is the proximity sensory active all the time? Is it so the Ambient display doesn't turn on when face down?
Click to expand...
Click to collapse
Its constantly trying to see if your phone is up to your ear or not.
I'm also wondering why the phone would need to have the proximity sensor active when I'm not using Ambient mode, and not currently engaged in a call. There's no need for it to be using the proximity sensor when I'm just browsing my home screen or using some other app. My phone isn't configured to turn off the screen if I set it face down for awhile or anything like that. So there shouldn't be anything using the proximity sensor.
This is common in modern phones, it's checking if you're holding it, if it if is by your face, in your pocket it allows gestures like wave to wake
Get used to it, it's not going away.
mrkhigh said:
This is common in modern phones, it's checking if you're holding it, if it if is by your face, in your pocket it allows gestures like wave to wake
Get used to it, it's not going away.
Click to expand...
Click to collapse
But the pixel doesn't have any of those features.
if u want to turn the sensor, disable all option in ambient display.
koax88 said:
if u want to turn the sensor, disable all option in ambient display.
Click to expand...
Click to collapse
Nope. I tested that a few months ago (this isn't the first time this has been spotted). You can turn the ambient display off completely and the sensor is still active.
Unless of course they've realised in the meanwhile that this is pointless and fixed it in a software update - I've not retested it recently.
Large Hadron said:
Nope. I tested that a few months ago (this isn't the first time this has been spotted). You can turn the ambient display off completely and the sensor is still active.
Unless of course they've realised in the meanwhile that this is pointless and fixed it in a software update - I've not retested it recently.
Click to expand...
Click to collapse
I Just tested my phone, the sensor did not blink at all if u turn off all setting in the ambient Display section. Even double tap to wake will make the sensor blink. I noticed this since 8.0 tho.
Sent from my Pixel 2 using Tapatalk
oSandmaNo said:
But the pixel doesn't have any of those features.
Click to expand...
Click to collapse
It certainly does. I use it to keep the screen off when my phone, in an Otterbox Defender, is in the holster, or when I lay it down face down. Both the front and rear cameras can see into the infrared. Just aim a TV remote at them when any camera app is running and press a button and you'll see the remote's IR LED going. (It has no IR output, though.)
HELLO
I am from Pakistan
My poco x3 pro become dead after update on miui 13 luckily I had a warranty and sent to service center
They sent me back after a month and now it have new problem in it
My proximity sensor is not working
Properly facing problem during calls
Now I see this proximity sensor works sometimes when phone little heated so I heat my phone with hair dryer and check it works perfectly until it cold down to normal temperature
Please help me somebody how to tackle this issue