Develop Bugs

Proximity sensor seems to not work anymore

I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?

Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.

My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .

I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.

I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.

amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).

iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app

Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !

Marshmallow Sensor Problem

Hi. I'm on the latest build, 223 with root. Any time I get a phone call, when something is on the call sensor, the screen goes black and never turns on till the call is over. Sometimes I have to restart it. Also when listening to sounds in WhatsApp, the same sensor problem happens. I bought my device in Europe. Is there anything I can do to fix it?

No, I have this problem too.
You can only disable the sensor in the settings of asus call app

Deleted

holymoz said:
No, I have this problem too.
You can only disable the sensor in the settings of asus call app
Click to expand...
Click to collapse
It works on calls but doesn't affect WhatsApp.

BerkeKan said:
It works on calls but doesn't affect WhatsApp.
Click to expand...
Click to collapse
whatsapp doesn't have the option to disable the sensor.
there is an xposed module that disable completely the sensor but it needs bootloader unlock, root and xposed.

holymoz said:
whatsapp doesn't have the option to disable the sensor.
there is an xposed module that disable completely the sensor but it needs bootloader unlock, root and xposed.
Click to expand...
Click to collapse
If it is the module you're talking about, I am using it. I removed it but WhatsApp still use it.

Ss

BerkeKan said:
Ss
Click to expand...
Click to collapse
yes is it, strange that not work, I used it in the past and it worked, used the app sensor box to test the sensor and was disabled.

Yes, I faced this problem in Marshmallow. I was hoping they fixed it in 223 but based on your post it looks like its not yet fixed.
Recently my touch broke and I replaced by LCD+Touch and now proximity is not working on Lollipop also. It is always stuck at 'near'. Cleaning did not help.
I deleted 'android.hardware.sensor.proximity.xml' but it did not help. I badly need a way to disable proximity sensor completely for all apps (WhatsApp, Jio4GVoice, Phone etc.).

holymoz said:
yes is it, strange that not work, I used it in the past and it worked, used the app sensor box to test the sensor and was disabled.
Click to expand...
Click to collapse
Actually, I figured out it was my bad not get it to work. I have disabled the sensor again, tap the disc icon and the sensor was disabled completely for all apps.

wizwin said:
Yes, I faced this problem in Marshmallow. I was hoping they fixed it in 223 but based on your post it looks like its not yet fixed.
Recently my touch broke and I replaced by LCD+Touch and now proximity is not working on Lollipop also. It is always stuck at 'near'. Cleaning did not help.
I deleted 'android.hardware.sensor.proximity.xml' but it did not help. I badly need a way to disable proximity sensor completely for all apps (WhatsApp, Jio4GVoice, Phone etc.).
Click to expand...
Click to collapse
Root and Install Sensor Disable via Xposed. Set proximity sensor to far always. i.e. Mock sensor values (5 cms)
This is the workaround I use and it is better than having a black screen when I make or receive a call.
Works for all apps.

How to disable proximity sensor in rooted phone?

So it appears that my proximity sensor is faulty because of which it always thinks there is something close to it. Due to this issue, whenever I make a phone call the screen is always off as the proximity sensor thinks my ear is close to the phone, even when I remove the phone from my face.
This is quite annoying obviously and I was wondering if I can somehow disable the sensor. I rooted the phone with the hope of doing so. I am guessing I can delete/rename an appropriate file in the "sys" folder or add something to the build.prop to disable the proximity sensor. Can someone tell me what needs to be changed?

Use an app for disabling/mocking sensor reading, e.g. this one. I'm using it on Nexus 5, which after some time stops reading data from proximity and light sensors. Unfortunately, for this one you have to install Xposed too.
Maybe somebody will come up with an app, which will work without Xposed.

przemcio510 said:
Use an app for disabling/mocking sensor reading, e.g. this one. I'm using it on Nexus 5, which after some time stops reading data from proximity and light sensors. Unfortunately, for this one you have to install Xposed too.
Maybe somebody will come up with an app, which will work without Xposed.
Click to expand...
Click to collapse
I know I could do it with Xposed but Xposed does not work for Nougat. I need a solution for Android 7.1.1.

no pocket mode - proximity sensor gets ignored

After being new to the pixel 2 xl I'm rather confused as to why there's no pocket mode or judge - I'm able to unlock my device while being in my pocket (fingerprint & dt2w), usually there's a option like "avoid accidental touches" or a inbuilt "pocket judge" that blocks all inputs when the proximity sensor detects anything close but this is not the case on the Pixel 2 XL (something that worked flawlessly on all my OnePlus devices) - after reading the plenty reports of people with proximity sensor issues I did check my sensor and it detects proximity just as it should, it just seems not to block inputs... Or is it intended from Google that the proximity sensor gets ignored? Due to the many reports of people that claim their proximity sensors always detect anything near, hence the screen stays black when call is finished...
I feel like it's really inconvenient to have a device in my pocket that doesn't lock itself when being in a pocket, under a pillow or something like that and rather completely ignores proximity even though it's readings are correct - any thoughts on this? Did I miss something?

Must be something wrong with Your device, because when I cover my proximity sensor display goes dark and it doesn't accept touch to wake.
Sent from my Pixel 2 XL using Tapatalk

Sibmet said:
Must be something wrong with Your device, because when I cover my proximity sensor display goes dark and it doesn't accept touch to wake.
Click to expand...
Click to collapse
Thanks for the fast reply this gives me hope to be actually easy to fix, I'll check another kernel next, however I'd be surprised if it's related to @flar2's ElementalX...
Sent from my Pixel 2 XL using XDA Labs

