Database Users

Screen locks immediately during calls - proximity sensor not working?

I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!

Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...

jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.

Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app

jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.

To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app

Dial *#7353# and make a test
sent from my Galaxy

samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!

Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?

Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.

I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.

My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse

Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.

I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse

hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )

I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse

Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:

HOw to solve, none of this works. How cann i clean proximity?

Knock knock not as responsive waking up...

Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4

Brava27 said:
Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.

hd-renegade said:
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.
Click to expand...
Click to collapse
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4

Brava27 said:
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....

I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.

csmith8507 said:
I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.
Click to expand...
Click to collapse
This is my exact problem. The phone just decides it doesn't want to wake up with knock-on...but after I press the power button, it only turns on for half a second and it's out again. I never tried swiping over the sensor, but hopefully it works because it's mighty annoying when it does it during a call!
I wonder if there's a fix for this?

canecbr600 said:
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....
Click to expand...
Click to collapse
this, if you are trying to do it like you did on the nokia n9 or nokia 8800 then it won't work
slow deliberate knocks are the only way
waiting on the g2 to arrive, but on my review unit, knock knock wouldn't respond correctly if i left the phone on the table, but if i picked it up, it would work nothing scientific here just an experience of one person and one prototype

I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!

in_dmand said:
I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!
Click to expand...
Click to collapse
I did notice it does seem to behave better when set to simple for the screen off animation.
My screen protector does have a cutout around the sensors. Keeping the sensor area clean enough to qualify as having OCD does seem to make it work properly the first time, every time. Maybe it's overly sensitive?
Edit: Scratch that. 30 seconds later it's behaving erratically again. Maybe it's not the fact that it's clean, but the swiping over the sensor that temporarily resolves it.

it also seems to work much better when knocking at the top of the screen where the statusbar would be.

So I ended up swapping the phone out over the weekend for a new one and now everything seems to work just fine. Seems to indicate that it's not a software problem, but rather a hardware issue with the proximity sensor.

Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.

Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
This is true however there are indications of problems with the proximity sensor as well. Some of the devices are behaving as if tree sensor is covered even when it's not.

Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
Thanks for this.. Very insightful.. I tried it immediately LOL

I had the same issue. I have no case or screen protector on, and was not covering the sensor when trying to wake the phone. For some reason though, knocking wouldn't wake the phone, and pressing the power button would only turn the screen on for a few seconds. I want even given enough time to get past the unlock screen. I went into the store and they are sending me a replacement that should come in later this week. It doesn't happen all the time. It is much more noticeable after receiving a call though.
Sent from my VS980 4G using Tapatalk

Definitely is dependent on the proximity sensor. If i just have my thumb on the edge of the phone by the sensor it will display this problem. Even with my finger a half to one inch above it will do this. I will be paying close attention to the proximity sensor from now on when it doesn't work. Still have a few days to return and thought i had an issue but maybe not.
Sent from my VS980 4G using xda app-developers app

sometimes its also greasy fingers, at least in my case, rarely though

As long as you tap twice the same place it's working fine. If distance between first and second tap is greater than 1 - 1.5 cm it won't work.

Got the same problem on my d802...when i left the phone on my table for 2-3min it wont wake up on first knock knock even power key wake it up for 1sec after auto turn off again....even with no screen protector....i noticed that sometimes there is a delay about 5-10sec after knock knock and screen turns on....other thing i noticed when i knock on immediently after turning off it works 100%....BUT i also noticed when i knock on after a while it turns on and i can unlock got vibration and sound of the unlock but i cant see anything. Screen looks like its off but when i look closely i can hardly see widgets and when i set effect to tv out i can see the effect by pressing the power button...when i press the power button again screen turns on like normal...i noticed sometimes on a rerboot the lg bootlogo disapears the led is working an showing all colors but the boot animation is gone like the screen is off at the bootup...dont know why after the bootup the pin lock screen is showing up normal....sorry for my english^^

Help: Camera turns on in my pocket.

I'm using the default screen lock, with swiping, and it happened 2 times in the last 3 days, that my camera was turned on, in my pocket. (The phone is in a leather pouch)
is there a way, to disable the camera on the lockscreen (swipe left)?

It´s not the lock screen. It´s because of volume buttons. If you hold it pressed for some time volume up starts quick memo and volume down starts the camera. I have the same problem: phone carried in a pouch. I wonder if there is a way to disable it since I don´t really use quick keys.

I've never had this issue in the past week and half that I've had this phone without any case on.
The back volume rocker buttons are definitely getting pressed if your camera is turning on. When you put the phone in your pocket, do you put the camera facing towards you or away?

