Database Users

[Q] Proximity sensor funkiness?

This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?

I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App

I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.

I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.

ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?

Yeah, ditto that - how do recalibrate the sensor?

Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.

I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#

Ok, mine says No Detection. Is there anyway to set the value?

One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.

If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.

ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?

samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....

Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps

What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?

BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?

another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?

rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned

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

[Q] Screen goes black when I make a call

My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help

Remove your screen protector.

Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.

Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else

kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again

Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input

Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...

Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered

Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.

Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again

I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.

Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help

Weird Proximity Sensor Problem

Hello XDA,
I have a weird problem going on with my Note 3. I had an issue where my screen would not shut off during calls so I immediately figured I'd test the proximity sensor with some debugging app and also the built-in service menu. I went ahead and did that and noticed it was sort of working but one of the values (the main one that ranges from 0.0 to 8.0) stayed at 0.0 and didn't change. I did some research and used an app that I believe recalibrated it and it began to work perfectly… EXCEPT, when the screen goes off during a call and SHOULD be locked from touch events I can still touch the screen and it is responsive, meaning even thought the screen is black I can end the call, mute it etc granted I touch the right area seeing as I can't see anything. Another thing that's going on that leads me to believe this is some sort of software bug is, when the screen is turned off due to the takeover setting, when I press the home button to turn it back on, it turns back on BUT the front app is lowered and i am brought to the home screen as if the screen was on and I hit it. Weird huh?
Any help would be appreciated…
Verizon Note 3 running on T-Mobile and CM13

LG V35 double tap doesn't unlock screen, always on display doesn't work too - Help!

Hey guys, just got LG V35 updated it to android Pie, everything seemed fine, but i can't normally unlock phone. On main screen i can double tap and it locks, however double tapping again, doesn't unlock phone, as if screen froze. Also fingerprint button doesn't work either, i mean i need to press it twice slowly and only then screen turns on and shows lock screen, always on display also doesn't work. After simple restart those features work, but after a minute, same thing happening again. Also noticed, that if someone calls, screen is also unresponsive. Got phone couple days ago. Any solution ?

Tadziunia said:
Hey guys, just got LG V35 updated it to android Pie, everything seemed fine, but i can't normally unlock phone. On main screen i can double tap and it locks, however double tapping again, doesn't unlock phone, as if screen froze. Also fingerprint button doesn't work either, i mean i need to press it twice slowly and only then screen turns on and shows lock screen, always on display also doesn't work. After simple restart those features work, but after a minute, same thing happening again. Also noticed, that if someone calls, screen is also unresponsive. Got phone couple days ago. Any solution ?
Click to expand...
Click to collapse
i had the same issue when i got mine. i think the screen protector i installed was the issue-it only had adhesive around the the edge and started to come off. i returned that one and replaced it with another make and haven't had the "knock on/off" issue since. good luck
tom

tomdi1999 said:
i had the same issue when i got mine. i think the screen protector i installed was the issue-it only had adhesive around the the edge and started to come off. i returned that one and replaced it with another make and haven't had the "knock on/off" issue since. good luck
tom
Click to expand...
Click to collapse
I agree with tomdi1999 and also have used the adhesive around the edge screen protector but they interfered with screen touch sensitivity, it is as if having a couple of fingers touching the screen permanently while trying to double tap or unlock the phone via power button. If you have any glass screen protector, try removing the screen protector and double tap again to see if it fixes the issue. If you are not wanting to remove the screen protector first and want to do some troubleshooting, try run touch screen test via the hidden menu (assuming your v35 is AT&T version) by dialing *#546368#*350# (Be warned that some options in this menu can really mess up your phone so don't go around messing with options in this menu randomly) in the phone dialer. In hidden menu select Device Test -> SAAT -> Service Menu - Manual Test -> Touch Draw Test. If, with screen protector on you are having trouble doing this test, remove the screen protector, clean the screen, and do the test again. If you still have trouble with touch screen it is probably a hardware problem or could be software problem but unlikely though. Also, place a test call to someone and slowly place your hand to cover the ear piece and proximity sensor area to see if screen goes dark. This is to check if your proximity sensor is working properly because if it is not then it could be the reason that double tap to wake is not working, although it doesn't explain why your power button is responding slowly, that points toward the phone processor being busy due to ghost touches such as due to bad screen protector or just a faulty power button (but what are the chances of having a faulty power button and double tap to wake going bad at the same time lol?).
I remember that years back on LG G4 double tap function would stop working if you had the screen replaced or sent in the phone to LG for repairs such as repair for notorious bootloop issues and it turned out that there was a small rubber piece that went around the proximity sensor that people were forgetting to put back when replacing screen or doing other repairs which basically broke the proximity sensor. Proximity sensor is suppose to disable screen wake up due to accidental double taps such as when phone is in pocket but if proximity sensor is malfunctioning it will not let phone wake even when you double tap to wake it.
If you figure out what was wrong and/or fixed your issue, please do post back so it can help others. Thanks.
Edit: If you are looking for a good screen protector try Skinomi or Armor Suit wet screen protectors. They are not glass and are a pain to put on but once you install them and let them dry, they are awesome.

It helped me thanks a million!
wouldn't think ever it was the screen protector, thought one of my apps...
I've removed it and it was back to normal.
thanks again