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] Oven QuickFix – Will it work for Nexus S?

Hello.
So it came. My Nexus S betrayed me. I started getting random "inabilities" to boot my phone. It was rather not booting than booting. The phone was booting like 1 out of 10 times (stuck at Google Logo). Suddenly I found out that applying pressure to the back of the phone (to the SIM card slot area) while pressing the power button solves the issue. At least temporarily.
The conclusion I came to is the following: Given this information (applying pressure) I came to the conclusion, that the soldered-on storage chip is not so soldered-on.
What about this: If oven-baking our laptops can repair them, is it possible to fix my Nexus as well? That is the question for you, guys! Will it take the heat? Can some components fall off the board when heated? Or get burn? If so, can I apply heat directly on that damn chip? That is the metaquestion!
Thanks in advance!

How can you fix a laptop by putting it in the oven dude ? Are you serious ? Ive never heard of that. Ever.
And i can't encourage you that this is a good idea cus it doesn't sound good.
Sent from my Nexus S using xda app-developers app

raducux said:
How can you fix a laptop by putting it in the oven dude?
Click to expand...
Click to collapse
Here you go.
https://www.google.com/search?q=laptop+oven+fix
And you're welcome eventually

I would rather use a proper heatgun and try to heat the place little bit while isolating rest of the "working" parts.
But honest advice, spare yourself the trouble of disasembling everything and start saving for new phone :/
Sent from my Nexus S using xda app-developers app

Awkward solution. Anyway i think that the device itself cant handle 385°…
Sent from my Nexus S using xda app-developers app

Ted Mosby said:
isolating rest of the "working" parts.
Click to expand...
Click to collapse
Maybe I could take aluminum tape and create rectangle around the chip, then heatgun the chip. That should work…

AW: [Q] Oven QuickFix – Will it work for Nexus S?
Oven quickfix does indeed work. I once repaired a HP nx7000 by disassambling the NB and put the motherboard into the oven. Worked like a charm afterwards.
Sent from my Nexus S using xda app-developers app

schurl85 said:
Oven quickfix does indeed work.
Click to expand...
Click to collapse
I found out that my coleague has a heatgun and his friend even has a machine for this (reballing stuff I would guess).
It is, however, good to know, that I'm not lost once I find out I'm out of RMA period. I *THINK* my phone does does have a valid warranty BUT I'm not quite sure I can find my papers and get to the store soon enough. It's indeed good to have a backup…

Go for the heatgun if possible. A lot of the parts on phone are extremely heat sensitive unlike larger hardware and you would likely end up damaging something else rather than just fixing the storage. Have put back to life quite a few devices using a heatgun and proper shielding, mainly xbox 360, video cards and other random peripherals.
Still would save for a new phone though, because it's likely it might die completely on you in the close future.

Inline headphone controls and black out

Where to start...
Basically I have 2 problems. Firstly. After getting a call that lasts (it seems about 5 or more minutes) the screen goes black. Nothing but a battery pull solves the problem. Yesterday I discovered the proximety sensor was a notable issue amongst users of the desire. I had a screen protector on. And where the sensor was it was scuffed. So I took it to my mates computer shop and he put on a new screen cover yet the problem still persists.. 1st problem.
2nd problem. All of a sudden my remote on stock headphones have stopped working. Can't skip tracks. Can't play from middle button and can't pick up calls via hands free. They are working sound wise. But like I said. No function with the remote.
I was thinking maybe an app is overriding the functions.
So last night. (i have a rooted s-off hboot phone) I reflashed satalite Rosie final version. And re partitioned the he card. (totally clean phone) still no remote function and black out still occuring.
This morning I think. Well running a sense 3.5 Rom on a a8181 might be the problem.. (even though it has worked before) so I flash qurpra v6 final edition.. same problem.. Not.liking some of the features of that Rom. Including battery notification fail. I reflash satalite Rosie.
I'm still in the same position I started.
Id like to add... No damage to the phone at all. It's pristine. Same goes for the headset. It worked fine (headset a few days ago) I just don't get it Tbh....
Thanks in advance for any help given
Sent from my HTC Desire using xda premium

Oh well. New headphones off eBay and the remote works so must be damaged.
New screen protector cleaned near proximity sensor and that's that sorted.
Just thought I'd add this because there are lots of people with the same problems. So Google says anyway.
Just thought I'd post possible solutions.
Sent from my HTC Desire using xda premium

Water damage

Soooo I'm in a super jam. Got water on my device.....had it in rice overnight....powered on fine...can see water damage behind screen but the touch screen works....my loudspeaker is shorted out, puts out super low volume. My WiFi works and my Bluetooth works but no cell service. I found the replacement speaker online for like $10 so that's fine....how do I go about repairing the cell radio? I didn't see that part anywhere. Is it part of a larger module?
Any insight is super helpful. Thanks guys!
Sent from my Nexus 7 using XDA Free mobile app

