Proximity sensor kind of wonky/bad? - G2 Q&A, Help & Troubleshooting

Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.

spinedoc said:
Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.
Click to expand...
Click to collapse
I've noticed that everything works well with this. Surprisingly so. On the s3 i would always get the black screen issue when pulling away from my ear. Ringtone even lowers as i pick it up. I could never get that to work on my s3. Not that, that matters.

spinedoc said:
Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.
Click to expand...
Click to collapse
Yes, but not all the time. When it does happen, i can't get the screen to come back on at all until after the call ends. It doesn't do it on every call but when it does it's really bad.
I'm running tge Verzion Clean Rom right now but it did it on the unrooted stock too.

Related

Standby during phone call

Anyone know how to prevent auto-locking/standby when talking on the phone?
The screen turns off when I'm talking, which I assume is from the light sensor, which is fine, but when I take the handset away from my ear it remains dark or is on lock.
fflakes said:
Anyone know how to prevent auto-locking/standby when talking on the phone?
The screen turns off when I'm talking, which I assume is from the light sensor, which is fine, but when I take the handset away from my ear it remains dark or is on lock.
Click to expand...
Click to collapse
I have the same problem since it was new. Sent it back for repair, and told nothing was wrong with it.
I uninstalled all my apps, but no improvement. shaking and tapping the phone makes the screen flash back on for half a second, but not long enough to press hang up or any keyboard numbers for automated answering systems.
I rooted the phone to see if I could get more control, but haven't found an answer yet.
first, where are you having this problem?
WinMo/Android
and second, it's not the light sensor, it's the proximity sensor.

Weird in call behavior

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.

Proximity sensor doing weird stuff since installing SlimKat on my Samsung Galaxy S3.

I searched, and didn't find any other posts about this, but the search engine here seemed a bit flaky.
I installed SlimKat 4.4.4.build.8.0 on my Samsung Galaxy S3, um, last year I think it was. I had previously been using SlimBean, having dumped the original Samsung ROM fairly shortly after I bought it. Since then there has been weirdness that relates to the proximity sensor.
I used E-Robot to disable the screen when anything is close to the proximity sensor. So put it face down, screen off; put it in my shirt pocket face inwards, screen off; leave it on the desk face up so I can see the screen, screen on. Naturally - hold it to your ear on a phone call, screen off, though that's a basic function of the proximity sensor, it did that anyway. On the flip side, if it was blanked and you uncover the sensor, the screen would come back on, but it would be the Lightning Launcher lock screen that I prefer. I got used to Lightning Launcher from SlimBean.
After installing SlimKat, when covering the sensor, first the volume controls show for a few seconds, THEN the screen goes off. Coming out again, the Lightning Launcher lock screen would not show. This got a bit awkward before I figured it out. I usually put my phone in my shirt pocket screen inward, so that the sensor triggers the screen disable. But now, since the volume control is showing for a few seconds first, I discovered that my chest would brush against the screen, randomly adjusting one of the volumes as it went in my pocket. Since I usually have the volume turned all the way up, the only way was down. I missed a few phone calls that way before figuring out why my phone wasn't ringing.
So I have disabled that E-Robot thing now. BTW, there's no way to turn the SlimKat screen blanker off? I would have tried that first, but could only find how to set the timeout, not how to turn it off.
More recently, though this may be a new hardware problem, but it's a big coincidence ... now the proximity sensor refuses to work at all. It always thinks it's covered. This is a really big pain, since as mentioned above, the proximity sensor is designed to disable the screen when you hold it to your ear, only now it disables it the moment the phone call starts, AND refuses to enable it after the phone call is over. The sensor still thinks it's being held to your ear, the screen stubbornly refuses to switch on, no matter what buttons I press. Only way I can get out of that state is to pull the battery. This is not good. (On the other hand, this sort of thing is why I always get phones with swappable batteries, as a very experienced computer dude, I know that sometimes you just have to kill the power.) So anyone I call gets to hear my swearing as I rip the case open and pull the battery out, before I can end the phone call. Though pulling the battery naturally ends the call. lol
About the same time I noticed the proximity sensor no longer working, I noticed the up volume button also isn't working. That could have been broken for awhile, I rarely use either volume control. Part of the reason for doing this entire proximity sensor disabling the screen thing is so I could avoid wearing out the physical buttons. The S3 is old, but I like to keep my computer hardware running for a long time.
Sooooo, proximity sensor and volume controls interact in odd ways, then both fail. That's a pretty big coincidence. Though having just written that, I have come up with a new theory. Maybe some common part of the physical circuitry for the sensor and the button was going flaky, such that the sensor triggering sent noise through the up volume control, triggering the on screen volume controls before blanking. Still, a coincidence that it only happened after installing SlimKat. Also, wouldn't this trigger both volume controls and screen disable at the same time, rather than within a few seconds? No idea how Lightning Launcher fits into this new theory.
So I'm still not sure what's causing this, or how to fix it. Other than going back to SlimBean to see if that fixes anything. It doesn't look like I can go forward, 4.4.4 looks like the last SlimRom made for the S3. At least according to OTA.
Anyone got any ideas? "Buy a new phone" isn't a good answer for me right now, can't afford it.
onefang,
I have a S3 that I ran the Slimkat 4.4.4 build 9 on for a while (9 months). There is a known issue with the CM package (used in SlimKat) that causes the volume button not to work correctly. When you are on a call, the call volume can not be raised or lowered. There may be other issues. I am currently running the CyanogenModCM12.1-20151117-SNAPSHOT-YOG7DAO1K6-d2att rom and the performance is much better than Slimkat.

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

