Anyone having the same problem? When I'm picking up the phone and pressing it against my ear to talk, sometimes it hits the mute button.
Ditto... I do it DAILY!
Oh my word, I hate that... I do it all the time. I wish there was a fix. My #1 issue with the phone
Yup same here! It happens daily, so much that I need to almost automatically check phone to make sure it isn't on mute before I answer or make calls. Hoping someone has some kind of fix.
EDIT: Just occurred to me that the proximity sensor is responsible for turn off screen before it hits your face precisely to avoid this problem. I looked at mine and the hole in my case to sensor was filled with dirt. I just cleaned it out and after 5 mins, it seems to be much better. Time will tell, but just wanted to pass it on
Related
Hi,
Every now and then, while my phone is in my pocket and I do receive a call, I pick it up to answer and the screen is totally unresponsive. I can't slide to answer or do anything at all. I tried to power it off and on again quickly, and then it seemed to get back to normal and I can answer the call. Most of the time this happened during incoming calls. Anybody noticed this behaviour as well?
I read in the HD2 Android forum that it was due to the light sensor. But I'm not sure.
Thanks,
-Gus
I'm experiencing the same issue...
Me too. anyone?
Same here. It happened on the Nexus one as well. Perhaps is a stock android issue.
I have created a bug report. Please help me by staring this report so that it gets Google's attention.
http://code.google.com/p/android/issues/detail?id=13853
Any update/fix on this issue yet? I'm having this problem on stock ICS, CM9 & AOKP as well.
I have this problem even without having the phone in my pocket, when I have it on the table and someone calls me, I have to wait for five seconds before answering, because before that the phone is irresponsive and it FC's, which rejects the call. It gets very annoying.
I've seen a lot of problems on the web about this. It might be the proximity/light sensor.
As a side note, have you cleaned the upper left corner of your screen (where the light sensor is located)? Or at least make sure nothing is actually over it (maybe a case or plastic, screen protector, etc).
Any update on code recently? Are you on stock ROMs or it happens on different custom ROMs/Kernels (good to test with several kernels instead)?
Some apps like AndroSensor or Phone Tester can give you insights about the proximity and light sensor. You might want to check it out and test this with a flashlight or something, and see if values change.
From the bug report, has someone actually tested comment 44 and 46?
Or tested this app DHD Proximity Sensor Recalibrator?
Some have even noticed missed connectors when phone was dissembled (this requires more effort).
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt
Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...
I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.
sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt
i get it too. but i dont call so much. so i dont really care lol
I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.
You might be holding the phone in a weird position?
THUNDERBOLT
Damn, you lean something new every day, this thing makes phone calls too!
I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.
pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...
i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.
No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk
I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.
After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.
I have never had an issue. Been on mostly whatever the latest bamf release since rooting.
It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.
I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App
this is the first I am hearing of this. No problems for me.
Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots
I've had 3 Nexus 5's so far due to one RMA and lastly because of a mistake on Google's part. But with all 3 Nexus 5's I have had two bugs that have been driving me nuts. I was curious to see how many people have had the same problems and if anyone knew of a fix. Bugs:
1) Keypad buttons being pressed while on a call. This happens almost every call. It seems that the screen is still active even if the proximity sensor turns off the screen. I haven't been able to reproduce it on purpose, but every single call I take I hear buttons being pressed. Sometimes it's like my notification bar get's pulled down, then the clock is clicked and I feel all these vibrations and ringing sounds and I look down at my phone and I'm in the date/time settings. This happens even if I don't have the dialer keys open. Weird.
2) Say I'm laying in bed and I answer a call. It seems as if there is some sort of setting for the accelerometer that if my head is tilted too much it's as if the microphone stops working... almost like the phone tries to switch to the second microphone (the one not normally used for phone calls). I can't tell you how many times I've been in bed and get a call from my wife (who works night shifts) calling to say goodnight and if I ever put my head back on my pillow she can't hear a word I say. As soon as I lean forward again she can hear me.
These are two problems that I have had with 3 different Nexus 5 phones. I've experienced the same problem with both Franco Kernel and the stock kernel. I don't know what else to do but it's driving me crazy. Anyone else seen these problems or know of a fix?
Thanks in advance.
Try turning your screen off during a phone call and see if there are still key presses being made. Depending how you hold the phone, the proximity sensor might switch the screen on during your call and could register key presses from your ear. The sensor is on the right side of the phone and will "miss" your head if it's behind it.
Unless you're leaving the digitizer enabled (tap2wake etc.) it shouldn't happen.
The mic issue while lying down seems to be common. Your head/pillow blocks the sound and noise cancelation wigs out. You could alter the way you hold the phone while lying down so the secondary mic at the top sticks out more. Personally, I just sit up and haven't had an issue with the noise cancelation since.
Sent from my Nexus 5 using Tapatalk
In many situations found my self in trouble.
The screen is unlocking while in conversation because of a notification and got the hang up touched. The worse is I end up speaking with another person because it was calling over (call waiting) and touched with my ear and accepted immediately. This very annoying.
On Galaxy note if I was locking the screen manually never got this problem.
I did search a lot and didn't find any solution.
Really?
piratugsm said:
In many situations found my self in trouble.
The screen is unlocking while in conversation because of a notification and got the hang up touched. The worse is I end up speaking with another person because it was calling over (call waiting) and touched with my ear and accepted immediately. This very annoying.
On Galaxy note if I was locking the screen manually never got this problem.
I did search a lot and didn't find any solution.
Click to expand...
Click to collapse
Proximity sensor issue?
Don't seem to be the sensor. If I'm engaging a call and I pass over with my hand the screen goes off instantly. Quite fast and from 1 cm away from the screen, not necessarily to touch the phone on the proximity sensor area.
Hi all users,
Can someone confirm if this is a real device issue or only my device
Purchased nato-straps which has the strap under the watch and cover the sensor and also lift up the watch a bit from the skin.
Had the nato-strap some days now and it was working fine. Notifications was vibrating and phone calls had sound.
Yesterday vibrations and sound during phone calls just didn't work anymore. Happened midday out of nowhere.
Now, if i put back a different strap, which don't cover the sensor, all works perfectly.
Can som please tell me what is happening here? I can't be the only one who has noticed this. Does the watch think its not worn because of the minor liftup caused by the strap under the watch?
Feel the wear overrides this and make it work with all straps. But I really want it to work..... Just as.... Before?!
Any ideas, suggestions why this is happening would be very very helpful.
/Best regards
DuoPad said:
Hi all users,
Can someone confirm if this is a real device issue or only my device
Purchased nato-straps which has the strap under the watch and cover the sensor and also lift up the watch a bit from the skin.
Had the nato-strap some days now and it was working fine. Notifications was vibrating and phone calls had sound.
Yesterday vibrations and sound during phone calls just didn't work anymore. Happened midday out of nowhere.
Now, if i put back a different strap, which don't cover the sensor, all works perfectly.
Can som please tell me what is happening here? I can't be the only one who has noticed this. Does the watch think its not worn because of the minor liftup caused by the strap under the watch?
Feel the wear overrides this and make it work with all straps. But I really want it to work..... Just as.... Before?!
Any ideas, suggestions why this is happening would be very very helpful.
/Best regards
Click to expand...
Click to collapse
Your watch most definitely thinks it is not being worn. The strap is not a "minor liftup". It will completely block the sensors not to mention making charging a complete PITA. Go to Settings --> Apps and Notifications and see if "Do not disturb when off wrist" is turned on. If so then turn it off.
My watch auto locks whenever it comes off my wrist since I have Pay setup and that requires locking. IMO the kind of strap that runs under the watch is a non-starter for this watch. It also renders the HRM useless too.
Thanks so much for the update. I think you made my day just so much better! It was turned on!?
Yes, i quickly realized that these are PITA =)
Will try if this helps.
Edit1
It worked to disable. Thanks again. You saved an angry phone call for Huawei support =)
DuoPad said:
Thanks so much for the update. I think you made my day just so much better! It was turned on!?
Yes, i quickly realized that these are PITA =)
Will try if this helps.
Edit1
It worked to disable. Thanks again. You saved an angry phone call for Huawei support =)
Click to expand...
Click to collapse
Why an angry call to Huwaei support? You are clearly covering all the sensors. The watch thinks it's off your wrist and what about the heart rate monitor? Why even dream of covering that?
Ok.
Humor. A joke. In the end I would have had to contact support since I didn't realize there was a sensor. Now I know.
Don't care about heart rate. I use garmin for serious running. All running apps can't match up a real Garmin with all of the features (intervall training etc). Yes i use two watches while running (4g version)