Before you do anything drastic, I'd verify its the not the sim card destroyed. I wet my device once and two days later all was fine except no reception and it turned out to be the sim card was corroded. You can also try cleaning the damaged sim card in alcohol but that's a last resort method.

I put the Sim card in my nexus 7 and it registered on network. Couldn't load any webpages or videos but it showed me as having "H full bars"
Sent from my Nexus 7 using XDA Free mobile app

briandresstoyota said:
I put the Sim card in my nexus 7 and it registered on network. Couldn't load any webpages or videos but it showed me as having "H full bars"
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It could still be the card at that point. I would still get a new one because you would need it either way. Worst case you paid 10$ for something you're going to need anyway. (If the damage was that deep it no doubt must have hit the sim card) its better to explore the cheapest option right off the bat before going in to repairs that mess with the inside of the phone.

Well I need to replace the speaker anyway
Sent from my Nexus 7 using XDA Free mobile app

So I'm actually posting from the damaged device. Turned it on today and the speaker is working. My WiFi is working as well as my GPS module. Camera and flash are both working. I guess I need to just try a new Sim card. There is definitely water marks behind the screen..anyone have any ideas on how to clear that up?
Sent from my Nexus 5 using XDA Free mobile app

My mic works too. Just tried it with a voice search. The vibrator motor seems to go in and out
Sent from my Nexus 5 using XDA Free mobile app

I actually just now had signal for a few seconds. No data but had bars. I intermittently have the display changing from "no service" to "emergency calls only"
Sent from my Nexus 5 using XDA Free mobile app

Anyone have any thoughts as to what would cause the intermittent signal? Is it a sim reader failure? and antenna failure? Something that can be repaired?

My USB connectivity came back!!! Can go through all my files and adb connectivity is functional. Anyone know if there is a diagnostic that I can run to find out what parts have failed? I'd like to just have to replace my antenna if that's all I need
Sent from my Nexus 5 using XDA Free mobile app

Um... I replied to the other same thread basically that you opened. ?

KJ said:
Um... I replied to the other same thread basically that you opened. ?
Click to expand...
Click to collapse
yeah this thread as you can see is kinda dead. im like the only poster almost so i opened another thread asking for something different. if the mods want to consolidate the two thats ok by me. Sorry for clogging up the forum, just dying for some assistance from the great minds of our community

You're wasting your time in my opinion. 99.999 percent of the time... If something doesn't work after water got to it.... It's fried. Would be a gigantic coincidence that something went weird the exact same time. ?

KJ said:
You're wasting your time in my opinion. 99.999 percent of the time... If something doesn't work after water got to it.... It's fried. Would be a gigantic coincidence that something went weird the exact same time. ?
Click to expand...
Click to collapse
ok well it was not completely sumberged.
the antenna cable is a separate module in the device
If everything else is working perfectly it would be very hard for me( a EE trained person) to assume that the motherboard is "fried"
im not even suggesting that something "went weird". LOL i am suggesting that possibly the antenna got water damage while the rest of the device survived. I am curious whether there is a diagnostic software that will let me know what hardware pieces are damaged. As it is right now i dont have a multimeter or i could just open the sucker up and resistance check everything LMAO

The radios toast. Just because everything else works doesn't mean the radio survived. Had the same issues with my wifes phone. She gave it a tea bath. I took it apart, cleaned it with electrical cleaner, dried it in rice for three days. Put it back together and everything worked great. Except the radio. Sold it for parts and moved on.

GPS 100% broken?

I recently changed the housing on my M8 to red and have been using the phone perfectly until I recently tried to use GPS and found it non functional. I have tried flashing sense roms which have always gotten a GPS lock right away no matter which version I was using at the time. I am running the latest Lollipop firmware and currently am on bliss CM12, however no matter what rom I try I always end up with no lock and no signal change when looking at GPS status or other application. Is the GPS module on this phone plugged in or physically attached to one of the main/daughter boards? It almost seems like either the new body is interfering or the GPS is unplugged(if that is possible). Any help here would be greatly appreciated as the only other thing I know to try is to purchase replacement speaker grills and try swapping back to the original housing.

Have a look at this thread. It may the answer for you.
http://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Sent from my HTC6525LVW using Tapatalk

That you SO MUCH, that sounds highly likely due to the tightness of the rear housing.

FIXED!!!! I can't thank you enough for that link. I found the "pin" broken off(sorta? it looks like it is held by placement rather than solder) ended up soldering a very short piece of wire to the small pad on the board so that it touches the case when closed. Booted up and GPS Status locked 12 Satellites immediately