Proximity sensor red faint light always on now , randomly turned on not sure why....
I have no motion things enabled
I tried turning off proximity sensor for phone
Ive rebooted several times
Ive turned off auto brightness
Im running the stock s3 rom rooted.
Anyone have any ideas how i can fix this?
Hmm.. My quick research of this makes me think you have a rogue app, a sticky setting or a defective sensor.
Let's be sure we're looking at the right thing. Your faint red light is just to the left of the front camera lens, correct? If so, then it's a definite indication that you're proximity sensor is on and constantly taking a reading.
Is it always on, from power on to power off? Or does it turn on once the phone has booted up? Does it stay on long after the screen shuts off during idle?
This sensor is used by motion features and talking functions. Triple check that you don't have 'smart stay' turned on, or one of the other super cool gs3 features enabled. I'd consider turning them all on manually, rebooting and then turning them all off followed by another reboot.
Lastly, take a look at your apps. Any kind of app that involves motion or talking (Voxer, Skype, certain games etc) can activate the proximity sensor and keep it on. A lot of those apps start on boot and never go away. Close them one at a time, or consider uninstalling suspect apps temporarily.
As a hardware test you can install Elixer2 from the play store (for free). Its sensors section allows you to turn the proximity sensor on and off, as well as test the near and far readings. If all else has failed, it might be nice to know that at the very least, your sensor can be turned off.
Report back with results from everything and we'll go from there.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
Well i was using Viber, when i turned it off manually, the red sensor light went off. So it must be ab application that is keeping that sensor on all the time. Smart stay does not need proximity sensor and enabling or disabling it causes no change to sensors. Hope this will help ya
Sent from Galaxy Class Android using Tapatalk 2
Thank you so much for the awesome response. I didn't find any other similar responses on the Internet other then " oh that's just the ir sensor don't worry about it". I too have viber and I believe that was the app causing the issue because of the way it integrates itself with the phone, can't be certain because so many apps updated as of late but it is gone now thankfully.
I get this when I`m in a dark room. The sensor will turn on. The only way to correct it is to restart the phone.
Plausible Solution
I don't know if this works 100% of the time, but it HAS worked for me. Go to your Viber application, menu, and then EXIT the app. Viber seems to be the culprit, so if you find exiting the app manually every time bothersome, you might be better off uninstalling the thing. Click the Thanks button if it helps =p
In pocket detection on?
Sent from my DROID BIONIC using xda app-developers app
Disable Proximity Sensor
I´m trying to disable my proximity sensor in GS3. I tried with Hardware Disabler and doesn´t work, and the Elixir2 can´t disable the sensors.
Does anyone know another app to disable the proximity sensor?
Garouto said:
I´m trying to disable my proximity sensor in GS3. I tried with Hardware Disabler and doesn´t work, and the Elixir2 can´t disable the sensors.
Does anyone know another app to disable the proximity sensor?
Click to expand...
Click to collapse
x2. bump
Related
Hi,
Just noticed yesterday evening that something is lighting at the top of my HOX, see photo attached.
And it is barely visible, only when you are in dark place, but seems more in infrared...
What is this?
After reboot it turns off, but then on again...
It looks like the proximity sensor to me. Anybody, feel free to correct me.
It's been reported that Viber is turning this light on, but never happened to me.
[email protected]|-|oR said:
It looks like the proximity sensor to me. Anybody, feel free to correct me.
It's been reported that Viber is turning this light on, but never happened to me.
Click to expand...
Click to collapse
yep, its the proximity sensor, should only be visible to a camera though, its like the led on a remote control ... outside the human eyes visible spectrum ?
strange
Exiting viber solved a few people's problem.
Sent from my HTC One X using Tapatalk 2
That's the proximity sensor. It's visible to the naked eye when it's on, though it's somewhat dim. As others have noted, it seems Viber is to blame.
Yes, you are right. It is proximity sensor and Viber turns it on.
Thanks!
Anybody know why Viber is doing this? What does it need the sensor for in the first place?
By the way, there is also thread about this http://forum.xda-developers.com/showthread.php?t=1633148
It is a proximity sensor from what I've read.
It's interesting to note that it's not only Viber that causes it to turn on.
I'm on SlimBean 2.5 with ncx 7.5 kernel and it appears whenever I make a call as well.
It's used to turn off the screen when you have the phone to your ear during a call. Never works at night for me, I often disable wifi or put it in flight mode with my ear.
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
Today I noticed a dimly lit red light from the second dot to the left of the front camera staying continuously on even when the display is turned off. I am not mentioning about the notification light that is placed to the left side. I tried many options but it stayed dimly lit. Later I thought of restarting the device and that did turn it off. This did show up as bright red for a moment when I turned on the device which later turned off.
Any idea what made it stay continuously on?
Sent from my GT-N7100 using xda app-developers app
I was having similar problem with gs3,turned out to be viber I guess...uninstall it and report again.
I don't have the viber app installed. By the way what is this led called and what is its function?
Thanks
Sent from my GT-N7100 using xda app-developers app
If its not the proper led then it must be proximity sensor(uses infrared light to detect proximity)
Normally turns on when u get a call to turn of screen when u hold close to your face.if its not viber then it might be what's app or Skype god knows what(may be try freezing phone apps one by one and find out for yourself)
Its not a bug or anything. Its meant to stay lit this way because its a proximity sensor.
turn off smart stay and anything else you might not need and it will go away
turn this off by go - Setting>Motion> Quick Glance: untick :good:
As I said it went off by restarting. I don't have the problem now to check any solution. Just was curious to know what was it.
While it was on, it stayed on even during the call or even when the display was turned off. I did not have any motion setting enabled.
Thanks everyone for your kind replies. I will see if I get the problem again
Sent from my GT-N7100 using xda app-developers app
I noticed that too, then I realized what was causing this. It's the Quick Glance function on "Motion" that's triggering this, because while the screen is off the phone's proximity sensor checks whether or not you have your hand in front of the screen for activating Quick Glance. In order to do that, the sensor must continously stay on, hence the continous red light.
Hi,
The proximity sensor on my Galaxy Note 2 has broken, which means as soon as a I make a phone call the screen goes black and I can't end the call or wake the screen up.
In touchwiz there is an option to disable the proximity sensor during calls but I'm using an AOSP rom, I have had a look in all the settings and there is nothing about disabling the proximity sensor during calls.
The sensor is called "cm36651", I have tried to disable it using Hardware Disabler but I can't find it in the list of devices even when I search from "/".
So does anyone know another method of disabling the proximity sensor?
Thanks
Go into the phone app. Click settings. Untick the turn on proximity sensor during calls.
Sent from my GT-N7105 using XDA Premium 4 mobile app
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
During calls, does your screen turns on again if you shine the proximity sensor under a bright source of light? If yes, all you need to do is recalibrate. I had the same thing happening.
http://forum.xda-developers.com/showthread.php?t=2045569
Sent from my GT-N7105 using xda app-developers app
spigget said:
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
Click to expand...
Click to collapse
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
costcutter said:
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
Click to expand...
Click to collapse
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
CanadianKB said:
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
Click to expand...
Click to collapse
I Got It! Click Here --------> https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix ... the app is call Proximity Fixer i have a Note 2 Verizon running on CM 11 and it works perfectly :good: :laugh:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
disable prox sensor
j3oomerang said:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
Click to expand...
Click to collapse
I tried everything I could find, including several root programs, and nothing would keep my screen from going black when I made phone calls on Nexus 5 (after broken screen replaced). Tried every single proximity sensor "fix", and disabler app but nothing worked. The Sensor kept showing 0.0 meaning it though it was right up against an object.
I finally put a piece of foil in front of the sensor, and now it reads 5.0 (max distance) and FINALLY the screen stays on in phone calls - unless I tap the power button to shut it off.
There must be some factory calibration they do with the original screen, and any replacement one is just not quite exactly the same.
I've been using Tasker to keep my phone off in my pocket with a combination of 'orientation on right side' and 'proximity sensor' active. Googling a bit, I see some mention about a software upgrade breaking the proximity sensor not long ago.
Anyone know more about it? Sensor seems to work ok when phone is on - maybe it got broken for non-phone things?
(note - turned off double-tap to wake & lift to wake to try to keep phone off when in my pocket)
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
jemfalor said:
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now - actually that won't work, would require the camera to always be on.
Hmm.
polstein said:
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now.
Click to expand...
Click to collapse
tried. had tasker as well and was relying on proximity sensor. gave up
jemfalor said:
tried. had tasker as well and was relying on proximity sensor. gave up
Click to expand...
Click to collapse
I was trying to play with the light sensor with no luck - so I stripped my profile down to just Orientation Right Side = off...and it failed. The screen off works when i manually test it in Tasker, not sure why orientation fails too.
Maybe this is for another thread - what the heck are people that keep the phone in their pockets doing? I've read keep screen away from leg which is a pain for me and the flygrip I use on my phone. Must be a better way!