Sam Nakamura said:
Thanks for the fast reply this gives me hope to be actually easy to fix, I'll check another kernel next, however I'd be surprised if it's related to @flar2's ElementalX...
Click to expand...
Click to collapse
I'm using Elemental X right now and don't have this issue.

AcidNoteZ said:
I'm using Elemental X right now and don't have this issue.
Click to expand...
Click to collapse
same

ive had the same issue only on stock rom. When on stock I used Gravity Screen. Currently on Havoc and that has an option to block screen when proximity is covered.

The weird thing is AndroSensor reports proximity as working just fine, also on calls it's working - when I hold the screen to my ear it blacks out and gets back on when I remove it, I get the impression that Google has not implemented at "pocket mode", I also compared it to N5X running stock 8.1, same behavior, even though it's just the fingerprint due to the lack of dt2w, which unlocks the device even in the pocket...
On the previous devices I owned (OnePlus 2, 3t, 5t) dt2w & fingerprint was blocked as soon as proximity sensor detects anything close, I was expecting this exact behavior to be Standard, it seems however not to be the case unfortunately!
Sent from my Pixel 2 XL using XDA Labs

A workaround/suggestion...
I had a really bad issue like this back on my Samsung Galaxy S5 (there was a well known bug), and what I ended up using that worked really well was an app called Gravity Screen by Plexnor (https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=en); granted it's been a LOOOONG while since I've used and even seen the app, so I can't say if it actually works on the Pixel 2 XL and/or Android 9 Pie, but if it does work as intended, it may just give you a (at least temporary) solution...

Proximity sensor/pocket dial protection

I have been using my 3a xl for a couple weeks and very happy overall with the speed and performance. I am having one issue trying to overcome that's very disappointing. I do a lot of of walking with my phone in my pocket. When ever I get a call or notification while my phone is in any of my pockets it will either answer it or because it's moving around it will go thru the menus etc. Even if I don't pull my phone out it will always do this. The pocket dial/proximity programming is not good. If you test the prox sensor by covering it up you can open, unlock, make calls etc. with it covered. I am coming from a LeMax 2 and never ever had a single problem with that phone. It had a setting in there and wouldn't allow you to accidently open, unlock, do anything if the sensor was covered. Does anyone have any workarounds for this or insight. I should be able to carry it in my pocket without it doing this. Thanks for any input.

You must have a detective prox sensor or something else is not working correctly with your phone. When I cover my prox sensor (with my hand or in my pocket) the screen does not come on for notifications, calls, or when I tap to wake.

When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?

retrov said:
When I cover prox sensor and unlock phone with fingerprint the screen comes on too. Does yours do that as well?
Click to expand...
Click to collapse
Yes

I just tested my phone today and my screen does wake for incoming calls even when the prox sensor is covered.
This is very annoying.
It does not wake for notifications.

Very annoying for me as well. I guess it's the software program. With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.

My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.

creeve4 said:
My wife's Moto X4 behaves the same way.
If you want, you can install Xposed and GravityBox, it has an option to use the proximity sensor when deciding to wake the decide (see attached screenshot). It will keep the screen off for incoming calls when the sensor is covered.
Click to expand...
Click to collapse
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....

duh1 said:
I thought Xposed wasn't available for Pie except through some unofficial closed source buggy Magisk extensions. Are you running that? I'm not sure I trust closed source on a rooted phone....
Click to expand...
Click to collapse
It's all open source now. I have not experienced any bugs, it's working really well for me.
Search the magisk repo for Riru - Exposed. I use the sandhook variant. You can find links to more information in the module description.
GravityBox Pie has a thread on XDA.

retrov said:
With that sensor covered like in your pocket it shouldn't allow that to happen. Thanks for letting me know at least I know my phone isn't defective.
Click to expand...
Click to collapse
Sounds like an annoying bug to me as well.
Google / Pixel has a bug reporting system...
https://support.google.com/pixelphone/answer/6398243/
If we all submit reports, hopefully they'll take notice and the issue will be fixed in an update...

Just submitted a report on the issue. Thanks

Try the gravity screen app & see if it fixes your issues. I use it & the phone doesn't wake in my pocket for text notifications - but I'm not sure how it will respond to phone calls/notifications; it has options for proximity sensor & a "pocket sensor" feature as well.

retrov said:
Just submitted a report on the issue. Thanks
Click to expand...
Click to collapse
If we want this bug fixed in future updates, everyone should send in a report, especially with Google, squeeky wheel gets their attention...

Anyone that has a pixel 3a 3axl please submit a report on this issue.

My Pixel 3a ja behaving the same way. Coming from a OnePlus 5 with a splendid pocket mode this phone is really getting on my nerves. I love everything about this phone but the constant pocket answering is really bad. Thinking about stop using it...
I've tried every app in Play named pocket mode but nothing seems to work properly.

I've submitted feedback report a couple times hopefully everyone on here can do the same. Won't get fixed until they update on there end. That's the only bad thing I don't like about this phone so far.

Sent.
FYI - for others looking to do this, you file the report under your phone's Settings/About Phone/"Send feedback about this device"

My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.

acejavelin said:
My biggest issue isn't answering in my pocket, but when it's ringing and I pull it out of my pocket, it will see a swipe down action this rejecting the call... Happens to me at least once a day. I really hope this is fixed in Android 10 next week.
Click to expand...
Click to collapse
Android 10 didn't fix this. I really hate Google right now.

I keep my current N6 phone in a wallet like case with a front cover. Do you guys think that might help?