I have been facing this issue where my calls keep getting muted due to accidental touches during calls. Now, what i understand is that the sensor should detect the phone being raised and keep the screen off during the call, however, it doesn't always work and my calls get muted by my face multiple times. Is there any way to fix this or change the sensitivity settings?
Thanks!
iLithiyum said:
I have been facing this issue where my calls keep getting muted due to accidental touches during calls. Now, what i understand is that the sensor should detect the phone being raised and keep the screen off during the call, however, it doesn't always work and my calls get muted by my face multiple times. Is there any way to fix this or change the sensitivity settings?
Thanks!
Click to expand...
Click to collapse
I've been having the same issue and it's very annoying.
iLithiyum said:
I have been facing this issue where my calls keep getting muted due to accidental touches during calls. Now, what i understand is that the sensor should detect the phone being raised and keep the screen off during the call, however, it doesn't always work and my calls get muted by my face multiple times. Is there any way to fix this or change the sensitivity settings?
Thanks!
Click to expand...
Click to collapse
Well known problem. There are some workarounds but none of which are convenient or obvious and none of which we should be required to use. I thought I saw an update on the December patch due out today but we'll see. Yes, it's extremely annoying on multiple fronts.
iLithiyum said:
I have been facing this issue where my calls keep getting muted due to accidental touches during calls. Now, what i understand is that the sensor should detect the phone being raised and keep the screen off during the call, however, it doesn't always work and my calls get muted by my face multiple times. Is there any way to fix this or change the sensitivity settings?
Thanks!
Click to expand...
Click to collapse
One of the fixes in today's update will be "General improvements for sensor stability & response in certain conditions". Hopefully that will address the problem that you and others are having (I've not encountered that problem).
Also, I've read that clearing the Phone app's cache has helped some people, for what it's worth.
I use earbuds for this reason specifically. Had the same problem on my 4xl and 5 as well. I think it's just garbage thresholds set for when to turn off the screen and turn it back on.
Related
When I make or receive calls the screen turns black and the touchscreen is disabled. I assume this is to avoid accidental keypresses with my ear or something, but my phone doesn't leave this mode until call ends.. I assume it would switch on screen/touch when leveled horizontally, but it doesn't.
I cannot end the call or do anything while the screen is disabled.
The only thing that works sometimes is to double press power button to turn on camera (thus enabling screen/touch), but it is no reliable method.
Sometimes, if I call a person not taking the call, without mailbox or automatic termination of connection, I have to reboot to phone to end this.
Any idea what I can do? Can this supposedly helpful behavior be switched off or fixed?
I am on Android stock 8.1.0 (OPM6.171019.030.H1, Aug 2018), rooted with most recent Magisk.
This bug is driving me nuts, so Thank You for any ideas or help!
Is there anything blocking the proximity sensor (below the right of the speaker)?
nowster said:
Is there anything blocking the proximity sensor (below the right of the speaker)?
Click to expand...
Click to collapse
Not that I know of. All is as normal as can be.
But right now, it seems the "trick" with the camera double click works more reliably (>50%) than before. Whatever reason..
If you've had the phone apart recently ... check proximity sensor. There's a little rubber piece tends to fall out.
Did You applied a screen protector recently? I had the same issue because of screen protector was covering the proximity sensor
Ever since I bought the phone I had this issue which has not been solved with recent rom updates nor application updates. Basically while playing a voice message, either in WhatsApp or Telegram, the screen goes black (without putting the phone close to the head) and the audio switch from the speaker to the ear capsule. Even more, when this happens, the screen is stuck and I can't turn it on neither by double tapping the screen or pressing the power button. The only way to turn it back on is to put the phone "parallel to the ground", I know it's strange but that is. Other times, when this happens the audio is also distorted.
Are you experiencing the same problem?
Cheers.
Just checked. No problems. Do you have anything that covers the distance sensor?
Nothing installed on the phone (tempered glass etc.) it happens with just the MI cover installed. Also, it happens when I have the phone in my hand, if it's flat on a surface there's no problem.
Just made a research on the official forum and I found out that a lot of other users are experiencing this issue.
I'm facing the problem with distorted audio when recording whatsapp messages. But happens only sometimes, don't know how to reproduce. Proximity sensor bugs also sometimes... in my case the screen doesn't goes black, which leads to accidental touches..
PurPLe SKy said:
Ever since I bought the phone I had this issue which has not been solved with recent rom updates nor application updates. Basically while playing a voice message, either in WhatsApp or Telegram, the screen goes black (without putting the phone close to the head) and the audio switch from the speaker to the ear capsule. Even more, when this happens, the screen is stuck and I can't turn it on neither by double tapping the screen or pressing the power button. The only way to turn it back on is to put the phone "parallel to the ground", I know it's strange but that is. Other times, when this happens the audio is also distorted.
Are you experiencing the same problem?
Cheers.
Click to expand...
Click to collapse
The same thing happened with me.
Any solution?
I think this happens only when i get a message... i guess the sound notification from the incoming message disturb the ongoing voice WhatsApp message
Tgcastro said:
The same thing happened with me.
Any solution?
Click to expand...
Click to collapse
None. This problem is quite common even on other Xiaomi devices (MI 9, Redmi Note 7 etc.) but not everyone is complaining about it.
I have the same problem -and always had- on a Xiaomi Mi MIX 2 running LineageOS, so I guess it depends on the firmware.
I've same issue
Solutions?
Thank you
No problem package blocking WhatsApp at all...
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
vinay3190 said:
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Click to expand...
Click to collapse
It's issue on most OnePlus phones.. I had the issue on 6T, 7 Pro.. annoying
1rahul1996 said:
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
Click to expand...
Click to collapse
This is the biggest reason I may be going Pixel 4...
Yes I too have this issue with my OP7T
Yup, same issue here.
Another thread about it here - https://forums.oneplus.com/threads/proximity-sensor-doesnt-work.1147600/
Also issue present on OP7Pro forums.
Seems to be related to this "Virtual Sensor":
https://www.ellipticlabs.com/2019/0...eaner-design-to-oneplus-7-series-smartphones/
So we have to wait and hope (could be this same as Never Settle? :d) that can be fixed with a software update.
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Josh McGrath said:
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Click to expand...
Click to collapse
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
trveller72 said:
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
Click to expand...
Click to collapse
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Josh McGrath said:
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Click to expand...
Click to collapse
Yeah, I am starting to remember good ol' days with the OPX. Every OTA was fixing one thing and breaking 3 other.
At that time I said no OP again, but still, this one seems to be be a good phone. Time will tell.
Coming back to our issue, I am puzzled that only a few people reported this.
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
roofrider said:
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
Click to expand...
Click to collapse
Not rooted, but using a custom dialer as the default Phone app (True Phone).
When I switched the default Phone app to Oneplus App, I could not reproduce the issue.
Testing for a few days to see if this works. Would be such a pity if the app is the problem because I really like it.
Also I just sent a log to OP support (they contacted me after I logged the issue on the feedback).
Yes, it is using the virtual sensor as you said (link in my previous post).
How does the virtual sensor work?
Sent from my [device_name] using XDA-Developers Legacy app
I couldn't find anything concrete on how this software-based proximity sensor, Elliptic Labs INNER BEAUTY, works. The keywords are: ultrasound, sensor fusion, and machine learning. A hardware-software I guess.
The 7T does have an IR sensor under the display, but I think this is only used for DT2W and Tap to Show to prevent the display from accidentally turning on when the phone is in the pocket and so on. Not for calls.
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
igotlostintampa said:
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
Click to expand...
Click to collapse
Twrp is out for the 7t. It's not flashable last I checked but it is bootable and usable for what I used it for which was a backup of stock rom
After a few days of using this device i noticed that my screen turns on during phone calls. After doing some research it came out that the proximity sensor is not working properly when phone is being tilted to horizontal position with screen upwards. It just immediately shows that it is far away from any object even that it isn't. The fun fact is that when covering the sensor with my hand while phone is laying on his back doesnt switch it and rotating the phone to vertical position also does not make any effect like the sensor would be locked. Covering it again in that position makes it work.
Can anybody help me with this issue? It's very annoying for me and makes my phone unusable for making calls.
Edit: similar problem here https://forum.xda-developers.com/android/help/huawei-nova-5t-proximity-sensor-problem-t4136595
Same problem here...
here also
I am so lost. What do I do with the phone? What? When does it happen? (Also subscribing.)
Same here, and i notice i have also problems with whastapp and telegram audio notes.
Sometimes screen goes blank randomly and with no reason when i'm listening a audio note.
Hi. Its a well known problem. Its becouse the device has a ultrasonic sensor not like any other. Sensor like you already find out works only in vertical position of the phone. Its well described in the net how it works. Just search. In 4PDA in the section for our phone. But you need to know russian.
I found that thread and it seems that not everyone notices that... Not spending more time on reading this I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Same problem here, it's very frustrating. I can turn the screen back off during a call once I see it's turned on by itself, but it keeps turning back on. I'm sick of muting calls and hanging up on people by pressing buttons when I'm on the phone.
What is the app that you are using @Spectre45?
Spectre45 said:
I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Click to expand...
Click to collapse
Can you please tell us what app you are using?
kage00 said:
Can you please tell us what app you are using?
Click to expand...
Click to collapse
try proximity screen off or call proximity screen fix
LightSmok said:
try proximity screen off or call proximity screen fix
Click to expand...
Click to collapse
Thanks
Listen. There is no proximity sensor at all. The upper mic, speaker and the sensor for orientation are doing the job. When you pick a call the speaker is sending ultrasonic signal and if it locate your ear it dims the screen. Once it works it is working in all positions. But if you move your phone away only in horisontal position it will nit work untill you mive it in vertical again.
Edit: Experienced this issue too. Annoying.
Does using Xiaomi.EU fix this problem? This issue really gets on my nerves. I started daily driving this device (finally I was able to unlock) and I just cannot use it for calls, which is kinda ridiculous from a phone.
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
I was using the phone with cover provided by MI, upon removing that back cover I encounter no such issues.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I didn't have any proximity issues on stock with google dialer. It's not google dialer, it's how you position your head against the earpiece. Sensor is ultrasonic, so it probably doesn't detect properly depending on the position people hold their phones in...
I have the same problem with my work phone - redmi note 9. Tried the app "proximity screen off" but MIUI keeps killing it no matter what i do to keep it alive. It seems that sensor is located on front top right side of the phone so sometimes it gets behind your ear if you are right handed (mine are pretty small) and then the muting starts. When using the phone with left hand - no problems at all.
I would love to have a working app to keep screen off during call.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I also flashed EU rom and the problem persistes.
Just wanted to know if other users have this issue.
I do a lot of phone calls for my work and since I switched to this phone I can not make a decent phone call at all... lol
Every couple of minutes or less the call breaks off. That is either because the other side can't hear me anymore, either the connection breaks off.
Also noticed that when receiving notifications during calls, the screen lightens up so I do get false touches which results in a total chaos on my screen...
I already placed sim to other slot, tried all different preferred network type, rebooted...nothing helps.
This is really annoying as on my other phones like F2 Pro and MI9 all ok.
Anyone having the same issue?
EDIT : 16.04.2021 I noticed now that due to the bad ultrasone proximity sensor the screen lightens up and makes a lot of false touches resulting sometimes in a mute of the mic on dialer or even shutting down the phonecall itself
Yes, it has also happened to me that the screen does not go out when I am on the phone. If you take the phone away from your ear for a moment and then go back to it, the display goes off.
CHGICEMAN said:
Yes, it has also happened to me that the screen does not go out when I am on the phone. If you take the phone away from your ear for a moment and then go back to it, the display goes off.
Click to expand...
Click to collapse
Yea already am doing that often because of the screen lightens up.
But did you also encounter a lot of false touches and even the call shutting off?
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
CHGICEMAN said:
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
Click to expand...
Click to collapse
This is related to proximity sensor
Value is 5.0 when no covered and 0 when covered.
Test is ok but in call screen didn't turn off.....so should be a softaware bug I think.
CHGICEMAN said:
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
Click to expand...
Click to collapse
nicnic94 said:
This is related to proximity sensor
Value is 5.0 when no covered and 0 when covered.
Test is ok but in call screen didn't turn off.....so should be a softaware bug I think.
Click to expand...
Click to collapse
Yea I already tested that before this post. It's working fine. No problem with that.
Problem is that when receiving a notification the screen lights up and it shouldnt. I cannot find the issue for now.
Also and this is more important : when making a call, the line gets cutoff (people cant hear me but I can).
This happens so often and never had this with my other phones running.
Already unchecked 5G, even 4G and now on 3G. Same issue.
Will look further into it...
Do you use always on display ? Maybe that's the cause? Maybe Miui optimization?
I didn't put sim card from my f1 to f3 yet, but you are making me check this out. Ill put the sim card as soon as I get case and glass. On telegram I have not seen anyone to mention this issue.
osemoka said:
Do you use always on display ? Maybe that's the cause? Maybe Miui optimization?
I didn't put sim card from my f1 to f3 yet, but you are making me check this out. Ill put the sim card as soon as I get case and glass. On telegram I have not seen anyone to mention this issue.
Click to expand...
Click to collapse
Nope not using AOD. Things are set to basic as to rule out issues.
Saturday I'll be unlocked though and going to check the fastboot xiaomi.eu rom
If you can make a test later on, do make a longer phone call. Also send a message to your phone when you're making a call and see what happens.
Had the same issue with my poco x3 nfc - same issue with the f3. I think either I got used to it with the X3 or it got fixed....
umairmalik2410 said:
Had the same issue with my poco x3 nfc - same issue with the f3. I think either I got used to it with the X3 or it got fixed....
Click to expand...
Click to collapse
Yea I read.
Anyway, the phonecall shutting off (other cant hear me) was all due to the fact that I accidentally muted the mic (or even false touched the red button or whatever) on the screen because of the false touches when screen suddenly lightened up.
The ultrasone proximity sensor is not the best solution to dim the screen when calling.
You can even test that in kernel settings. The value 5 goes to 0 even from behind or from the top. So in some cases the screen will light up suddenly.
On tweakers forum there are a lot of people who have the same issue with the proximity sensor too.
An infrared sensor would have been much better....
raystef66 said:
Yea I read.
Anyway, the phonecall shutting off (other cant hear me) was all due to the fact that I accidentally muted the mic (or even false touched the red button or whatever) on the screen because of the false touches when screen suddenly lightened up.
The ultrasone proximity sensor is not the best solution to dim the screen when calling.
You can even test that in kernel settings. The value 5 goes to 0 even from behind or from the top. So in some cases the screen will light up suddenly.
On tweakers forum there are a lot of people who have the same issue with the proximity sensor too.
An infrared sensor would have been much better....
Click to expand...
Click to collapse
I have a similar issue. I use a pretty thick case and it breaks the proximity sensor such that during a call the screen turns off but after the call when i move the phone away from my head, it remains permanently off, like it still thinks the phone is near my head.
Which tweakers forum are you referring to?
lukesky said:
I have a similar issue. I use a pretty thick case and it breaks the proximity sensor such that during a call the screen turns off but after the call when i move the phone away from my head, it remains permanently off, like it still thinks the phone is near my head.
Which tweakers forum are you referring to?
Click to expand...
Click to collapse
That's indeed true. It happens that the screen remains black after moving the head from the screen during call. You can even trigger that when opening the sensor part in the kernel (tap on it for a few times and test the proximity sensor - you'll notice that you even can let it stay on 0 by slowly removing your hand...)
But for me these false touches due to the screen lights up during a call makes it even worse.
tweakers translate if needed - starts from end of page 6.
Btw, I'm just using the case that came with the package.
Anyway, since they fixed the haptic crackling sound issue on v1204 eu and having already no issues on battery drain (9%/h SOT and 0.4%/h idle) , the only issue for me remains the proximity sensor.
If you pick up the call and wait 1sg or so to raise it to the ear, the screen turns off well, but if you pick up the call quickly it does not turn off, it may be a google dialer failure
Perhaps you can bring this issue to Poco's attention directly via: https://c.po.co/global/
I would also like to know if it's a hardware or software related issue.
Nemix77 said:
Perhaps you can bring this issue to Poco's attention directly via: https://c.po.co/global/
I would also like to know if it's a hardware or software related issue.
Click to expand...
Click to collapse
I already did as for the haptic motor sound issue (which is fixed now).
So lets wait for a response...
raystef66 said:
That's indeed true. It happens that the screen remains black after moving the head from the screen during call. You can even trigger that when opening the sensor part in the kernel (tap on it for a few times and test the proximity sensor - you'll notice that you even can let it stay on 0 by slowly removing your hand...)
But for me these false touches due to the screen lights up during a call makes it even worse.
tweakers translate if needed - starts from end of page 6.
Btw, I'm just using the case that came with the package.
Anyway, since they fixed the haptic crackling sound issue on v1204 eu and having already no issues on battery drain (9%/h SOT and 0.4%/h idle) , the only issue for me remains the proximity sensor.
Click to expand...
Click to collapse
For me if I use the case that came with the package, proximity sensor works fine , it also works fine if the phone is naked. but with a thick case, then it becomes a bit crazy such that i have to map the power button to end the call, else I wont be able to access the phone after or during a call unless i shake it hard
Reboot and shutdown issues have been acknowledge by Poco, will addresses in the upcoming updates:
Poco F3 battery drain & random reboot issues to be fixed with next update
A community mod has informed that the battery drain and random reboot issues on the Poco F3 are to be fixed with the next update.
piunikaweb.com
I really hope it's a software issue because I plan on placing my order for phone this weekend.
I wonder where's the proximity and ultrasonic sensor. *#*#miui#*#* can't test it. Using nillkin's case, one works perfectly, while the one with the thicker camera protector blocks the sensor and calling won't dim the screen.....
experienced this with the global rom but now flashed EU rom so far everything is ok.
choobs95 said:
experienced this with the global rom but now flashed EU rom so far everything is ok.
Click to expand...
Click to collapse
I see. So it's a software issue huh? Then I'm gonna flash into eh and see how this weekend.