Please refer to this post:
http://forum.xda-developers.com/showpost.php?p=62828995&postcount=1432
Has anyone gotten this problem? The person who posted this has been the only one having this problem. This can't be a rare thing, is it? Is everyone just dealing with this issue until it gets fixed?
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
AnotherContributor said:
One issue though I've been having is that when I'm making and receiving calls, sometimes the phone display goes black and will frankly not come back on. I press the App button and sometimes the display comes on, sends the call to the Status Bar, and the screen goes dark. So, I have to press the Application button again and draw down the menu to hang the call up. When I press the power button, the screen flashes on for maybe a quarter second then goes dark. It keeps doing that every time you press the power button. The worst case scenario that has happened a handful of times is that when I'm in a call, neither the power nor application button are responsive. When that happens, pretty much the only option is to power down the phone and reboot.
...
I'm not sure if I would be able to dial an extension with the way the phone is acting up. I feel like this was not an issue the first couple of weeks I had CM on the phone. Now, it seems to be happening with every call.
Click to expand...
Click to collapse
14th September 2015
samuraix21 said:
Hi, I have this issue. Were you able to fix this issue? You're the ONLY person that has posted this issue so I'm not sure if this is a rare hardware issue or everyone on this forum is somehow dealing with it until a fix comes up.
Click to expand...
Click to collapse
19th September 2015
hawk1500 said:
are people still experiencing the screen off during call problem? I am not talking about when you put it up to your face, but how the screen turns off and won't come back on?
Click to expand...
Click to collapse
20th September 2015
hawk1500 said:
Naw, no screen protector installed. tried the proximity sensor fix app as well as the xposed don't go to sleep during call module but it still does it.
Click to expand...
Click to collapse
20th September 2015
tonochito said:
i think that bugs should be listed more detailed:
front facing camera does not work well, if i want to take a selfie it crash. video camera also does not work equal it will crash. I had to install Google Camera and Open Camera in order to have both selfie and video options working, With Google Camera i take selfies and with Open Camera i record videos, As the guy talking about the scren off in calls is true, i don't have a screen protector and it has this behaivour, also as i mentioned there is kind of lag when i try to dial a number i have to do twice, it doesn't show up right away. The same goes when i am calling for example my carrier and i have to dial on the IVR i have to dial twice in order to get the dial keypad. I didn't have Google play crash.
Another thing that i notice was setting a wallpaper as screensaver does not fit in the middle or correctly i had to use Quick Pic and the option 768x1280 because with the stock gallery wallpapers are like aside of the middle
Click to expand...
Click to collapse
I think this issue needs some attention. I am having this problem as well (with and without screen protector). There are times that I need to enter extensions and codes during calls which has become impossible. I have two of these phones and they both behave this way. I recommend that people start posting screenshots of the app Proximity Sensor Finder which displays different distance numbers detected by the prox sensor. See my screenshot attachment which shows the proximity sensor always detecting a "covered" state of 0.0cm even when nothing is in front of the screen. Everyone should go try this and post their findings.
Other phones on CM11 were able to fix this problem in the past by adjusting the calibration which is unique for each phone, so I started searching around through the Fire Phone CM11 files and I found these:
/system/etc/permissions/android.hardware.sensor.proximity.xml
I could not discern anything of value from this .xml file.
/persist/sensor_calibration/SHCAL_DU20060142640727.csv
This file seemed promising. Its timestamp is back in 2014 so I assume that this comes straight from the original Fire Phone files. If this file is actively used to govern sensor behavior, I'm wondering if perhaps it is not being read correctly. It makes me wonder if there is a log out there somewhere that could shed more light on it. Anyways, you can open up that badboy in any spreadsheet to discover sensor IDs for a bunch of sensors along with calibration coefficients in the form of:
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=550.30
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=395.62
SENSOR_TYPE=PROX SENSOR_ID=SI1143 SENSOR_REF=4CCU1 COEFF0=19262.26
You'll have to open it and analyze it in context of the other columns and other sensors. I've attached it (re-saved in xlsx format because .csv files are not permitted - if you don't trust my xlsx just retrieve the file from your phone). I highlighted the rows of interest. We could just mess with coefficient values, but without any guidance, it could just be a waste of time. Plus we don't know if this even governs the sensors or if it's just helpful documentation. If anyone has insight about this or even far fetched theories, please comment!
I'm thinking about doing a 'grep' on the entire file tree for some of these key words like SENSOR_ID=SI1143, SI1143, 4CCU1, COEFF0, SENSOR_TYPE=PROX etc etc - to see if any files use any of these terms. It may prove unfruitful due to the amount of compiled software that is no longer in text form. Any thoughts about any of this?
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
tonochito said:
i have this screen always making a call with any cm11 i have used in the past, i have to press back and again the keypad and works normal, same when i have to dial a number
Click to expand...
Click to collapse
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
jdmillard said:
But if the prox sensor is always detecting a "covered" state, then it completely disables the screen during a call and we are unable to press "back". Could you post your findings from running Proximity Sensor Finder from CM11 Fire Phone?
Click to expand...
Click to collapse
i will give a shot, and post my result
In fact, it would be AWESOME if we could get someone (whose screen does behave perfectly during calls) to post their findings from Proximity Sensor Finder. If their screen works perfectly during calls and this app shows 0.0cm all the time for them too, then we can conclude that this app isn't functioning correctly and we know we need to find our root cause elsewhere.
tonochito said:
i will give a shot, and post my result
Click to expand...
Click to collapse
Available but why it doesn't work right?
tonochito said:
Available but why it doesn't work right?
Click to expand...
Click to collapse
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
jdmillard said:
Interesting. Is it stuck on 10.00061 even when you cover the front of your phone with your hand? Or does the number fluctuate?
Which ROM build are you on? (I should say, which publish date?)
Click to expand...
Click to collapse
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
tonochito said:
yes weird it is stuck no matter what i do, well if i put my finger in the "first camera" of the phoen it goes to zero
Click to expand...
Click to collapse
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
jdmillard said:
That suggests to me that the sensor is "all or none" meaning it doesn't bother detecting intermediate values, rather it just has a threshold that determines a covered or not covered state. That seems normal to me. I need to get mine to do that.
Does your screen behave normally during calls? Specifically, does the screen turn on when you pull the phone away from your face?
Click to expand...
Click to collapse
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
jdmillard said:
I just removed my glass screen protector and now mine behaves just as yours. Which is good that it functions as expected, but also a disappointment about the screen protector. I just looked to request a refund and it appears that they have an excellent return policy so I'm not too worried about it. Now I just need to find a screen protector that doesn't cover the prox sensor. ... sigh.
I'm still interested to see what happens with what you were describing: like how the screen would still behave finicky. I'll keep an eye out for that behavior and I'll let you know if I discover anything about it.
---------- Post added at 01:26 PM ---------- Previous post was at 12:38 PM ----------
I forgot to say thanks! You posting your results helped me figure out where I was going wrong. Gracias!
Click to expand...
Click to collapse
your welcome
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
KLit75 said:
I have a glass protector and i noticed over time that i developed a specific technique for answering the phone. I sort of slowly move it close to my ear and then the sound comes on (hear ringing, able to hear caller). If i press the answer button then put it to my ear, most of the time i cant hear the caller but they CAN hear me.
Never even considered it being a sensor issue. I thought it was CM bug triggered by my setup somehow. I flashed this rom and put the glass screen on within a couple of days after receiving it in the mail and since touch-wise the tempered glass works perfectly it was never even a thought. Dont mean to go on but is anyone else dealing with issues like the one i describe? Whats strange is i dont recall having that black screen issue others are experiencing.
Click to expand...
Click to collapse
I was lucky enough to have a good return policy on the glass screen protectors I recently got (for two Fire Phones). I'm returning them today and I've already ordered this as a replacement:
http://www.amazon.com/gp/product/B00WXY18WK?psc=1&redirect=true&ref_=od_aui_detailpages00
It has excellent reviews, decent price, very thin, and it is specifically mentioned many times in the reviews that there is a little cutout for the prox sensor (and you can see if if you look carefully at the pictures). I'm hoping that it will solve my black screen woes and protect my screen. There are reports from folks on these forums saying that there is still some strange behavior during calls (such as your example among others). I personally haven't encountered what you're describing, but I'll keep an eye out to see if I can be of any help.
jdmillard said:
Here is a compilation of the comments made about this issue thus far. There seems to be a consensus that screen protectors are not causing this issue.
11th August 2015
14th September 2015
19th September 2015
20th September 2015
20th September 2015
Click to expand...
Click to collapse
Hi. I like to get back about this since I've been quoted on this.
For me, the glass protector screen that I brought from XtremeGuard was the issue my dad had when he tried to make or take calls. After I removed it, it was back to normal.
The persistent issues now, based on what my dad is telling me, is that sometimes after you dial in a number and call a person, you don't hear the ringing tone to know if it went through or not. My dad would freak out when someone on the other line said something since the ringing tone is not working.
tonochito said:
Not always as some users says it sometimes goes black, or i have notice that the notification bar sometimes goes down by itself and the annoying problem of the keypad on calls
Click to expand...
Click to collapse
hi
this is usually related to hardware composer.
cheers
superdragonpt said:
hi
this is usually related to hardware composer.
cheers
Click to expand...
Click to collapse
but why? does it matter with the bootloader, i mean i know the CM11 on the Fire phone still on beta with no NFC working and the camera too at least i am using Snap camera and everything works. But making calls is a bit annoying even i don't use the phone to make a lot of calls just for WhatsApp almost all the time
Related
I was checking voicemail today.. put in my password thru the keypad.. and then once i put the phone back next to my ear.. i kept pushing the keypad buttons with my cheek. until the promixity sensor caught on..
anyone else getting this prob? just an fyi.. i have the SGP Oleophobic Screen Protector on my phone.. i'm not sure if that decreases the reaction time for the sensor or not.. but its a pain..
No mine does that too. I've been using google voice to keep my old number, which asks to hit a 1 or 2 to accept/decline thus keeping the keypad up.
When I'm on a call and shufflin' (everyday I'm shufflin') sometimes the screen pops back on with my face on it and all of a sudden you'll hear a bunch of tones over the phone. lol. Everyone asks, "What was that?!" and I just giggle and say, "Don't worry about it" or "I didn't hear anything" lol.
But yea. It's a tad slow. Probably just a setting. I'm sure it'll get fixed soon.
I thought I was the only one experiencing this issue! I had this proximity sensor issue on my Iphone 4, but it was hardware related. This only appears to occur when the dialpad is still on during a voicemail or phone call. This is BEYOND ANNOYING and I hope that Google is able to address this via software fix. I'm surprised they let this one slip through the cracks.
Proximity sensor slow
Yep. Mine too.
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
http://www.youtube.com/watch?v=cjTGQaK1Qvw
This thread is pretty dead, and I haven't found too many other posts regarding this issue. I'm shocked to not see any replies, including the ones who already wrote in this thread. I was hoping to get some confirmation if their "slow" responding phones are also exhibiting this correlation with the accelerometer.
Is this not a wide spread issue? Is what I demonstrated not expected behavior? Do I need to exchange my phone?
I hope not - I bought this from a Amazon merchant, so I don't know how hard it is to get warranty work done (since it's imported).
I'm in the US, and this is a GSM version. We only have the CDMA version (Verizon) officially.
Forgot to post here regarding this issue. Not fixed, but I think it's more of a software issue than hardware. I wrote and made a video that might explain why I think it's a software issue:
http://www.guytechie.com/articles/2012/1/22/galaxy-nexus-slow-proximity-sensor.html
naddie said:
This thread is pretty dead, and I haven't found too many other posts regarding this issue.
Click to expand...
Click to collapse
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
case0 said:
Probably because no-one else has this problem? I know I don't anyway, mine is always instant and works flawlessly. Sounds like a hardware issue or your screen protector?
Click to expand...
Click to collapse
It's an issue for me, no screen protector and the timing's almost sporadic when holding it naturally. But it could also be how I hold it as said earlier in the thread
I also have the same issue when checking voice mail. My damn cheek always hits a number or some button after putting in my pin.
Screen orientation in general seamed slow to me on 4.0.2. 4.0.4 speeds things up a bit, it's listed as one of the improvements.
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
ericshmerick said:
Same issue here. I just tilt the phone so that the top (where the sensor and speaker are) touches my ear for a second, then flatten the phone against my cheek. This gives the sensor time to activate and never results in accidental keypresses.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
this is what i do too it's a pain though - i hope we get 4.0.4 in the UK on o2 soon! im tired of waiting for faster screen rotation and more responsive proximity sensing
All my P sensor issues were fixed after flashing the PrimeLA03 bootloader.
Hi people. I have the same issue on 4.0.4 (Stock OTA).
The proximity sensor shows no output after testing it with "Sensor List" and with "Elixir 2".
Any ideas? Thx.
I have this issue too!
I have it too, I just tilt the phone to touch the ear first and then bring it close to my face.
edit with a rom
If your using a Rom like AOKP, you can edit it to be faster and better in your desired ways.
Done it and it works the second I raise my phone to my ear when necessary.
Emergency Call from lock screen
Never had a problem GV or the stock phone but the orientation affecting the proximity sensor might explain why I am making emergency calls from the pattern lock screen.. wish there was at least a simple swipe needed to make the emergency call.
naddie said:
I just found out why this is. The GNexus requires the phone to be upright before the proximity sensor will turn off the display. If it is laying flat, it won't work. Because of the complexity (the requirement to satisfy both conditions), it seems to react slower.
The hardware itself isn't the problem. It's the stock dialer.
To demonstrate, I made a video. I used the stock dialer and GrooVe IP (a dialer I use for Google Voice). GrooVe IP turns off the screen right away when I put my hand over the proximity sensor. Also, it does not cause accidental ear dialing.
I hope Google will fix this in the next update. It's certainly by design (a bad decision), and can be fixed by software.
Click to expand...
Click to collapse
Not fix even on 4.1 ...
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
I didn't notice this on the unit that I sent back!
Thanks.
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
fury683 said:
Do you have a screen protector covering the proximity sensor? It may not be working correctly if it's covered.
Is it only during calls or all the time? A few other people have posted about prox issues with the smaller Pixel 3, here's one thread:
https://forum.xda-developers.com/pixel-3/help/proximity-sensor-keeos-display-off-t3864055
Seems it can be fixed by cleaning the area around the sensor if you don't have a screen protector.
Click to expand...
Click to collapse
Thanks for the suggestions.
No screen protector fitted or anything obscuring the sensor.
Next time it happens, I'll check to see if it might need cleaning.
One theory I have, is that this phone has been upgraded with the November patch and maybe there's something in there that has caused this issue.
Has anyone else noticed this after the Nov update?
Thanks.
jscsltd said:
I'm on my second Pixel 3 XL after an RMA for distorted bottom speaker.
I'm now noticing that the proximity sensor is stopping working when you bring the phone to your ear in a phone call and thus, leaving the screen visible and active.
A restart does fix this but only for about a day!
Has anyone else noticed this issue?
Click to expand...
Click to collapse
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
I know there is a bug when using the pixel buds and unplugging them either before a call or during it would stop the proximity sensor from working.
a reboot was the only thing that would fix this issue for me
xweb10 said:
I just got the phone yesterday and am seeing the exact same behavior. It works and then it does not. Reboot temporarily fixes it.
Click to expand...
Click to collapse
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
How do I test my proximity sensor?
jscsltd said:
I've RMA'd the phone that had this issue and still have the issue.
It does seem quite random. I'm hoping Dec Update will fix this along with the distorted bottom speaker.
I think that this issue is software related, as I tried using an App that shows when the proximity sensor is triggered and this seemed to work as expected.
Click to expand...
Click to collapse
I am trying to get to the bottom of this. Do you happen to have a Samsung Gear watch? I have the S3 and removed the "phone calls" option from the Pixel Bluetooth menu and so far this issue has not occured, but I am still testing.
---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------
swieder711 said:
How do I test my proximity sensor?
Click to expand...
Click to collapse
There are apps on the play store.
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
jscsltd said:
That's interesting regarding the Gear S3 watch.
Yes, I do have one of these watches.
I'll try what you've suggested and report back with the results.
What made you think it could be an interaction with the Gear S3?
Thanks.
Click to expand...
Click to collapse
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
xweb10 said:
I have a pixel 2xl, as well. I looked at the Bluetooth setting on that phone when connected to my S3 and noticed the "phone calls" option was disabled.
I was looking at all apps that access the dialer or phone calls. Really just a guess.
Click to expand...
Click to collapse
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
jscsltd said:
I see....good spot.
If I do disable this setting in Bluetooth though, will this just disable the ability to take voice calls on the watch using the internal microphone and speaker or will it as well, stop the watch from vibrating when a call comes in?
Click to expand...
Click to collapse
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
xweb10 said:
I believe it only disables the ability to take voice calls on the watch. It continues to vibrate when a call comes through.
I forgot: Also boot to Safe Mode first. I do not have a reason, but that is the path I took.
Click to expand...
Click to collapse
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
jscsltd said:
That's a shame that you can't take voice calls on the watch as that's a feature I do use at times.
Either, way I disabled it after more issues with the screen not blanking and will see how it goes.
I also had a new issue, where I'm in a call and could not switch to Speaker. I would choose the Speaker option but it just would not switch.
I'm wondering if you've had this same issue when you had your Gear S3 watch setup to take calls?
Click to expand...
Click to collapse
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
baginz10 said:
I've had to RMA mine due to the bottom speaker crackling. I purchased from carphonewarehouse in the uk so have had to to a standard replacement. Does anyone know if they will send the replacement out before receiving the faulty one? They did this last year with the 2xl. It's not due to get back to them until next Thursday so hoping I won't have to wait too long.
Click to expand...
Click to collapse
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
xweb10 said:
I am able to switch to speaker but I never have my S3 set to take calls. I have not gone full on Michael Knight yet.
BTW My proximity problems are gone. Must be the Bluetooth S3 issue.
Click to expand...
Click to collapse
I've switched off the ability to take calls on the S3 and can now switch to phone speaker with ease.
I'm hoping I can re-enable the S3 capability when an update by either Google or Samsung fixes the issue.
jscsltd said:
I've had my pixel 3 XL replaced twice due to distorted bottom speaker by Carphone Warehouse Business.
They will deliver a replacement and then collect your faulty unit a few days later, in order to allow you to transfer your data to the new unit.
Click to expand...
Click to collapse
Sorry I wasn't clear I've done an RMA with google so just wanted to see if anyone else had done the same even though they didn't purchase direct from them. Last year with the 2XL they would send the new one out once the faulty device was sent at the post office, they must have known from the tracking. This time it's via UPS and is going straight to Poland! Not due to arrive until the 4th. If a replacement doesn't get sent out tomorrow or Monday looks like I'll be waiting a while. I even noticed screen burn in when resetting it. Changed to Samsung displays and still burn in from the nav bar just like last year. I wish I'd gone back to carphonewarehouse now to get a replacement!
Wow, I never would have thought of the Samsung gear watch interfering. I have the newest one (the one after the s3) and had the same issue with the screen staying awake while on a call. It was the one thing I really didn't like about the phone. Seems like the symptoms are the same Pixel 3xl, verizon, Samsung Galaxy watch and a restart fixes the issue for a while. I just tried what you suggested. Thank you very much for posting your idea.
I've been dealing with a similar issue, but not exactly,
My screen turns off when I hold the phone against my ear, but the display still seems "active".
My cheek is still bringing the notification area down, toggling my quick settings or even going into the settings app (if my phone was unlocked while I answered a call).
It's been super constant and annoying because one time my flashlight was toggled in an elevator, which was a bit awkward.
Another time my clock app opened and changed my alarm time and then turned it off entirely.
Luckily I could feel the vibration so I knew something was going on but this is a really strange issue.
I have already setup a RMA since the phone has a speaker distortion problem as well, so we'll see what happens once the new device arrives.
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?
So I have a very weird issue and I'll try to explain the best I can;
For some reason, ever since the S10+ I've had issues with Samsung phones, I think its something to do with the proximity sensor that's now under the glass, I'll explain as I'm getting similar and more issues on my S20 Ultra.
So last year when I had an S10+ and when I was on a call, which I mainly use my left ear (I think my right ear is a few db less so I use my left) I would quite frequently seem to activate the menu (top right) and therefore end up pressing things with my ear, unbeknown to me, sometimes I'd add a 2nd person to the call or simply put the other person on hold! This happened a lot and I was close to sending it off for repair even though I used apps to test to ensure the proximity sensor was working correctly but in the end, I sold it and got an OnePlus 7 Pro, which I didn't have an issue with. During my time with the S10+ I noticed that even though I held the earpiece to my ear I could see the screen light up and that's where I think I'd end up pressing the screen accidentally as I've just explained.
Roll on to now where I'm facing similar issues but also I'm finding if I need both of my hands and therefore use my left shoulder to keep my phone against my ear the call disconnects as if I'm hanging up. Now it seems a straightforward resolution which is not to do that but I've never had this issue before and I've tested it out quite a bit when I do this the screen isn't on and my face is nowhere near the end button!! It's really driving me crazy at the moment and annoying my other half who's normally on the phone to me when this happens!!
Anyone got any suggestions or thoughts, does it happen to anyone else or am I just being stupid??
I haven't gone down the route of resetting the phone yet but I'm going to consider it.
T.I.A
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Xode said:
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Click to expand...
Click to collapse
I did that the other day, however, when I moved the screen away I saw it light back up....
maverick1103 said:
I did that the other day, however, when I moved the screen away I saw it light back up....
Click to expand...
Click to collapse
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
View attachment 5012913
S20U-Exynos
Xode said:
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
S20U-Exynos
Click to expand...
Click to collapse
Thanks, I've already got that enabled, will just have a play around.
maverick1103 said:
Thanks, I've already got that enabled, will just have a play around.
Click to expand...
Click to collapse
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
vrgolin said:
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not yet, still having issues.