Database Users

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

[Q] Can't hangup or use buttons in call (cmod 11)

Hi everyone,
I've got a used LG G2 with a broken display that I just replaced. Everything works with CyanogenMod 11 20140708-snapshot-m8-d802 (4.4.4), except for the dialer which acts up weird.
When I place or receive a call, the display turns black, and it doesn't come on again when I remove it from the face - seems like the light detector isn't working. I can turn on the diplay by using the power button though. Here another problem araises; I can't use any of the button on the dialer screen. I can't hang up, I can't enable the speakphone or show the numberpad. I haven't done any modding expect for installing a new rom and wiping the previous users' data.
Any ideas?

decon89 said:
Hi everyone,
I've got a used LG G2 with a broken display that I just replaced. Everything works with CyanogenMod 11 20140708-snapshot-m8-d802 (4.4.4), except for the dialer which acts up weird.
When I place or receive a call, the display turns black, and it doesn't come on again when I remove it from the face - seems like the light detector isn't working. I can turn on the diplay by using the power button though. Here another problem araises; I can't use any of the button on the dialer screen. I can't hang up, I can't enable the speakphone or show the numberpad. I haven't done any modding expect for installing a new rom and wiping the previous users' data.
Any ideas?
Click to expand...
Click to collapse
Sorry. I have the exact same problem. Began on PA 4.4.4+ and now back to stock and still does not work. Have you figured it out? Seems like a problem with the proximity sensor and no way to turn it off. Frustrating.

Sorry to hear that I ended up fixing it by hard resetting my phone with the software provieded by LG. I haven't installed a new custom rom since - instead I use the LG rom and customize it with the Xposed framework and the G2 Settings module. It works great, except for some random update notifications from the LG app store from time to time.
Not really a the solution that I has looking for, but now I can use the phone as it was intended. Please keep me updated if you come about some other workaround.

Screen keep waking up with Touchwiz Rom

Hi All,
There is some hardware issue with my S4 that it will wake itself up randomly every few seconds. It has this issue with every touchwiz rom I put on, Kitkat or Lollipop (fresh install so that I know it's not caused by some apps installed later). I'm sure I have tried everything like disabling air gesture, every senor related function that I'm aware of.
I used wakelock trying to track which apps triggered the wake with no luck.
I also tried gravity screen, no luck.
The only fix so far is using a cm rom. I suppose it's because cm rom ignores some sensor info compared to touchwiz. I can stay with cm but I really like the stock camera.
Can anyone cast some light on how to fix this screen wake up issue on touchwiz?
Update: Finally got this fixed. The fix is very specific to this phone. As I mentioned this phone has some issue including home key not working and the random screen wake. After disable home key mapping in Generic.kl and gpio-keys.kl by adding # in front of key 172 Home, screen wont wake up by itself again.

shadowcliffs said:
Hi All,
There is some hardware issue with my S4 that it will wake itself up randomly every few seconds. It has this issue with every touchwiz rom I put on, Kitkat or Lollipop (fresh install so that I know it's not caused by some apps installed later). I'm sure I have tried everything like disabling air gesture, every senor related function that I'm aware of.
I used wakelock trying to track which apps triggered the wake with no luck.
I also tried gravity screen, no luck.
The only fix so far is using a cm rom. I suppose it's because cm rom ignores some sensor info compared to touchwiz. I can stay with cm but I really like the stock camera.
Can anyone cast some light on how to fix this screen wake up issue on touchwiz?
Click to expand...
Click to collapse
Hi
I've been having the same problems with my phone, I think I've managed to fix the problem,
I went to settings, device, display, then at the bottom turn off 'ambient display'
Problem seems to be gone

Oxygen OS Annoyances

Hi everybody, i upgraded to the OP5 midnight black from my OP3 with LineageOS and as last year, I'm trying to stay on OxygenOS for as long as possible
Basically I like OOS, but there are some things that just don't make sense to me (those things are not new, but I noticed them when switching back to OOS):
- Dash charge sound: when i plug in the dash charger, i see this lightning animation followed by a sound/jingle. I can't check right now, but I think this only happens when the screen is not unlocked, but also when the phone is on silent/DND mode. At least give us an option to deactivate it.
- Ringer volume to zero: I'm perfectly happy with the stock android volume management. All, DND, and silent - most of the time my phone is in my pocket or in my hands, thus i do not want a ringtone. Sometimes the phone is on my desk and i'm some meters away - that's when i need a ringtone. On LineageOS/Stock Android, i could just raise the ringer volume from zero to the volume i want. On OOS, things are different and I do not like it. Why change it in the first place?
- also i'd like to control the media volume with the volume rocker keys by default (i change ringer volume maybe once a week). this used to be an option in one of the LineageOS / Cyanogenmod versions I think.
- camera disables flash when battery is under 15%. Most of us are grown up people who should be able to decide for themselves if they want to save battery or take a good photo.
- minimum brightness is to high for me and auto brightness is buggy.
- button backlight is too short / only lit after a button is touched.
What do you guys think about these things? Are you annoyed as well or do you think these "features" are legit? If you know of mods/hacks/tricks to fix one of the problems, feel free to share. thanks in advance :good:

Most of these things have already been criticized on the OP3/T and brought to OnePlus' attention months ago.
They didn't listen unfortunately.
Especially the fact that we can't mute our phones with the volume down button is mind-boggling!
Been this way since OOS 3.5 Marshmallow Beta1 on the OP3 and users started complaining. We are at Beta 18 + numerous stable builds later.
I think it speaks for itself.
I'm missing DND mode + vibration because of this.
Also when the device is on the upmost slider position (silent),
it will also silence android wear devices and render them useless for notifications!

tukiii said:
...minimum brightness is to high for me and auto brightness is buggy. ...:
Click to expand...
Click to collapse
I use Lux (on playstore) which completely overrides the built in auto brightness with an easier to control alternative. To use plugins requires root but I am not using plugs on my OP5.

3DSammy said:
I use Lux (on playstore) which completely overrides the built in auto brightness with an easier to control alternative. To use plugins requires root but I am not using plugs on my OP5.
Click to expand...
Click to collapse
That app got buggy on marshmallow - is it any better in N? Doesn't look like it's been updated in over a year. (Just curious.)

Elnrik said:
That app got buggy on marshmallow - is it any better in N? Doesn't look like it's been updated in over a year. (Just curious.)
Click to expand...
Click to collapse
I didn't have any issues with it on AICP Nougat 7.1.2 on a TabS SM-T800. Now on the OP5 (v4.5.4) it works well although occasionally it does not seem to start on a reboot but with so many OTAs so quickly I can't nail when that started. Its also not a consistent issue. Once started it sticks and works as advertised. Lux has been part of every Android device I've owned for a long while now. I really like using the profiles for example one for inside, outside and watching videos (Youtube, Netflx, Plex ...).

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.