I am unable to pull down the notification bar while on a call using my Bluetooth headset. When my finger gets near the top of the screen, it trips the proximity sensor and blanks the screen. I'm not sure if this is a design flaw or something that I can fix. There are MANY times that I want to use my phone while I am talking to someone and it seems stupid to me that I cannot interact with notifications while I'm on the phone. Anyone else experience this issue and/or have any suggestions? Thanks!
Swipe down starting at the htc logo or just to the right of the center. The proximity and light sensors are just left of center.
This works, just tried it.
http://forum.xda-developers.com/showthread.php?t=694888
No fix yet I'm afraid I'm sure the developers here will figure something out though...
Thanks so much for the information guys. Glad to see this has already been brought to Sprint's attention. Hopefully they will get a fix pushed out soon.
Related
While im in a call on my G2 randomly the call will end or it will get muted or it will go on speaker phone. It seems like there is a proximity sensor or a light sensor in the upper left of the phone and randomly it freaks out mid call and turns on the screen and my cheek hits some of the touch buttons. It is very annoying. Randomly ill be in a conversation with my girlfriend and it will hang up -_-. maybe when we get root access or more api access to that sensor we can turn it down or something like that. Anyone else having a similar problem?
ChaosXIII said:
While im in a call on my G2 randomly the call will end or it will get muted or it will go on speaker phone. It seems like there is a proximity sensor or a light sensor in the upper left of the phone and randomly it freaks out mid call and turns on the screen and my cheek hits some of the touch buttons. It is very annoying. Randomly ill be in a conversation with my girlfriend and it will hang up -_-. maybe when we get root access or more api access to that sensor we can turn it down or something like that. Anyone else having a similar problem?
Click to expand...
Click to collapse
This is a common problem with smartphones that use proximity sensors. Whether or not you get this problem depends on how you hold your phone to your head and possibly whether you have long hair (there is some argument about that). Some phones also do have more problems than others, suggesting it might be related to programming of the proximity sensitivity/hysteresis.
I see. I actually do have long hair... that could be a factor. My hair could be moving across it or moving and it could be triggering the sensor. Maybe once we get root access we can see if there is a way to disable the sensor altogether for calls. I like the auto back light feature but so far in calls it is very annoying. Shouldn't be too hard i think.
One thing I like to do is cover the top part where the sensor is first with my ear / side of my head then place the rest of the phone on the side if my face. So angling it basically, whole process takes about 2 secs. Hope this helps.
fRom Snugs G2 ^.^
I have the same problem too, its annoying. What I do is that I try to keep the sensor area (top left of the phone) as close as possible to my case, also as covered as possible. Kepp the bottom half of the face a little bit away from the face (cheek). - this way you wont set off any on screen buttons if light does get through the sensor.
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help
Remove your screen protector.
Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else
kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again
Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help
I've had this issue since I got the device at popup in London on 21st July
The proximity sensor only seems to register if skin is actually pressing against the glass where the sensor sits which is bad because unless the top of my ear is in exactly the right place the screen stays on during calls meaning random key presses.
I'm thinking now this is a hardware issue, don't really want to RMA if I can help it.
Does anyone know any way to tweak the sensitivity of the sensor with a setting /line of code etc?
Mate, that does seem like a RMA.
I have no trouble with the proximity sensor. Works fine without touching the glass .
Know that's not what you want to hear but better to get it fixed now instead of investing a few days and still having to RMA....
Extra couple of days suffering and longer to wait return....
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**
I am having issues with my Z3 proximity sensor being activated when it's not supposed to.. e.g. when I receive a call the screen will just go black and I cannot answer the call or even see who is calling me, same when I dial out, I just have to hope the other person hangs up or I have to soft reset my phone with power + vol up until it turns off then restart.
I have tried all the silly apps and none of them work, or they are just bloated with ads etc. and besides I would rather not have to rely on an app for this. I have read in a few places that the proximity sensor is at /dev/cm3602 but only on certain devices, and possibly only on ICS/JB.
Surely there must be a way to disable the proximity sensor via root shell?
I have tried so many things, at first I thought it was a firmware issue, but after trying various ROMs I figured it's not. What confuses me is that the proximity sensor and light sensor are the same sensor, and the light part works fine but the proximity doesn't.
Is there anyone out there who knows anything about this? Has done this before? Or is willing to give me any idea on how to get going in the right direction?
Cheers in advance..