Database Info

Proximity sensor issues?

I'm running CM 7.0.3, and I'm having massive proximity sensor issues, t the point where the phone is becoming unusable. If I'm in a call and I don't manually shut the screen off, the following happens (constantly):
I'll feel some haptic feedback on my ear, and my voice will mute. When I look at the screen, the lock screen is up and when I unlock it, it's at the dialer screen. I'm not hitting the mute or hold button with my ear, it seems like once it gets away from the call screen, my voice is muted.
Needless to say, this is getting massively annoying. Later tonight I'm going to try to see if using a Sense based rom fixes this, but I'd much rather stick with CM. Has anyone else experienced this?

I believe there is another post on this.. you can also Google search for inspire proximity sensor adjustment - someone created an app to adjust the sensor
Sent from my Desire HD using XDA Premium App

The thread in question:
http://forum.xda-developers.com/showthread.php?t=1062561
EDIT: I haven't used the proximity sensor adjustment application that's linked in the thread as mine is working normally. If it doesn't work there's a possibility the sensor's faulty and should be replaced (I recently went through this whole thing with my old iphone 4).

Yeah, to be honest, I tried that app and it didn't seem to make much difference. I'll try calling HTC

Flashed to a sense based ROM, and the sensor seems to be working fine. Very odd, to be honest. I will say that after using AOSP for so long, I have no idea how you guys deal with Sense at all.
Well, now I have to decide: I can live with Sense, or I can ship my phone back to HTC and be without a device for 2 weeks. Going to try out the proximity sensor app again, but it didn't seem like any setting made a difference, but it could be that I just don't know what I'm doing with it.

Check under Settings>Call Settings and put a check mark in the "Always use proximity" box. It says it's to help with prox. sensor screen locking when the phone is horizontal, but the CM7-based ROM that I was using showed the same issues and I fixed my particular issue by checking that box.
Tested with a few calls and the screen is definitely shutting off when the phone is standing or lying down.

I read up on the proximity app, and I think I have it calibrated properly at 5/6. It certainly helps, but it's definitely not perfect. Night, thanks for the advice, but yeah, that option has been checked from the start. At least the issue is tolerable now, before it would do this 10 times per call.

Funny - mine was calibrated at 10/11 by default and works pretty well. Try going up to those values. I used a local time/temperature number here, and it worked well when my finger got 1/8" or so from the phone. While I admittedly haven't measured the depth of my ear or anything, it does seem to be working well at those settings.
I think the upper threshold is where you may want to adjust. From my playing with that app, changing the lower threshold too high will make it ignore things too close to the phone and so will an upper threshold that is too low. Try lower 5, upper 11 and see what happens. Anything between lower and upper apparently triggers the sensor. (<<< speculation without documentation)

[Q] the telephone...

So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?

PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?

This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...

ghost/phantom touch issue in 1+7pro not solved

I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument

My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.

will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps

Issue is back again after 9.5.9 update.

IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.

I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.

Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...

UPG to 9.5.10 Plz - Issue has disappeared again.

ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.

Do you have a dirty screen protector?

This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...

I just Installed android 10 May Update (52.1.A.2.1)

So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.

Well, sadly I couldn't fix the issue with the voice notes, but I disabled the "ok Google" feature from the Google assistant and I haven't had any problem with voicenotes anymore, let's see if it stays like that.
It didnt solved the problem, I plan to go back to android 9

Does not feel any fix, but so frustrating 'couse battery capability is much much worse...

I think the fingerprint at least is faster and more reliable.

ferluna18 said:
So, what the title says, I just downloaded it from xpirifirm and Installed it using flashtool, am hoping to fix the problem with voice messages from WhatsApp and messenger as well (basically 1 in 10 voice messages I send go silent in the middle of the recording), there is not a changelog from Sony but they never give any so I hope this could be more than just a security patch, I want to know if any of you have installed it and if you have noticed any fix, thanks, If I find out something I will tell you. Thanks for reading.
Click to expand...
Click to collapse
I fixed the voice messages disabling the feedback tactile of 3 under screen buttons

Did the upgrade change your GPS functionality? Since the day I updated, my phone started drifting. I have 25 kilometers displacement on a day staying permanently at my home office. Compared to 0.5 kilometers before the update.

I didn't understand how you fixed the voice messages, can you be more specific?

Hey guys, it's July 9th and the last firmware released for xperia xz2 is 52.1.A.2.1, will Sony stop supporting this device or what? Btw my cellphone has now a ghost touch.

ferluna18 said:
Btw my cellphone has now a ghost touch.
Click to expand...
Click to collapse
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.

sersel2 said:
Same for me! Just about a week or so, I am annoyed by the quick settings bar being occasionally pulled from top while typing on the keyboard or working in apps. With the "Show taps" option turned on from the developer settings, I can clearly see that the device sometimes detects an extra tap (draws the corresponding circle) at the very top of the screen right after I tap somewhere else. This activates the system bar and switches the focus from the app. This only happened before with the screen very dirty or wet (i.e. in the rain). However, this time cleaning it and rebooting the system didn't help. My initial idea was that I could have damaged the screen sensors or other hardware somehow. But this might be instead a planned action to support the upcoming models' sales Interestingly, there was no software update accompanying the behaviour change — seems like there are some remotely controlled sensor options their engineers could be playing around.
Click to expand...
Click to collapse
Thanks for sharing your experience, well I still have the ghost touch but now occurs more often and I have had another issue since some months ago ad well and tje thing is that sometimes the proximity sensor "detects" it's being covered and makes the screen flash several times during a call or hearing voice notes in whatsap, sometimes the failure is as bad that I have to restart the phone, I don't know what could be causing this problem but I have to say that I have dropped some water in my cellphone in the past two or three times, and I don't know, maybe some of this water came into the phone through the earpiece and messed with the upper part of the screen and the other sensor up there, my phone os almost a year old now, Do you guys think it might mot be water resistant anymore? And btw, have you dropped water in the phone as well? Thanks for reading.

Proximity Sensor Location/Issues

Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.

Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.

apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.

Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.

apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.