When I'm making a call with my Samsung Galaxy S I9000, the proximity sensor seems a bit... well... unefficient.
Usually, if I need to do something with both hands, like going through papers or using a computer during a call, I put the phone between my ear and my shoulder to hold it. Usually when held like this, the phone isn't entirely pushed against my ear/cheek, so the proximity/light sensor reacts to pretty much everything. When it reacts, the screen is turned on and my cheek sometimes pushes the mute(or speaker or end call) icon, and that gets really frustrating as it happens multiple times during a call, and you can't really notice it.
So you may imagine how it's like to keep on jabberin about something and then you hear your friend going "Hello? You still there? " and then you just go "****, AGAIN!?".
I was simply wondering if anyone has had this problem and if there is a fix for it. I have been looking all over the web for an app or a mod to disable the proximity during the call, so that the screen would simply go off only if you press the screen lock button. Or so that the screen would at first use the proximity sensor and then disable itself, so that the screen would go on only if you press the lock or home key.
I have been thinking about trying to solve this problem with creating an app through the SDK, but I still kind of lack the knowledge of creating such things (with being busy studying and stuff).
So, if anyone knows an app already or has found a way to solve this problem, I'd be greatful of your advice.
I have the same problem with the proximity sensor on my Samsung Focus.
Probably there are work arounds for this issue - but IMHO the proximity sensor is too sensitive and phone call UI is not very well design (end call button should be at the bottom of the page opposed to the top where it's not and is very easy to press it accidentaly with our ears/cheeks/etc.)
Since Samsung isn't fixing this, why don't you try Sanity app from market. It has many options along with the option to switch off the screen during the call.
Give it s try.
Sent from my GT-I9000 using XDA App
I have this problem since th beginning, with my FOcus. Any luck fixing this? I did increase the count to 75 through the Diagnose mode. But I still constantly find my phone on hold or on speaker or on mute while on call. Please help!!!
Related
Often i have to press to or maybe three times on some buttons before the phone recognise it as a press. Especially when i press the end call button.
It seems like the phone has some problems with touch sensitivty.
Anyone else have this problem?
Nope, mine seems good.
I do have the CM induced right edge of the screen issue though.
The problem with end call
Hi Fenrisulven_,
To me, the bug with the end call button is experienced because of the screen off feature on call... When you want to end call, you take it down from your ear, but it takes just a little more time for the touch interface to go on than the screen to switch on.
If anything the touch sensitivity seems maybe a little too high to me
I find the lock screen gets a little 'sticky' though.
Hey guys,
Im on CM7 and alot of the time when I have an incoming call and pull the phone out of my pocket I sometimes by accident press the back capacitive button and then drop the call.
Anyhow I can disable this feature / all capacitive buttons during incoming call? It should be only like a slide button to drop the call.
Using stock CM7 ADW Launcher
Thanks
Turn your phone so that the screen faces your body. This also protects your screen much better, as it's not exposed to impact. Battery cover is cheaper than screen/screen glass.
I also have this problem, and it really annoys me.
And it's not because of the orientation of the screen: I always put it turned to the body, but my leg can also act on the capacitive screen, and keeps cancelling calls...
Please, anyone have or know of an app/settings/script to disable "back button cancels call"?
..in cm it´s possible to code this as an option, so you could ask your maintainer, or in cm forum for that.
Thanks for the help, hopefully the devs will fix this
Sent from my Optimus 2X using Tapatalk
The devs will do nothing, they not known your idea.
Tell them.
Hi all,
I've come across a couple of problems with the phone that I've put down to manufacturing, but I'm not really seeing anyone else complain about them. I'd just like to see if anyone else is experiencing these issues or if I should have my phone replaced under warranty.
Issue 1: Microphone.
During a call, people can hear me clearly, but if I switch to speakerphone (or use an app like Skype or Viber, which usesspeakerphone for video calls), they have trouble hearing me. I know there is an issue where the mic stops working for some people, but mine is still working...only I sound very faint to the other person. If I bring my face right up to the phone and speak, they can hear me somewhat clearly, but it defeats the purpose holding it to my face when I'm in a video call.
Issue 2: Screen touches during a call.
I've noticed that when in a regular call, the screen turns off when I bring the phone to my face, and turns back on as I pull the phone away, which is fine. The problem is though, that while the screen is off and pressed to my ear, shortly after the light of the screen turns back on and it seems I've been pressing things with my ear, e.g. pulled down the notification shade, opened an app on my home screen or opened my app drawer, etc. Is anyone else noticing the screen turning back on mid-call? Or does anyone know if the screen still responds to touches even though the backlighting is off? Or is this an iPhone 4-esque situation where I'm "holding it wrong"?
Thanks guys
I take it the lack of responses means that no one else is experiencing the issue and that I should swap it under Warranty :/
ronnie301184 said:
I take it the lack of responses means that no one else is experiencing the issue and that I should swap it under Warranty :/
Click to expand...
Click to collapse
nope. my speakerphone works great, everyone hears me very clearly. and during calls, when my screen goes off, the screen is actually off and my ear doesnt register touches. and yea, id rma it.
ronnie301184 said:
Hi all,
I've come across a couple of problems with the phone that I've put down to manufacturing, but I'm not really seeing anyone else complain about them. I'd just like to see if anyone else is experiencing these issues or if I should have my phone replaced under warranty.
Issue 1: Microphone.
During a call, people can hear me clearly, but if I switch to speakerphone (or use an app like Skype or Viber, which usesspeakerphone for video calls), they have trouble hearing me. I know there is an issue where the mic stops working for some people, but mine is still working...only I sound very faint to the other person. If I bring my face right up to the phone and speak, they can hear me somewhat clearly, but it defeats the purpose holding it to my face when I'm in a video call.
Issue 2: Screen touches during a call.
I've noticed that when in a regular call, the screen turns off when I bring the phone to my face, and turns back on as I pull the phone away, which is fine. The problem is though, that while the screen is off and pressed to my ear, shortly after the light of the screen turns back on and it seems I've been pressing things with my ear, e.g. pulled down the notification shade, opened an app on my home screen or opened my app drawer, etc. Is anyone else noticing the screen turning back on mid-call? Or does anyone know if the screen still responds to touches even though the backlighting is off? Or is this an iPhone 4-esque situation where I'm "holding it wrong"?
Thanks guys
Click to expand...
Click to collapse
Never faced any of such issues with my nexus. You should go for a replacement
when i answer or send a call and put my stock Gnote3 to my ear, the screen doesn't turn off. then my ear plays with the screen, touching buttons and sometimes hangs up on the caller. anyone know what i can do to fix this?
thanks in advance
Settings > Device > Call then make sure Turn off screen during calls is checked.
thanks for the reply...where's the Thanks button?
it was checked, so i unchecked it and rebooted phone. then went and re-checked it. it still won't always turn off when i put it to my ear
I seen this thread, Proximity sensor issue and solution http://forum.xda-developers.com/showthread.php?t=2568003
looks like i need to be rooted for that thread to work for me.?.
Yes
Blow on the speaker above the Samsung logo. The proximity sensor is under the shiny metal part. There might be dust blocking it. Hope that helps
Sent from my SM-N9005 using Tapatalk
My note is about 16 months old now and this is just the norm now. I have blown through the speaker with canned air, it fixes it for a day or too. Then the proximity sensor gets blocked and does it again. It just gets worse and worse I don't even bother anymore. I just turn it off with the power button when I am talking.
just tried the canned air, hope it helps! thanks fellas
I use the phone a lot handsfree for work and it bugs me when the screen times out and locks on a handsfree call. I can't then easily mute, unmute, look at call durations, enter digits etc. without interacting with the phone in a clunky manner.
As an example i might be on a long conference call on speakerphone, mute my audio input to get up and walk around a little and then have to quickly unmute. To do this i have to press the side volume button and then the on screen unmute which sounds easy but can make for an awkward second or so of silence.
Basically i want the screen to stay on when in call and the proximity sensor detects it's not against my face.
Samsung has a phone app option for this i remember (keep screen on during calls).
Any suggestions ?
orbital247 said:
Any suggestions ?
Click to expand...
Click to collapse
Use a bluetooth earpiece/headset and add that as a trusted device. All the time it is on and connected the phone won't lock. Then just set screen sleep to something more appropriate like 5 minutes..
you could try something like this:
https://play.google.com/store/apps/details?id=com.ndtsoft.sensor&hl=en
i haven't tried it, but i think it could solve your problem
EDIT: i just tried an app called "WaveUP" and it did the trick. also has a lot of other cool features, as well.