Mine is doing the same, actually. Yesterday I logged into my Google Plus page and saw there were new photos uploaded, ready for review. There were 8 or so pictures taken inside my pocket.

I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?

Klotar said:
I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
You're right! I completely forgot about that.
I think the proximity sensor (located between front camera and the earpiece) should prevent the camera from turning on and I just did a quick test.
Phone in hand, pressing volume down rocker results in the camera turning on. This is normal.
To simulate phone in pocket, I took a shirt and used 1 layer to cover the proximity sensor and then pressed the volume down rocker. The phone did not turn on.
Quick easy test, took 10 seconds, give it a try to see if your camera still turns on. If not, something else other than the volume down rocker is turning on your phone.

This might be a stretch, but I've noticed the phone turns on by itself sometimes when putting it down on the desk. I'm thinking it's picking up a double-knock signal some how in the pocket and further movements cause the lock screen to slide to the right (which is the camera).

I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app

bearsblack said:
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Click to expand...
Click to collapse
I don't think so. I'm on T-Mobile, and while I rooted my phone last night, I had the issue prior to rooting.

bearsblack said:
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app
Click to expand...
Click to collapse
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.

yyz123 said:
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.
Click to expand...
Click to collapse
Obviously lol... But nope.. Still loading the the camera with sensors covered. I'm not too worried about it tho. I haven't unlocked this phone in my pocket yet. Even with knock on active.
Sent from my LG-LS980

I have the T-mo one and I keep getting the camera and quick notes opening. It's super annoying. I have recently turned my phone arround, now the screen faces outward. It seems to be helping, I have not had it happen since.

Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app

Must be some thin ass pants. Never once had happened to me. Proximity cover still lets cam launch.

xdafoundingmember said:
Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol... I wish it was that easy.
I wear black 5.11 tactical pants everyday at work that have plenty of room and I have this issue.

did anybody find a way to turn the Vol Up/Down functions on lockscreen off?

I reckon an Xposed mod could help you with that.

I have been having the same problem and yesterday deleted 17 photos taken from inside my pocket in the last 2 days while I was at work. I have no case on the phone at the moment and I am not rooted.
Sent from my VS980 4G using xda app-developers app

I had the exact same problem when I first got this phone. Had no idea the camera was on until I felt my phone extremely hot in my pants. A case solved that problem for me.

robogo1982 said:
I reckon an Xposed mod could help you with that.
Click to expand...
Click to collapse
strangely enough, it lets you control the Vol keys only for the screen off (which would help everybody in this thread, yes) but i'm also looking to disable it for the lockscreen.

Disable proximity sensor with Android L

This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.

I have this exact same issue, and was also hoping to find a fix. Any ideas?

One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app

n2d551 said:
One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. I have done this, for the time being, as it's difficult to end calls, otherwise. However, not being able to use the keypad whilst in call is posing to be an issue. Prior to the update and using 'Proximity Screen Off' app, I was able to catch the 'Home' button when pressing the power button, which allowed me to use the phone screen whilst in a call. With the new update, I am unable to do this.
I have come across a Disassembly Video (watch?v=AZDAIgwbXk4), but I'm not sure how confident I feel taking my phone apart.
The screen on my Nexus 4 has previously been replaced. When it was replaced, I'm fairly sure the Proximity Sensor did work, but then I dropped it on wooden flooring, and after that it no longer worked. It was a seemingly short drop, but this has somehow damaged the sensor. I'm not sure if the rubber cover (as shown in the video) has just moved out of place, or if it is completely broken. The light sensor works fine, in any case.

BobSmith9 said:
I have this exact same issue, and was also hoping to find a fix. Any ideas?
Click to expand...
Click to collapse
Admiral Nelson said:
This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2657176

mene82 said:
http://forum.xda-developers.com/showthread.php?t=2657176
Click to expand...
Click to collapse
I thought I had fixed it, but unfortunately the fix was short-lived. I discovered that I'm missing the gasket covering the proximity and light sensor, and this is causing an issue.
Anyone have any workable alternatives?

Screen display problems during a call

Do your Nexus 6P screen go black during a call. Mine does on every call. My display settings is set for 1-minute. I call Huawei support. The lady says that the screen is suppose to go and stay off during a call. Never heard of that from a phone. You cannot respond or do anything during the call.

lskeys said:
Do your Nexus 6P screen go black during a call. Mine does on every call. My display settings is set for 1-minute. I call Huawei support. The lady says that the screen is suppose to go and stay off during a call. Never heard of that from a phone. You cannot respond or do anything during the call.
Click to expand...
Click to collapse
Lol - most, if not all do that!
But, it's supposed to come back on when moved away from your ear.
Standard behavior.
You have something blocking proximity sensor?

