Database Users

Mid Call Proximity Sensor Problem

Does anyone know if there is a way to adjust the proximity sensor.
It's proving a problem for my wife who uses the phone. When she's on a call the phone is intermittently sensing if she's holding it to her ear.
Hence being a capactive screen, when her cheek brushes the screen during a call the other end either hears DTMF or gets cut off by it touching the end call.
I called her yesterday and kept getting random DTMF digits sent to me, then I got sut off.
I was watching her use the phone and the screen was de-activiting (correctly going blank) for part of the call then coming back on, this would happen several times during one call.
Is this a hardware issue or software bug. Has anyone else suffered this problem?

Also happened to me a few times touching end call wih my cheek, really annoying.

Anyone else having the same problem with the proximity sensor intermittently not working during a call?

I had that problem on the old 1.43 ROM but it was fixed when I upgrade to 1.48.

I have this problem and I constantly have to call back and say sorry to my customers and blame it on the phone...
I have reported several errors to HTC and all i get back is "Take it to the retailer and get it changed, it must be a hw error", annoying as hell
1.48 not yet official in sweden.

TouchLockPro
You can try TouchLockPro, it has an InCallTweak, using the GSensor. Searching for accessing programmatically the Proximity Sensor though, for more options (e.g unlock by Proximity Sensor). It works on HTC Leo, people confirmed.

Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil

philtrick123 said:
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
Click to expand...
Click to collapse
Indeed, TouchLockPro detects itself the available sensors and uses the available ones. Of course you can configure detailed things (via pressing the BattClock), but the defaults are already the sensible ones

Thanks again ZuinigeRijder.
Just been doing some more testing and occasionally the screen flashes on for a brief moment during a call. Could it be the proximity sensor trying to turn on the screen? Or is it the G sensor not being very accurate?
In the application is there a way for me to adjust the G-Sensor angles that activate the screen off? i.e. 45+ Degrees activate ??
Or are there any other adjustments I could make during testing??

I found one more problem... I checked it several times....
If u make a call using portrait orientation of phone app (Rotated using BSB Tweak). Proximity sensor doesnt work at all.... i made a while lyin on the bed and no matter wat i tried it wasnt turning off the screen....
Then i kept it in portrait position for a few seconds den proximity started working again...
Is there anyone who can confirm me with this problem.... or is this issue only with my HD2

Proximity sensor

I have noticed that during a phone call proximity sensor doesn't while to taking i could hear those click sound(touch sound) and after i end call somehow i am in gallery or whatsapp or some other app.
Sent from my D6503 using Tapatalk

Can't say I've experienced that myself
Sent from my D6503 using Tapatalk

I get my calls cut off occasionally. That happened with my previous SIII so I guess it is just a standard problem with proximity sensors - they're not as effective as the manufacturers would have you believe.
Sent from my D6503 using XDA Free mobile app

The proximity sensor turns the screen off when the phones in a normal talking position. If you're led down, it's likely it won't. Try it, move the phone around and put your hand over the sensor.
Sent from my D6503 using Tapatalk

its not a proximity problem as the screen stays off if it was the sensor the screen would keep lighting up
I have had this problem and posted about it already
I have tried with the double tap to wake feature off to see if it was that but no such luck!!
---------- Post added at 09:43 PM ---------- Previous post was at 09:42 PM ----------
heres the thread I started http://forum.xda-developers.com/showthread.php?t=2769679

i also find myself in different places after call, this happens with flap cover closed

I usually have same problem, I click on power button to turn off the screen and usually it solves the click problem.
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.

ikm19 said:
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.
Click to expand...
Click to collapse
never had this problem on my HTC one X
and I have never heard of the problem on other phones either!!

I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).

Turning of double tap to wakeup seems solved my problem.

my PS works great. never had that issue. maybe you should take your phone to diagnostics.

Im having the same issue. Hearing ticks/clicks when im on a call and I end up somewhere after a call. I hope Sony fixes this. Temporarily I lock my phone to prevent this problem.

ikm19 said:
Turning of double tap to wakeup seems solved my problem.
Click to expand...
Click to collapse
No it doesn't I tried that weeks ago

In the Diagnostics app, go to Test Device and run the Ear Proximity test. Mine passed just fine.
Sent from my D6503 using Tapatalk

