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).
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
Hi all,
I bought an infuse last week for a family member and loaded cm7 on it without any issues.
Starting today, when the infuse is placed on a phone call no one can hear me but I can hear them.
I've checked the sim card for scratches and it looks perfectly fine.
After troubleshooting it a few more times, what I noticed is as soon as the screen goes black during a phone call the mic is muted, so I have to consistently light the screen back up for the person on the other end to hear me. This also happens when I use the sensor and place the phone next to my face, it will also mute me. I've made sure that I'm not accidentally hitting the mute button, but it's strange that the mic cuts out as soon as the screen goes black.
Does anyone have any fixes or inputs on this matter?
I have an infuse for myself as well, with the exact settings, modem, and rom and mine is working just fine.
The phone hasn't been dropped or anything.
I've browsed around and people have been suggesting to "uncheck background noise" setting, but I can't seem to find it. I tried pressing the menu button while on a call and there is nothing. Am I doing this wrong or is the setting nonexistent in cm7?
Thanks
chaosdmonik said:
Hi all,
I bought an infuse last week for a family member and loaded cm7 on it without any issues.
Starting today, when the infuse is placed on a phone call no one can hear me but I can hear them.
I've checked the sim card for scratches and it looks perfectly fine.
After troubleshooting it a few more times, what I noticed is as soon as the screen goes black during a phone call the mic is muted, so I have to consistently light the screen back up for the person on the other end to hear me. This also happens when I use the sensor and place the phone next to my face, it will also mute me. I've made sure that I'm not accidentally hitting the mute button, but it's strange that the mic cuts out as soon as the screen goes black.
Does anyone have any fixes or inputs on this matter?
I have an infuse for myself as well, with the exact settings, modem, and rom and mine is working just fine.
The phone hasn't been dropped or anything.
I've browsed around and people have been suggesting to "uncheck background noise" setting, but I can't seem to find it. I tried pressing the menu button while on a call and there is nothing. Am I doing this wrong or is the setting nonexistent in cm7?
Thanks
Click to expand...
Click to collapse
Might i suggest to try another ROM? =/ I dont really know much about cm7, still its not expected to work perfect since theres not a real build for our devices only unnofficial compilations.
Or try all the compilations available for instance i can post this 2 threads that you can find on android development section:
LinuxBozo build:
http://forum.xda-developers.com/showthread.php?t=1195525
uberamd build:
http://forum.xda-developers.com/showthread.php?t=1311960
If both have the same problem i guess using a smsung based rom would be the next step, theres a rom and rom port galore at our forum so you wont be short on options
Nope, the noise cancellation setting is not available in CM7. You would have to go back to a 'stock' based ROM to get that setting.
Thanks for the info guys. Unfortunately, it didn't work. I went ahead and exchanged for another one since I am within my 30 days.
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
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