I am 100% stock no fooling around yet (hotspot is my must have) surprisingly it works right from Sprint store! I have an issue with my cheekbone hitting the mute button 75%of time I answer calls. Took me a while to figure it out. I thought it was a phone issue initially till I noticed it was white which means on. Any thought on solution? Sucks having to be aware of it ever time I answer now, instead of just you know the thing going dark a moment before contact is made! Thx for reading hopefully
jblaze10 said:
I am 100% stock no fooling around yet (hotspot is my must have) surprisingly it works right from Sprint store! I have an issue with my cheekbone hitting the mute button 75%of time I answer calls. Took me a while to figure it out. I thought it was a phone issue initially till I noticed it was white which means on. Any thought on solution? Sucks having to be aware of it ever time I answer now, instead of just you know the thing going dark a moment before contact is made! Thx for reading hopefully
Click to expand...
Click to collapse
I thought I was the only one with this issue haha
I had it with my oneplus 3T as well.
This might not be the issue in your case but I found I just hold the phone oddly under normal circumstances.
I diddnt realize it but I hold it a bit off center on my left ear causing the proximity sensor to miss me.
this turns the screen on and like you I end up muting it most of the time.
I figured it out by taking it off my ear while on a call and using my hand to cover the sensor. (it turned off the screen right away as it should)
then I just experimented with placement until I realized what was happening.
it diddnt happen with other phones I had but I realized they all had smaller screens so it wasn't as easy to hold them off center without noticing.
I found I can consciously move the phone center and see the screen go off out of the corner of my eye.
unfortunately that's a bit more focus than I like to put on it so I usually just end up hitting the power button while on a call which turns off the screen and it wont come back on until you manually turn it back on.
on a side note I used to have a cheap nokia windows phone that was inexpensive enough they did without the proximity sensor.
Instead they had it so when a large enough area of the screen was touched it would turn off.
single touches kept the screen on so you can still pull it away and mute or put it on speaker etc.
I kinda wish more companies would do that instead of the proximity sensor, but I think I'm in the minority as you are the only other person I've heard say they have that issue as well.
Ha, I'm not alone! Thanks for the tip, I will do some fooling around and see if maybe I'm holding at funny angle. I have been rooting since my first smartphone (HTC Evo 3d) for hotspot consequently. Seems even back then, especially on HTC phones the proximity sensor was a problem so I'm surprised I was clueless for as long as I was. That was a total bug tho. I would be talking to someone and open 4 apps and turn on airplane mode,take a screenshot, I even composed an email of gibberish and sent it to my son because the screen would not shut off Who knows, it was less than optimal. This is not a bug it seems either as you astutely pointed out I may be bringing it to my ear oddly enough to hit it before the sensor senses, ha. OR it is a hair slow. Who knows could be worse I could have a Samsung or Apple HA!

Categories

Resources