Fixed my Proximity/Ambient light Sensor
Hi, I had this problem since new and I tried installing lots of stock and custom roms (Stock US, Stock SP, Stock TW, Miui, CM11) but it was until I installed EXISTANZ rom, and a hard reboot, and then it magically started working. I knew it wasn't a Hardware issue because when the phone boots it worked for few minutes, then stop reading samples. But I've been with this rom for 3 weeks and I don't have any problem with this (Already installed and update, reset the phone and still working).
So if you have the chance, install this rom.

double tap to wake issue
raducanmihai said:
I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).
Click to expand...
Click to collapse
Hi ,
I also encountered this issue and i performed a test with and without the "double tap to wake" option.
The result is: without the option activated all is fine but when the "double tap to wake" option is activated and the proximity sensor is covered(screen is black) if you double tap the screen it remains closed. So seems that if you are engaged in a conversation and you miss touch twice the screen, it will remain closed.

Hi all,
First sorry from bringing an old thread.
I am an owner of two black d6502 xperia z2
One of them is running perfectly, the other suffers from the same behaviour the op describe.
When handling a call, the proximity sensor works fine, it is making the screen black but it is NOT LOCKING the menu, I.e the screen is black but you can swipe the status bar down and enter different menu while the proximity sensor is keeping the screen black.
My second xperia z2 behave normally, when handling call, proximity sensor turn the screen black and locks the menu, if i swipe on the screen the software ain't responsive.
Was anyone successful to fix this issue?
Elie.

The problem is in the screen protector. There is a post in the Sony Forum how to solve the problem.

It's simple hardware problem... you have to remove back cover, find connector of proximity sensor, remove it and put again, press hard and it will work...
for long time I've had that issue, but until I ordered new sensor tried to do that trick and it helped

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?

Unintended taps during call: how to prevent them?

Hi!
I"m not the only having the problem: during a call unintended taps takes place while screen waking up is not registered during the call. So, you see, I'm not sure a proximity sensor is the reason of the problem as far as screen is kept turned off.
I have tried to reproduce the issue by fingers, but wasn't lucky.
Have you any ideas how to eliminate the problem?
I mean not-rooted official up-to-date stock firmware use case.
And, by the way, I haven't found proximity sensor calibration in service menu for A1. Is it placed somewhere into another place?

That happens to me all the time too.

Yup, me too. While in call I sometimes unknowingly turn on the flashlight and probably look like an idiot. ?

With the rn3p I would constantly end up muted. With mi a1 the problem is much less although I've noticed that numbers are still pressed. I've learned over time to switch to keypad so when something gets touched it's not the mute and at worst the other person receives some key tones.

I also have this problem a lot. I mute myself 9/10. To bypass to problem, I just lock the screen before placing it against my ear.

Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)

dejano said:
Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)
Click to expand...
Click to collapse
That's what I've been doing. That and pushing the top part of the mobile on my face just to make sure. lol
Oh and use the Feedback app and send it to xiaomi and hope they fix it on the next update.

i had this problem too, has it been fixed in the latest of updates? its a really annoying bug.

You must be doing something wrong. This issue "must" have been in all smartphone operating systems in the world, if what you are saying is the truth.
There's no way to drop the call, or press anything while you are calling someone. The proximity sensor doesn't allow turning on the screen when it's close to an object. The gyroscope also turns off the screen when you rotate the phone vertically during a call.
But all I can say is that it's not a bug, this is how is your phone knows when you are in a call, and you put your phone to your ear, or when you use your "speaker", and so the phone knows it's supposed to used it's speaker to transfer voice through the call.
Beside my poor English, try to move your phone a bit vertically before putting it close to your ear.

same problem here, also disabling ambient display... i also tested proximity sensor with some apps and it seems ok

I have that problem too from the beginning. None of the updates came up with a solution

Same here: I mute, turn on the flashlight or even open apps sometimes with my face. And thanks for the input @SmallTarzan but i know how to operate a smartphone and did not have any similar problems for the last five years. Apart from that annoying bug it's a great phone.

Wow, i dont know of this bug since i'm using custom rom from very beginning.
Try to make a call then use your hand to cover top part of the phone, screen doesn't lock??

I am having this issue too and it is really annoying

