When I put the phone up to my face, the stock in-call screen's speakerphone button is evidently in the same exact spot as my protruding cheekbones. Almost every I answer the phone, as soon as the phone goes up to my face it flips to speakerphone right before the proximity sensor switches off the screen.
I guess I could learn to place the phone to my ear first then lay it over the rest of my face. But I was just wondering is there a replacement for the stock in call screen where the speakerphone button wouldn't be right on my face?
Yes, i realize this is a dumb thread.
If you root, you can install GravityBox for MM, and use the option in there called "Use Proximity Sensor" to decide if the screen needs to be woken up or not.
Could do nothing, or could fix your issue as it's another sensor coming into play. You can't switch to speakerphone if the screen is off, no matter how bony your cheeks are
Related
I'm having trouble with the proximity sensor on my HD2. It works if the phone is pressed up directly on my ear, but if I move it away just the slightest, the screen comes back. Is there somewhere I can access the proximity sensor settings, and give myself a bit more room? Like, say, anything inside an inch shuts off the screen?
ROM info is in the sig, and I'm using the HTC phone dialer, if that makes any difference.
http://forum.xda-developers.com/showthread.php?t=624206
Aw balls, I hate it when there's a thread for this, and my impatience with searching failed to find it.
Thanks!
Doesn't sound like that app does anything for the sensitivity, unless i missed it. it just makes the screen stay off after the sensor is activated.
However the point of the proximity sensor is to shut off the screen so your ear isn't pressing buttons. If you've got the phone far enough away from your ear to reactivate the screen, then there's no longer a need to turn off the screen to prevent ear dialing.
If you're worried about power savings, the screen should shutoff in a minute or so, depending on your screen timeout options
d0ug said:
Doesn't sound like that app does anything for the sensitivity, unless i missed it. it just makes the screen stay off after the sensor is activated.
However the point of the proximity sensor is to shut off the screen so your ear isn't pressing buttons. If you've got the phone far enough away from your ear to reactivate the screen, then there's no longer a need to turn off the screen to prevent ear dialing.
If you're worried about power savings, the screen should shutoff in a minute or so, depending on your screen timeout options
Click to expand...
Click to collapse
correct, I haven't found a way to change the sensitivity for it, just turn it on or off. I believe the way the sensor works like a motion sensor in a store, either you are there or not... Hardware driven on sensitivity, not software.
Nibbley15 said:
correct, I haven't found a way to change the sensitivity for it, just turn it on or off. I believe the way the sensor works like a motion sensor in a store, either you are there or not... Hardware driven on sensitivity, not software.
Click to expand...
Click to collapse
I actually posted about the sensor in another post. The sensor is just an IR LED and a photo diode. The photo diode looks for the reflected IR when the phone is near something like your ear.
The IR LED only turns on during a phone call. Try this get a digital camera with a live preview and aim it at the 2 dots where the proximity sensor is, you'll see the IR LED light up when you initiate a call
The same photo diode is used to alter the screen brightness depending on the ambient light that hits it
im running full stock everything for starters.
When i am in a call sometimes up to my ear or speakerphone the screen will go black and i wave my hand in front of the light sensor and nothing works. The screen stays black. I like having the lock button hang the phone up so i want to keep that option on...
Just wondering why it is doing this, thx.
Its a thing to save battery usage,
do you have a case on it?
from my experimentation, the sensor is somewhere at the top, left of the power button when the phone is facing you.
prehaps your hand, hair, or case is covering it causing it to turn off - as it should
it thinks your in a call and you dont need to look at the screen.
Well, I've searched the forums for this phone and I haven't found anyone with this issue.
When I make or receive calls, the proximity sensor either doesn't turn off the screen or, more often, it does but turns it back on after a while. This results in random keys being pressed making noise and, eventually, it presses the button to end the call or puts the call on hold and dials another number.
It's very, very annoying. Could it be something on the settings? Hope it's not hardware... Any sugestions on how to solve this?
I'm using Miui 1.9.9 with franco.kernel from 10 set.
The proximity sensor is located at the top left corner of the phone (next to the speaker) and flashes red while active. Make sure you cover this area with your head when speaking. I am left handed and sometimes the sensor doesn't detect anything because of the way I hold it, this could be the case with you also...
There are some apps that can help you test the sensor if it works or not.
Mine was stupid too with stock rom, but with custom roms it works very good. detects even finger in 3cm range and turns on screen after 2 seconds.
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.
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**