*DELETED"
*deletedDeleted*
*deleted-deleted*
Added some basic testing how-to. Let me know "ok" or "not ok". I will have to return my phone today if this is not a generic issue
250 views - no responses from the nexus owners?
anyhow, just realised LIGHT sensor works in daylight (at least from 10 to 160 lux). However, still no cookie on the proximity sensor - can anyone confirm or deny please?
My prox sensor works just fine. Not really had chance to check the light sensor as Ive only just bought the phone and had it set to full brightness. Ill post back shortly..
mine seems to be functioning fine here.
Sent from my Galaxy Nexus using Tapatalk
Right then i can confirm the light sensor works in mine too in daylight
Proximity sensor not though... anyone else?! this is really strange
Both work on mine.
Sent from my Galaxy Nexus using XDA App
Mine is OK as well.
Mine seems fine for both
Both work perfectly on mine! For the proximity sensor, try it during a call! It might be trivial but just saying.
Sent from my Galaxy Nexus using xda premium
AndroSensor says both work but auto brightness (auto dullness?) is useless and I triggered a keypad press while on a call...
Sent from my Galaxy Nexus using xda premium
xtrawise said:
AndroSensor says both work but auto brightness (auto dullness?) is useless and I triggered a keypad press while on a call...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
see - thats exactly the point. The sensor does NOT work (on mine)
Proximity Sensor - will switch display off to avoid the keypress or other issues while on call when you are holding it to your face(ear). And re-enable display when moved away from the face
Autobrigh: measures ambient light and then adjusts brightness accordingly
you may have both confused?
check with AndroSensor:
proximity sensor - cover it with your hand (next to the front camera) and the values should change in AndroSensor - but they dont. neither does the display switch off during calls when detecting your face (actually just detecting "no light")
I will return my GN. I had enough.
The light sensor works according to AndroSensor but auto brightness simply dims the screen to a useless level. Likewise proximity sensor works (values are either 0 or 2 inches) but whilst the screen does indeed dim during calls key presses are still possible infuriatingly. Software fix would cure both.
Sent from my Galaxy Nexus using xda premium
Light sensor works fine.
Proximity sensor does not work. I think it stopped working after the volume fix OTA.
For my device, the proximity value changes fine however the screen doesn't turn on off when answering and ending a call. hv to lock the screen and unlock the screen manually to prevent mistouch..
Just tested and the screen turns off just fine for me on a call.
Sent from my Galaxy Nexus using Tapatalk
I know this topic is kind of old, but I'm still having the proximity issue, do you think I should return my nexus?
Mine doesn't work either, since 4.02 I think. Are there any settings that should be enabled for it to work like gprs or location services or is the proximity service always running?
Sent from my Galaxy Nexus using Tapatalk
Related
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
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.
Ambient light sensor no longer works on my V500 after upgraded to 4.4.2. Auto brightness dims the screen but doesn't do anything to adjust it according to light conditions. Also, CPU-z cannot report the sensor any more. It was reported correctly under 4.2.2. Can anybody else replicate the same thing?
Sent from my LG-V500 using Tapatalk
bloommax said:
Ambient light sensor no longer works on my V500 after upgraded to 4.4.2. Auto brightness dims the screen but doesn't do anything to adjust it according to light conditions. Also, CPU-z cannot report the sensor any more. It was reported correctly under 4.2.2. Can anybody else replicate the same thing?
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Mine doesn't work either since updating
I do not normally use the auto sense mode for the screen but enabling this I tested it and I can confirm that mine works without a problem. 50020b US version. It does take the brightness about a second to adjust to sudden lighting changes though...
Additionally androsensor does show a light sensor for my device and it does respond to changes.
Sent from my LG-V500 using XDA Premium HD app
I happen to have two V500s, one with 4.4.2, the other with 4.2.2. I set the brightness to 100% with auto. In a dark room, both tablets are dimmed. The 4.2.2 one adjusts its brightness to a comfortable level. The 4.4.2 one is far too dimmed to view the content. I can confirm AndroSensor detects light sensor readings on both. I need to block the sensor first to allow CPU-z to detect it. The auto brightness was quite convenient to use for me previously. It also helps for battery savings when the screen is on. Now it's totally useless. I found the battery lasts significantly longer during sleep mode after the firmware update. However, it lasts shorter during usage due to brightness issue.
Sent from my LG-V500 using Tapatalk
Hi as the question says
Did anybody notice a small blinking circle (will be around 1mm size), around 1 cm to the right of the camera when you place a call on the note 10 +
or is it only me?
During calls I noticed it.
Sent from my SM-N975U1 using Tapatalk
It appears to be the prox sensor (for turning the phone screen off when its up to your ear). That's what I've been seeing in comments of other people seeing the flashing during calls.
I believe it is the proximity sensor
charlieb620 said:
During calls I noticed it.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Fullmetal691 said:
It appears to be the prox sensor (for turning the phone screen off when its up to your ear). That's what I've been seeing in comments of other people seeing the flashing during calls.
Click to expand...
Click to collapse
dchurch85 said:
I believe it is the proximity sensor
Click to expand...
Click to collapse
okay thanks... was worried it might be dead pixels
Hopefully a sensor and not a pixel issue. Happening to me
Yes, proximity sensor. S10+ 5G has it also.
Sent from my SM-N975U1 using Tapatalk
That would be the proximity sensor
It is the proximity sensor.
And by the way it doesn't work well at all on my S10 plus. When I am on the phone the screen would turn on and then my ear would start tapping on the screen turning things on and off.
Pretty annoying, so I had to learn to manually turn the screen off with the power button every time before I answer or make a call...
I sincerely hope they have somehow found a way to improve it with the Note
just now saw it whilst playing a whatsapp voice message. when i put my finger over it, the phones speaker will shut off which seems to confirms its proximity sensors.
i did notice after some seconds, maybe a minute, the blinking light stops on whatsapp if you are listening to a speaker call on whatsapp... i have the whatsapp on full screen mode so the green part of the phones GUI is up there...
I noticed this today also when I placed a call. I dont make calls much so I just noticed it after 2 days. Just had some free time now and quickly rushed to locate this thread I had seen yesterday I believe.
What a relief it's the proxi sensor.
tiho5 said:
It is the proximity sensor.
And by the way it doesn't work well at all on my S10 plus. When I am on the phone the screen would turn on and then my ear would start tapping on the screen turning things on and off.
Pretty annoying, so I had to learn to manually turn the screen off with the power button every time before I answer or make a call...
I sincerely hope they have somehow found a way to improve it with the Note
Click to expand...
Click to collapse
Working quite well for me so far.
It shows that Samsung has the ability to create camera under screen, but they didn't most likely due to photo quality
Good to know it's the proximity sensor.
Mine appears to flash rapidly more than blink though lol.
I thought I had a defective note. Thanks for the info.
Sent from my [device_name] using XDA-Developers Legacy app
It's the same thing just like S 10
those of us coming from the Note 9 that didn't have this, it's a new thing to discover...
When I first noticed it I thought dead pixel lol but it only visible during calls iv noticed
Yes, it is the proximity sensor, it is sad that this sensor implementation does not allow third party apps to use it, I used gravity screen in my past devices to turn screen off when in pocket or turn it on waving over the sensor, but now the app became useless, I use macrodroid, but it is not as good as gravity screen
does anyone else have a problem with the proximity sensor not turning the screen off during the call over telegram, threema etc.?
iopah said:
does anyone else have a problem with the proximity sensor not turning the screen off during the call over telegram, threema etc.?
Click to expand...
Click to collapse
Literally read the post before yours.
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!