And still nobody came up with a solution???
It's easy to understand why it happens.
Proximity activates while you're in a call, but apparently the touchscreen digitizer remains working (even though the screen is off). Touching the digitizer with your ears or cheeks activates different actions while you think your screen is locked.
I can't believe how this issue is not fixed yet! That's a shame!
Same applies for the network fluctuation issues. You need to either choose 3G or 4G to avoid loosing your data connection.
Xiaomi that's more than LAME! You need to be ashamed of yourselves.

It happens to me quite often, although not always.
It's more frequent during long calls. If the call lasts for less than a minute or so, it doesn't happen.
Proximity sensor works, and screen turns off as soon as I put it at my ear.
Keyboard is off and not responding for a while. Then, all of a sudden the phone comes alive.
In my case it's not the torch. What I activate unknowingly is the handsfree loudspeaker, which can be even more embarrassing, sometimes.
Maybe it's because I am left-handed.
In an attempt to have the proximity sensor fully covered by my face, I tried to make calls by holding the phone with my right hand, but to no avail, after some time the screen wakes up regardless of everything.

Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.

AlaiSalaam said:
Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.
Click to expand...
Click to collapse
Try this app, some users say it helps.
https://play.google.com/store/apps/details?id=ss.proximityservice

Any fixes yet?

simontol said:
Any fixes yet?
Click to expand...
Click to collapse
None, same sh**

Proximity sensor not working

Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?

In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.

stanley56 said:
In the engineering menu * # * # 6484 # * # * we find 27 - Proximity sensor
When approaching the palm to the front camera should show "0".
I always showed "5", did not want to be calibrated.
I pressed Error, went out and went to the engineering menu, a miracle happened - it was calibrated.
Click to expand...
Click to collapse
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?

Fortis10 said:
No, nothing happened. As usuall, screen is always on.
Yes, proximity sensor in settings was on and I have rebooted the phone.
I really don't know what to do. Is it because of bug in Global Rom or is it hardware malfunction?
Click to expand...
Click to collapse
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.

DelphinusMinor said:
Hold your phone with your left hand. The placement sensor gets blocked by your right ear when you make calls using your right hand. Give it a go and get back to us.
Click to expand...
Click to collapse
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...

Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
I can't help there but left/right holding is an issue I guess with this phone. Or maybe it's the Pro. I forget offhand.

Fortis10 said:
Ok, non-related to left and right hand.. Now my phone gets black screen all the time during calls. I can't put it on speaker or do anything while talking with someone. I really don't know what's happening...
Click to expand...
Click to collapse
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.

Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.

jonathan_jon said:
Hi , are you on miui global stock rom? Or custom rom?
I just had the same issue , but in my case , I recently opened the bootloader and installed xiaomi.eu rom, everything was working fine. I got notification of update ,I downloaded the update , but flash it thru TWRP , and then with the new update, the proximity was not working at all. Flash again the new rom, but wiping everything , and now works.
Click to expand...
Click to collapse
Is the EU rom that better?
I mean is there any plane to compare the known issues between the global and EU ?

I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.

hi @All!
is there still no permanent solution for fixing proximity bug?
its really annoying and making me crazy....
even after making it working again using quicktune app - doing one call it is broken again

fasty said:
I'm using the miui global 10.3.3.0 PFGEUXM and definitely have some "issues" with the proximity sensor.
I'm still trying to tie down the exact nature of the problem:
With a quick test, or doing calibration, it seems to work exactly as I would expect; the screen switches off as you approach closer than about 2 inches.
However during a long call I notice the display start to flash "on" frequently in the corner of my eye and soft keys can get inadvertently pressed.
It kinda feels like it gets worse during the call, is it time or perhaps the phone warming up in my hand? Not sure.
Click to expand...
Click to collapse
Exactly what i've experienced.
Super annoying when you accidentally hang up during a call.
It happend countless times so far.
I'm on eu beta btw.
Wish there would be a solution.. . But afaik proximity is even more bugged in non miui custom roms.

I had this problem to. my proximity sensor what not responding at all. I thought it was defective because the calibration was not working to.
Then i went to the system update settings, downloaded the latest package and flashed it. After reflashing it started working with no problem at all.

Factory reset did the trick for me. Working normally now.

Install Quick Tuneup. Then do Sensor Celebration & Restart your device twice.

