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).
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
Hey!
The Issue: During a phone call the screen turns dark and will not reactivate...it will pop back up after the call disconnects. Hitting any of the site buttons does nothing.
I have tried flashing with the newest firmware (http://blog.geekbuying.com/index.ph...-firmware-released-0502-version/#.UtMOWM93vVI), and although it says this issue has been resolved, it does not fix the problem for me.
I heard that custom ROM fix the solution? (Saw it on this http://forum.xda-developers.com/showthread.php?t=1518663).
But last time I tried one of those, the phone bricked and it took me a while to get it back working (finding stock followed by lost IMEI).
Anyone know a solution? Or possibly a good solid custom ROM that will work? I would really appreciate your help!
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
alrightiwill said:
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
Click to expand...
Click to collapse
Hey! Not sure if this be of any help, but for me removing the screen (plastic) cover fixed the issue. I assume the screen cover was blocking a sensor thus resulting in my issues.
Just thought I let you know what worked for me...although I doubt your issue can be solved like this.
BTW, I suggest you start a new post, as this one is old and I doubt anyone will read it! also, check out geekbuying.com blog in regards to your phone. They might have more info.
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Bump for help please.
We are in the same boat
detailedvenom said:
I've been digging as much as I can on this issue, and so far I haven't been able to find any official acknowledgement or diagnosis of this issue. Please forgive me if this has been discussed before, but I simply cannot find the thread.
So far, I have had 2 Nexus 5's. Both of them had the exact same issue. When I am on a call, occasionally the volume from the other side will drop to a level where I cannot hear it. This happens most often when I am listening through the earpiece, thought it has happened while using speakerphone and multiple bluetooth headsets (plus my car). There doesn't seem to be a specific thing that triggers the issue, the area or type of phone I am calling doesn't seem to matter.
The phone is stock, I've never messed with the OS and the only apps I've downloaded were basic free ones, too many to list but if an app could be causing it I can post a list.
So far, I've tried the following to resolve the issue.
1. Factory reset both phones
2. Change sim card
3. Contacted my wireless provider (AT&T)
4. Contacted LG
5. Contacted google
Changing phones didn't help, Factory reset seemed to fix the problem for a bit but it came back. Changing sim did nothing. AT&T told me that because the device was third party, it wouldn't work properly. (I don't believe that for a second) LG just wanted me to ship the phone to them. (Not an option as they will take 2 weeks to get it back to me) And google just gave me some basic troubleshooting tips that I had already tried.
I cannot RMA the phone, i bought it used off of Swappa. I do not want to pay LG for a repair as this is a software issue and it should be solvable on my own. (though I will send the phone to them if it comes to that)
Has anyone had this issue, or at least heard about it? The only possible explanation I've found is that there's a problem with the noise cancellation software, but no one seems to have any solutions other than send it to LG, which really isn't an option for me at this point.
Thanks a crap load in advance to anyone who can shed any light onto this.
Click to expand...
Click to collapse
I'm being searching a lot to find a solution to this problem, but no luck.
I am using a Nexus 5 from the past 15 days and have the same problem of low to no volume from the speaker (voice of the other party). I initially though that it happens when I am outdoors, but no, it happens indoors too; and this does not happen always, sometimes it is loud and clear sometimes it is not. So I suspect that this has got something to do with the software rather than the software.
Even I don't have an option to send it back to LG cause I bought this in a different country.
My phone is Stock OS, updated to 4.4.4, rooted has Xposed Framework on it.
I also modified the build.prop and set the persist.audio.fluence.voicecall from true to false, but even this did not help.
Please, please, please, if anyone has found a solution to his please let us know.
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
IINexusII said:
If you press the back of the phone slightly, does it lower the sound? when i do not apply pressure to any back part of the phone, the sound is clear. with even slight pressure the sound dims on the other side. just noticed this today after trying to troubleshoot the problem. really bad design
Click to expand...
Click to collapse
So far I haven't been able to try that. For some reason the phone has started behaving, though there are a few issues here and there. I'll try this out next time it happens and report back.
I have my phone paired to my Pioneer head unit and if it disconnects it will occasionally cause the Bluetooth to turn on and off continuously without warning or anyway to stop the cycle. The only way I found to resolve the issue was a factory reset. I just reset my phone yesterday and the same thing happened today when I tried to re-pair to it again after I left my car. As you can imagine, this is extremely annoying, I am hoping someone can provide some insight on a possible fix for this.
Blu Pure XL
Stock ROM
Android Lollipop
SWV: BLU_P0010UU_V16_Generic_5.1_15-03-2016
I've experienced the same thing with my BLU Pure XL. It doesn't look like anyone has responded; likely because there isn't a fix and the phone is so substandard. Bluetooth is weak; signal strength is pathetic, cheap glass, lacks friendly ergonomics. I could go on. I've tried to submit issues through BLU website - no response. I won't give them another chance. Likely will buy the new Plus 1. Good luck and if you find a fix please post it here.
WilsonBridge said:
I've experienced the same thing with my BLU Pure XL. It doesn't look like anyone has responded; likely because there isn't a fix and the phone is so substandard. Bluetooth is weak; signal strength is pathetic, cheap glass, lacks friendly ergonomics. I could go on. I've tried to submit issues through BLU website - no response. I won't give them another chance. Likely will buy the new Plus 1. Good luck and if you find a fix please post it here.
Click to expand...
Click to collapse
So I noticed the Bluetooth issue only occurs for me when I am connected to a bluetooth device and a specific sequence of events occurs to cause it to happen. Specifically something like my vehicles aftermarket Pioneer radio where I can wipe the bluetooth memory of it (it has a 3 device limit). If, I wipe the bluetooth memory of my radio while my phone is connected, it will cause it to go into a loop and thus require a factory reset to resolve the issue. Since I discovered this, I have wiped the memory while the phone is disconnected and the issue does not occur. It has been quite sometime since I have originally posted here and I haven't had a problem since I have monitored it. Please let me know if this seems to be the same thing that occurred for you as well. Cheers