do you have a screen protector? if so, you need one that has the cut out for the proximity sensor.
happened to me. i thought it was a setting or my phone was defective. Found out it was a early production screen protector that didn't have the cut out for the proximity

lskeys said:
Do your Nexus 6P screen go black during a call. Mine does on every call. My display settings is set for 1-minute. I call Huawei support. The lady says that the screen is suppose to go and stay off during a call. Never heard of that from a phone. You cannot respond or do anything during the call.
Click to expand...
Click to collapse
I have this problem as well.
You must have a screen protector or tempered glass protector that covers the proximity sensor. The proximity sensor is under the top speaker on the right side bottom right corner. If you don't have a cut out there for the sensor, then that is why your screen is stuck black. If you have no screen protector, you have a real problem. I thought at first it was caused by google voice but after some google searches I seen that the culprit is my screen protector. I am leaving it on till my new one comes in a few days, but you can go to settings->accessibility-> and turn on hang up phone with power button.

TNS201 said:
I have this problem as well.
You must have a screen protector or tempered glass protector that covers the proximity sensor. The proximity sensor is under the top speaker on the right side bottom right corner. If you don't have a cut out there for the sensor, then that is why your screen is stuck black. If you have no screen protector, you have a real problem. I thought at first it was caused by google voice but after some google searches I seen that the culprit is my screen protector. I am leaving it on till my new one comes in a few days, but you can go to settings->accessibility-> and turn on hang up phone with power button.
Click to expand...
Click to collapse
The thing is that the phone turns black when I make a call or take a call. As soon as I am in a call. I cannot see the screen in a call or press a number or anything. Its all black. I do have a skinomi screensaver on. Cannot see a sensor anywhere. Are you getting a new phone or screen saver. BTW, I did a factory refresh of the phone. Still nothing. Do you think taking the screen saver off will help?

lskeys said:
The thing is that the phone turns black when I make a call or take a call. As soon as I am in a call. I cannot see the screen in a call or press a number or anything. Its all black. I do have a skinomi screensaver on. Cannot see a sensor anywhere. Are you getting a new phone or screen saver. BTW, I did a factory refresh of the phone. Still nothing. Do you think taking the screen saver off will help?
Click to expand...
Click to collapse
Yes if you have a screensaver on that's blocking the sensor it won't function correctly. A bunch of people are having these problems with screensavers glass and film ones.

notfaded1 said:
Yes if you have a screensaver on that's blocking the sensor it won't function correctly. A bunch of people are having these problems with screensavers glass and film ones.
Click to expand...
Click to collapse
I cut the top part of the screen saver off. Thanks, btw what kind of screen saver did you order?

lskeys said:
I cut the top part of the screen saver off. Thanks, btw what kind of screen saver did you order?
Click to expand...
Click to collapse
This is what I ordered
http://www.ebay.com/itm/201451006487
You can see where the sensor is below the top speaker bottom right corner

itstee said:
do you have a screen protector? if so, you need one that has the cut out for the proximity sensor.
happened to me. i thought it was a setting or my phone was defective. Found out it was a early production screen protector that didn't have the cut out for the proximity
Click to expand...
Click to collapse
But it's suspicious that the N5/N6 people are having this issue at or near the time Marshmallow was introduced.
https://productforums.google.com/forum/#!topic/nexus/oqh-V37hgDM
& one N6P member has sort of verified this:
http://forum.xda-developers.com/showpost.php?p=63693059&postcount=9

perveeus said:
But it's suspicious that the N5/N6 people are having this issue at or near the time Marshmallow was introduced.
https://productforums.google.com/forum/#!topic/nexus/oqh-V37hgDM
& one N6P member has sort of verified this:
http://forum.xda-developers.com/showpost.php?p=63693059&postcount=9
Click to expand...
Click to collapse
well i suggest removing the screen protector if you have one that covers the proximity sensor. worked for me and haven't experienced it yet

itstee said:
well i suggest removing the screen protector if you have one that covers the proximity sensor. worked for me and haven't experienced it yet
Click to expand...
Click to collapse
Yep_removed it last night.
Symptom was still there this AM.
Went away for one phone call.
Now back after sitting with no calls for a couple hours.

perveeus said:
Yep_removed it last night.
Symptom was still there this AM.
Went away for one phone call.
Now back after sitting with no calls for a couple hours.
Click to expand...
Click to collapse
that sucks..

itstee said:
that sucks..
Click to expand...
Click to collapse
Ha, right?!
But at least it is not me only and apparently symptomatic with numerous reports in that Google product support forum I posted above.

I had the issue removed the screen protector works fine now.
Sent from my Nexus 6P using Tapatalk