Two solutions
Fortis10 said:
Hi.
I have problem with proximity sensor. While making a phone call, display is always on.
I tried to enable it in settings. Turned it on, rebooted my phone and nothing happened.
Also tried *#*#6484#*#* solution, and when I open proximity sensor, there are 'test' and 'error' buttons on the screen and I can't click anything.
Does anyone know how to fix this?
Click to expand...
Click to collapse
It turns out that the problem is because MIUI does not activate the proximity sensor when the smartphone is turning on.
To force MIUI to ALWAYS activate the sensor at each start, we can do two things:
1- Always have "Automatic brightness" activated
2- Activate the "Pocket mode" (the best choice)
After applying one of these situations, it is necessary to restart the phone.
Only by activating the pocket mode it is no longer necessary to have automatic brightness activated all the time.
In the video I show how to activate the "pocket mode"
w w w . youtube.com/watch?v=2dfrqmH02O8
I published this solution in a forum in my country (Colombia).
w w w . laneros.com/temas/soluci%C3%B3n-sensor-de-proximidad-xiaomi.239997
I don't speak English, I had to use the google translator, sorry for any translation error.

2- Activate the "Pocket mode" (the best choice)
After applying one of these situations said:
KMILO_PARRA is a KING .........................
above is proof to SOLVE the Proximity Sensor no reaction in my Redmi Note 7.
I was having lots of TASKER Profile depending on whether or not Proximity Sensor is covered.
I found all those Profiles no more function due to the issue after I believe OTA to Global rom the latest ( August-2019 )
Thanks again to KMILO_PARRA
Click to expand...
Click to collapse

Actually, the proximity sensor for Redmi Note 7 isn't in the "usual" top-center position, it's a little bit on the top-right edge (if you watch the phone "against the light" you can actually see a small dot on that side).
If you're calling\responding try to put your ear at that angle, you'll never have those problem anymore.
I know it seems crazy, and of course the first times could be "unusual" to put the ear there, but it actually worked out flawlessly for me.

Mr
Quaresma_7 said:
Obviously the proximity sensor is at fault. Enter the menu using the code mentioned above, then press the menu/options button and select Calibrate proximity sensor. Once you're there, hold your hand over the proximity sensor (to the right of the front camera) and tap the Calibrate button. That's one thing that could fix it.
Failing that, go to incoming call settings and turn off the proximity sensor (turn off screen in call). Restart your phone, go to the same toggle and turn it on.
If neither of these works, you likely have a faulty piece of hardware. Your last option is to have the phone repaired or try a different kernel/ROM.
Click to expand...
Click to collapse
Thanks.....
It works for me

Hi guys,
I have made a little workaround, using the suggestion of @KMILO_PARRA user. (pocket)
https://taskerprofilecenter.blogspot.com/2019/09/project-proximity-sensor-workaround-for.html
This is mainly for Tasker users, but I have generated an APK to be installed too. So any user can use it. But what is needed, by now, is root, as it needs to write to Settings table.
Please, report me back if it does the job or not.
Note1: For those users that don't know how Tasker works, just install the app, and give it root permissions, and allow Write System Settings permission (Android option). I recommend you to not set it as an app to be killed from the OS using the battery optimization, as it could be killed. It acts on every shutdown and device boot.
Note2: It will generate two permanent notifications: Place holder, and the one that is the mini-Tasker code monitor (required). Just, disable the Place holder one, as described in the same notification (click on it), and disable notifications completely for the installed app to get rid of the last one.
---------- Post added at 12:44 AM ---------- Previous post was at 12:31 AM ----------
What it does exactly?
Well, as I explained on my web, it just changes the value (0/1) from the 'enable_screen_on_proximity_sensor' Global Settings table, that makes the pocket option to be toggleable in an automated way.
So, be sure not to use that option as a daily one, as the project/app uses it to allow the sensor be available at startup. And do not forget that you will need root too! Sorry.
What to download if I don't know what Tasker is?
You will only have to download the APK from the 'Kid App (APK)' link, provided under the 'DOWNLOAD' section. Nothing else.
If you know Tasker, you will know what to do.
Does it work really?
I'm currently testing this workaround, but as I could see, at least on my device (lavender too), seems to be working as expected. But needs to be tested a little more.
So, if it does not what it's intented for, please, report it me back.
After installing the app, giving root permissions, and allow it to modify system settings, reboot the device to take it effect.