no pocket mode - proximity sensor gets ignored - Google Pixel 2 XL Questions & Answers

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...

Related

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 !

OnePlus 3 loses much energy when it's inside my pocket

Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Well me getting same problem.. still not figured out issue.
Sent from my ONEPLUS A3003 using Tapatalk
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Hastaloego said:
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Click to expand...
Click to collapse
Hahaa ;p
well, smart lock is not active in my phone...
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
thebcooper said:
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
Click to expand...
Click to collapse
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
MagDag said:
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
Click to expand...
Click to collapse
Just be more wary of the screen being knocked/bumped!
Yeah that handles hardware as far as I know (might also be under other processes if they use it too though)
Alright, thanks for your quick feedback.
I guess i will reset my phone now...
I'm pretty sure it's the fingerprint sensor. Really sad to see that OP3 has this issue too, this started happening to me on OP2 too after the marshmallow update. They made the fingerprint scanner much more sensitive, greatly improving it's speed but this started happening. The workaround is to keep the phone in your pocket screen facing outwards...
I have the same problem. It should be fixable via system update to not activate the fingerprint sensor while the proximity sensor detects something.
Or am i missing something here?
Same issue here
Same issue. It's kind sad that OP can't handle this to prevent waking up using proximity sensor like it happens with duoble tap. I hope that they will release an update soon.
Is there anything in settings called "pocket mode"?? a friend has a THL phone that has pocket mode which stops the phone from doing anything when it detects its in a pocket
Nope, I've searched whole settings and there no option like 'pocket mode'.
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
I've created an e-mail to support with issue describe. Will update thread while getting reply.
Yes this is a bad bug which OP need to fix asap.
So what's the solution to the problem, finally?
MagDag said:
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
ArjunRanaOO7 said:
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
Click to expand...
Click to collapse
You would think that priority would be given to the proximity sensor. If triggered it would disable the finger print input.

Huge heat when in pocket

Today I kept my OP3 (Stock Rom Rooted) for 10/15 minutes the phone in my pocket and it become extremely warm (seems to be nabk with my OP2) !!
I made the following thoughts:
- the ambient display wakes up the phone and make it warm
- the FPS feels "something" and it wakes up the phone
- the proximity sensor doesn't work properly
Does some of you ahve the same issue ? Any feedback is welcome !
Now I disabled the ambient display, and let's see what happens.
I am facing same Heat issue when in pocket and riding the vehicle. Have disabled Gesture control in phone setting, Let us see the result.
yes..me too facing the same heat issue
Same here
raghumantap said:
I am facing same Heat issue when in pocket and riding the vehicle. Have disabled Gesture control in phone setting, Let us see the result.
Click to expand...
Click to collapse
I don't use the gestures, except the double tap to wake which honestly is use less with fps...
Sent from my OnePlus3 using XDA Labs
same here, i already started another thread for this issue:
http://forum.xda-developers.com/showthread.php?t=3403583
MagDag said:
same here, i already started another thread for this issue:
http://forum.xda-developers.com/showthread.php?t=3403583
Click to expand...
Click to collapse
I didn't used your thread just because you talk about energy and not heat (even if usually mr Joule said these are linked)... BTW I read it's because of fps: could be... I want to try the setup without gestures and ambient and than I will confirm it!
Sent from my OnePlus3 using XDA Labs
Hey!
it also generate heat here...
It's definitely the fingerprint sensor. Face the screen outwards inside your pocket and the problem doesn't occur anymore (thanks @Rauttis)
This happens to me also but I have no gestures enabled on the lock screen so it can't be that. Thus as MagDag says, it is probably the fingerprint scanner. I'll try to face it outwards to prove it.
MagDag said:
Hey!
it also generate heat here...
It's definitely the fingerprint sensor. Face the screen outwards inside your pocket and the problem doesn't occur anymore (thanks @Rauttis)
Click to expand...
Click to collapse
I will try this out and report back.
Sent from my OnePlus3 using XDA Labs
I have no problems so far. Using it for a week now.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Due to Gestures Fingerprint sensor, confirmed for me (haven't tried with Gestures ON and fingerprint sensor OFF) . Ambient display is on.
Sent from my OnePlus3 using XDA Labs
I used the following setup: no gestures, Yes ambient, fps on the outside side of the pocket... Seems extremely better (with 38 degrees here during the day)
Sent from my OnePlus3 using XDA Labs
Same problem for me too..
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
Soumitra.5693 said:
Due to Gestures, confirmed for me. Ambient display is on.
Click to expand...
Click to collapse
It's not due to gestures. As I said above, I have gestures turned off (and ambient display off too) but this problem still occurs for me, frequently.
bulletmark said:
It's not due to gestures. As I said above, I have gestures turned off (and ambient display off too) but this problem still occurs for me, frequently.
Click to expand...
Click to collapse
Hi, yes, I think it is due to the fingerprint sensor. I must have placed the phone facing away from my skin after disabling gestures (which was pretty stupid).
Sent from my OnePlus3 using XDA Labs
I have the same problem especially when at work although my pants are slim so the phone is against my body but going to try turning gestures off and seeing if the issue remains
I also have the same problem, thinking of returning the phone(ask for a replacement)
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
same problem here... if I turn off fingerprint then it will be fine. the sensor is too sensitive

Disable proximity sensor

Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Experiencing this as well. From what I have read, it is an issue with 8.1 specifically and the 5X.
Google haven't really acknowledged the problem yet, which sucks.
Related reddit thread
For calls, pressing the power button twice seems to bring the screen back for use again - doing this too quickly starts the camera, if you have that enabled.
This probably won't help for other use cases, like whatsapp.
I can understand that it's a bug for WhatsApp (she has that bug too), but for the dialer too ?
I don't experience such issues. My prox sensor is working like it should. Though I have a friend who has some minor problems with it, but he has a glass screen protector on top of it. Mine has a cutout for the sensors
Sebacestmoi said:
Hi,
My girlfriend's Nexus proximity senor seems to be broken and her screen is black all the time when she's calling someone.
Is there an easy way (root or not, I don't care) to easily disable the sensor all the time or in Caller app ?
She's on latest stock Oreo 8.1.
Thank you
Click to expand...
Click to collapse
My old original Nexus 5 had this problem and I got around it with an Xposed Module called Disable Proximity Sensor. That module has since evolved to something called Sensor Disabler (Link: https://forum.xda-developers.com/xposed/modules/mod-disable-proximity-t2798887). It doesn't say that it has been tested on the Nexus 5x, but it might still work. I am not sure how compatible it is with the new Oreo version of Xposed. Installing Xposed might be a bit overkill, but if it fixes the problem, it might be worth it.
I know how frustrating and annoying a busted proximity sensor can be, so I hope you can find a 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?

Categories

Resources