Help Proximity sensor not working on received calls

[Roymus]

I'm having a weird problem with the proximity sensor since upgrading to JB from ICS. The sensor will work on calls I make, but on calls I receive it invariably does not...resulting in all kinds of embarrassing key presses when receiving a call. What's more, I notice that the dialer behavior is different on calls...the keypad used to stay on, but now it disappears on calls. I've tested the sensor with Sensor Test from the app store, and it appears to be working fine...it only seems to stop working on received calls anyway. I've also checked Settings to make sure that the proximity sensor checkbox is checked in Call Settings. Any ideas? Thanks all...

 

[rcsrich]

I'm having a weird problem with the proximity sensor since upgrading to JB from ICS. The sensor will work on calls I make, but on calls I receive it invariably does not...resulting in all kinds of embarrassing key presses when receiving a call. What's more, I notice that the dialer behavior is different on calls...the keypad used to stay on, but now it disappears on calls. I've tested the sensor with Sensor Test from the app store, and it appears to be working fine...it only seems to stop working on received calls anyway. I've also checked Settings to make sure that the proximity sensor checkbox is checked in Call Settings. Any ideas? Thanks all...

You might try the dreaded factory reset- it can often clear up odd issues that pop up after an OS upgrade...

 

[Roymus]

Just did a reset when I updated my custom ROM and it didn't seem to help (I know, it could be the ROM too, although I've noticed the problem before). I may try another reset but it's a bit of a pain, will wait and see if there are any other solutions.

 

[Roymus]

FWIW, I have figured this out. The problem I described in OP only occurs if I answer my phone using the Home button (this is an option in Call Settings). By answering the call using Home button, you display the Home screen (rather than the Call screen) and therefore the proximity sensor is turned off. If you use the call swipe to answer, you stay on the call screen and the proximity sensor works.

I really feel like the proximity sensor should work on ANY screen, not just the call screen...if you put the phone up to your face, the dang screen should turn off. But, at least I feel better having solved the problem. Answering the phone using the Home button was a useful feature, but I don't feel like I can use it this way because I don't want to be fumbling around trying to turn off the screen while on a call (note also I use the power button to end calls, so I can't turn it off that way). Any ideas are welcome...it's a minor annoyance at best.

 

[rcsrich]

FWIW, I have figured this out. The problem I described in OP only occurs if I answer my phone using the Home button (this is an option in Call Settings). By answering the call using Home button, you display the Home screen (rather than the Call screen) and therefore the proximity sensor is turned off. If you use the call swipe to answer, you stay on the call screen and the proximity sensor works.

I really feel like the proximity sensor should work on ANY screen, not just the call screen...if you put the phone up to your face, the dang screen should turn off. But, at least I feel better having solved the problem. Answering the phone using the Home button was a useful feature, but I don't feel like I can use it this way because I don't want to be fumbling around trying to turn off the screen while on a call (note also I use the power button to end calls, so I can't turn it off that way). Any ideas are welcome...it's a minor annoyance at best.

Glad you figured it out- and I agree, if using the home button is an option to answer calls, it should work in conjunction with the proximity sensor!

 

[ExtremeNerd]

FWIW, I have figured this out. The problem I described in OP only occurs if I answer my phone using the Home button (this is an option in Call Settings). By answering the call using Home button, you display the Home screen (rather than the Call screen) and therefore the proximity sensor is turned off. If you use the call swipe to answer, you stay on the call screen and the proximity sensor works.

I really feel like the proximity sensor should work on ANY screen, not just the call screen...if you put the phone up to your face, the dang screen should turn off. But, at least I feel better having solved the problem. Answering the phone using the Home button was a useful feature, but I don't feel like I can use it this way because I don't want to be fumbling around trying to turn off the screen while on a call (note also I use the power button to end calls, so I can't turn it off that way). Any ideas are welcome...it's a minor annoyance at best.

This could be a limitation of your custom ROM. Or, this could be a bug the devs don't know about. I would suggest reporting this in the ROM's thread. They may not know that custom mapping is an issue.

 

[deebondlvn]

I have any unusual keypad issue. If I make a call and have to use the keypad to enter say my bank account number or the old press 1 for English as I get clse to the keypad it disappears, when I move away it reappears and it goes on and on until finally I am able to catch it and press the button. I have called both Sprint and Samsung and they have no clue, actually I think they thought I was looney! It is driving me nuts, as is the constant change of time on the phone and the no service and roaming in my own house. I cannot place many calls inside my home and outside is not much better. I thought I liked this phone but not so sure anymore. HELP!!! I have done soft reset, hard reset as given instructions by both Sprint and Samsung, nothing works! Strange thing is my husband has the same phone and uses his own similar Sprint plan and his works perfectly.....I cannot convince anyone that this phone is defective. UGH!!!

 

[funkylogik]

Do you know where the sensor is on your phone? (Just to the right of the call speaker)
Make sure youre not in the habit of putting a hand too close to that or have a case or screen protector too close to it :thumbup: