Database Info

[Q] Tbolt Proximity sensor

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

[Q] Are these problems with cyanogen mod or the actual phone itself?

I'm pretty sure this is a hardware problem but I just want to make sure. I have an HTC Sensation 4G for T-Mobile (using Family Mobile) with Cyanogen Mod 10 installed. The problems I'm having are related to the touch screen. First of all, moving icons is really hard because it's like it doesn't detect that I'm still holding the icon. Thus, if I have an icon on the homescreen that I don't want, I usually have to first drag it up one row, then again and again until I get to the top to remove it. It also sometimes launches the app instead of moving it which is really annoying. The next problem is very similar to this one: whenever I'm scrolling through something (like contacts or a webpage, for example) the scrolling is kinda choppy and it sometimes takes a few swipes for it to actually scroll. It also sometimes opens links or the contact or whatever when I just want to scroll. Finally, long pressing is not reliable at all, it usually just considers it to be a tap. I literally spent like 1 minute yesterday just trying to open a link in a new tab before just giving up.
Oh yeah, I'm also experiencing trouble with the keyboard. Certain keys like "t" "c" and "f" are really hard to press. Whenever I try to type those keys in particular, it chooses the two keys on the sides instead (so if I type "f" it inserts "dg" or "gd" instead). I've installed a different keyboard which has kinda helped but it's still a problem because it slows down my typing to very slow speeds.
So basically, it looks like my screen is messed up, or I though maybe the processor is running too slowly to process the input or something like that. Looks like the screen though because I can sometimes identify "trouble spots" on the screen that cause the aforementioned behavior. Anyone else had problems like this before? I've heard that flashing the right radio can fix things like battery life and performance but I've never heard of something like this before. I bought the phone used on the internet so there's no way to get it repaired (besides paying for it of course, but that's not an option for me right now). The vibration also isn't working so I think it must have been dropped and that's why the vibration and screen are now messed up.

Ir0nMa1deN said:
I'm pretty sure this is a hardware problem but I just want to make sure. I have an HTC Sensation 4G for T-Mobile (using Family Mobile) with Cyanogen Mod 10 installed. The problems I'm having are related to the touch screen. First of all, moving icons is really hard because it's like it doesn't detect that I'm still holding the icon. Thus, if I have an icon on the homescreen that I don't want, I usually have to first drag it up one row, then again and again until I get to the top to remove it. It also sometimes launches the app instead of moving it which is really annoying. The next problem is very similar to this one: whenever I'm scrolling through something (like contacts or a webpage, for example) the scrolling is kinda choppy and it sometimes takes a few swipes for it to actually scroll. It also sometimes opens links or the contact or whatever when I just want to scroll. Finally, long pressing is not reliable at all, it usually just considers it to be a tap. I literally spent like 1 minute yesterday just trying to open a link in a new tab before just giving up.
Oh yeah, I'm also experiencing trouble with the keyboard. Certain keys like "t" "c" and "f" are really hard to press. Whenever I try to type those keys in particular, it chooses the two keys on the sides instead (so if I type "f" it inserts "dg" or "gd" instead). I've installed a different keyboard which has kinda helped but it's still a problem because it slows down my typing to very slow speeds.
So basically, it looks like my screen is messed up, or I though maybe the processor is running too slowly to process the input or something like that. Looks like the screen though because I can sometimes identify "trouble spots" on the screen that cause the aforementioned behavior. Anyone else had problems like this before? I've heard that flashing the right radio can fix things like battery life and performance but I've never heard of something like this before. I bought the phone used on the internet so there's no way to get it repaired (besides paying for it of course, but that's not an option for me right now). The vibration also isn't working so I think it must have been dropped and that's why the vibration and screen are now messed up.
Click to expand...
Click to collapse
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?

I've never used this rom so I'm not sure weather or not this is a rom issue or not. You can find out by posting this question on their rom site. I have however had similar issues with other roms and the problem was solved once I flashed a different rom. What you can do for testing purposes is download another rom and see if there problem still persists. If it does than you know it's your device. If the issue is gone then the problem would be with the rom itself. Just because no one else is experiencing the issue it does not necessarily mean it's the device. I was using a rom once And had a lot of crazy issues going on. On the rom website they said it must be my device however after I installed a new rom all my issues we're gone never to appear again. So everyone's device is different. Do some testing and that will answer your question. Try out a couple of other roms, if the issue is gone than it was the rom. If it's still present with the other roms then it's your device. Good luck and I wish you the best. Hope this is helpful.
Sent from my HTC Sensation using xda premium

malybru said:
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?
Click to expand...
Click to collapse
I'll try one today. I've held back from trying different ROMS because I don't want to screw everything up and be left without a phone for a few days. But now it's the weekend so I'll back everything up and try a sense rom.

malybru said:
Hi,
I found CM ROMS gave poor screen sensitivity .
Not as bad as you are describing,though.
Have you tried a Sense ROM?
Click to expand...
Click to collapse
I tried installing a sense rom but it didn't install correctly. I started the install and one second later it said it was done. When I rebooted it threw me back into Cyanogen Mod 10. Any ideas?

I have elegancia installed now, same problems. i'll be re-installing CM10 since it had some really nice features. I guess I'll just deal with it then.

The only possible solution i can think of is the ground pin.
Check this thread... and i hope it will help you..
http://forum.xda-developers.com/showthread.php?t=1239238
~HTC Sensation powered by Bricked AOKP milestone 6~

No phone audio after rooting and new ROM

So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!

Edit, sounds like a hardware problem.
Have you tried to odin back to stock?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?

jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.

dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.

dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4

And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.

I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.

[Q] CM11 proximity sensor problem

Problem: Phone rings - Taken to ear - screen goes dark - talking talking - hang up - look at screen - somethings have opened ( apps or settings or bluetooth or people etc.)
I had tried Sultan's and Albinoman's CM11 kitkat roms. Happening in both. It didn't happen on any sense based rom.
I am trying Hypernonsense ICS now, so far so good, no problem.
What would be the problem with that situation??

3harfli said:
Problem: Phone rings - Taken to ear - screen goes dark - talking talking - hang up - look at screen - somethings have opened ( apps or settings or bluetooth or people etc.)
I had tried Sultan's and Albinoman's CM11 kitkat roms. Happening in both. It didn't happen on any sense based rom.
I am trying Hypernonsense ICS now, so far so good, no problem.
What would be the problem with that situation??
Click to expand...
Click to collapse
Hardware issue. Happened to mine too. Replace flex cable.

ShadowCodeGaming said:
Hardware issue. Happened to mine too. Replace flex cable.
Click to expand...
Click to collapse
If it is hardware, how do I not see the problem with different softwares? It didnt happened on Vipers or stock rom.
Curious.

3harfli said:
If it is hardware, how do I not see the problem with different softwares? It didnt happened on Vipers or stock rom.
Curious.
Click to expand...
Click to collapse
It'll start happening there soon enough, trust me
Sent from my Sense 5 powered HTC Sensation

My experience was slightly different: proximity sensor was not working while making calls (turned black and not on uless pressig twice power button), but working fine with skype and viber.
once tried spraying a bit of wd40 as suggested in this thread http://forum.xda-developers.com/showthread.php?t=1559945&page=4 everything works fine!
Check if your sensor is working with other apps, maybe it's software related!!!

This is weird. The light and proximity sensors only work on mine if I restart the phone 'with the power cord inserted'. ?!?

Camera issue (not always)

I am having a problem with my camera.
Sometimes my pictures are divided in two, one side is darker then the other.
Here a normal picture:
and an other picture taken a few minutes later but with mentioned issue:
You can clearly see that the right side of the picture is darker than the left.
Already tried several Camera's, but they all give me this problem. I am using LineageOS 7.1.2.
Friend of my who has the same OPO and is running on Cyanogen 5.0 is having the same issue.
Wonder if there is some fix for this

seninnha said:
I am having a problem with my camera.
Sometimes my pictures are divided in two, one side is darker then the other.
Here a normal picture:
and an other picture taken a few minutes later but with mentioned issue:
You can clearly see that the right side of the picture is darker than the left.
Already tried several Camera's, but they all give me this problem. I am using LineageOS 7.1.2.
Friend of my who has the same OPO and is running on Cyanogen 5.0 is having the same issue.
Wonder if there is some fix for this
Click to expand...
Click to collapse
It's kernel and camera blobs related.Happens with me when I flash an incompatible kernel.Are you using stock kernel?

Yes...stock kernel...never used ,as far as I can remember , an other kernel

seninnha said:
Yes...stock kernel...never used ,as far as I can remember , an other kernel
Click to expand...
Click to collapse
What can I say,clean flash's the best get.

Already did this. Several times, but issue stays.. already having this phone for 3 years...and every time I used had this problem

seninnha said:
Already did this. Several times, but issue stays.. already having this phone for 3 years...and every time I used had this problem
Click to expand...
Click to collapse
Tried clean flashing through fastboot? AFAIK,this is purely a sw problem.

Awesome, i'm not the only one with this problem...
I thought my phone got damaged in a drop or something. Mine has always been and since half a year or something I sometimes get this from the phone rear camera.