Related
Hi all again,
I must saw I've NEVER had to do so many posting for a single phone... anyway.
I just updated my Leo to 1.61 via a tortuous goldcard process and the proximity sensor is still not working correctly My wife is the main user of the phone and I was watching her while on a call- the screen was on and off like some demented Xmas lights.
I have a theory regarding the problem. It's only my wife who has the problem with the phone, it's seems ok with me (but I don't use it as much!). The phone is very wide, and the proximity sensor is not central. I think that the sensor is missing her ear (she has small ears!). The gap between her ear lobe top and her head is too great for the sensor. I tested the sensor gap with my thumb and it seems to be around 1cm to activate.
The hardware solution is either move the sensor so it's central (that's not going to happen soon) OR increase the sensitivity of it.
Does anyone know how to change the sensitivity of the sensor OR anyway to completely disable the touch screen during a call.
Hmm I can not believe that, I've tested my sensor:
It put the lights out if i come closer that 1,5 cm next to the screen during a call. So it think this is not the source of your problem.
But: I'm running a 1.48 rom...
I had the proximity sensor behaving eratically upon installing a screen protector. Even though I installed the original HTC screen protector which has 2 holes to position exactly over the sensors but even then I had problems. Ever since removing the screen protector everything is okay again.
Just thought if your problem also coincides with installing a screen protector.
Regards
The problem occurs when your hair overlaps the proximity sensor, the light immediately comes on. Stick the phone back to the ear and the proximity sensor works perfectly on time.
p.s. ive long hair and I too faced this problem and figured it out by running a few test as mentioned above ;-)
Hope this helps.
well, I'm having the same problem and It's not caused because of my hair. it just sometimes works and sometimes doesn't. the test I make is using the palm of my hand. if during one call It's not working, it won't work no matter what you do. then if I make a call and its working, I can turn on and off the screen placing my hand in front of the sensor..
jpresencia said:
well, I'm having the same problem and It's not caused because of my hair. it just sometimes works and sometimes doesn't. the test I make is using the palm of my hand. if during one call It's not working, it won't work no matter what you do. then if I make a call and its working, I can turn on and off the screen placing my hand in front of the sensor..
Click to expand...
Click to collapse
I reckon you clear the area around the receiver and try doing a hard reset.
CAUTION: Take an individual back of your data rather than doing a full backup using some software.
same problem
Hi, I have the same random proximity sensor bug problem. During call accidental hang-up happens every day. I have short hair and no screen protector. Is there any solution for this yet? thanks.
I wrote to HTC already, but they claim there is no problem reported. Sory for my English.
Had a similar problem. My proximity sensor is now working fine. Install the 'Proximity Sensor for Screen Off v0.2' cab. Search the forum for the thread.
thanks for tip, hope this little app will "evolve"...
hi,
i had the problem with the proximite, that it is only working when the phone is in portrait mode. when im incall and portrait i can put my finger to the sensor and it is working perfect. when i rotate the display to landscape the sensor does nothing and the display stays on. unfortunatly i turn the phone sometimes on the way to my ear, and so the screen stays on.
i will try now the mentoined .cab and see what it does for me.
regards mad
I am having trouble with my screen turning off when making a call,it happens both in win-mo and also when using Android.
I am using 13th Dec NRG rom and the latest HD2ONE android rom.
As soon as I dial number and pess call the screen goes black and the only button to work then is the end call button,in android it will take a battery out reset or abouit half hour left alone before i can use the phone.
I have done a search but the only thread that comes up is the same prob as mine dating back to June with no deffinite answer.
Does anyone else have this problem,its strange how it happens both in Win-mo and Android I'm at my witts end as to try and solve it,it happens no matter what rom combination I use.
Thanks
Well the HD2 has a sensor near the top so that the screen will turn off when you bring it up to your face, and turn back on when you bring it down again. Perhaps your sensor is broken? Can you send it in for warrenty?
Thats the problem,it does the same even if I am holding it away from my face at arms length,I have disabled auto-brightness too,makes no difference.I have now seen many threads on this subject with lots having the same problem but it still seems there is no deff answer.
If it's in both WinMo and Android it's almost definitely a hardware issue. Maybe there's some dirt in front of your proximity sensor, try cleaning it. If not, return for warranty.
Not trying to sound like a troll here but is the sensor clean? I've had a similar issue before but after cleaning the corner of my screen(skin oils get all over it), it worked fine again.
Another thing to think about is this: Does the WinMo ROM you're using have Co0kie's Home Tab Mod V2.0? If it does, Is the proximity sensor option turned on? If it is then any time anything gets close to the corner of the screen, even a finger, the screen will turn back off.
Sometimes partial data's like this are carried over into Android when you boot.
Check to see if you have CHT and if you do, check to see if that option is enabled. If it is, disable it, clean your screen and see if this helps.
Hello guys,
at first i want to excuse for my language mistakes, it's not my native language.
I have a problem with my phone. If I make a phone call, the proximity sensor deactivates the screen, like it should be, but the screen won't wake up, after I push the phone away from my ear. It takes a long time, until I can see something again on the screen. I don't want to create a new thread where I am crying about this issue, I want to solve this problem.
I also searched at many other developer-forums and i noticed, that this happens to many people around there and everybody is crying about it.
Everybody who can provide informations, that can help to solve this problem is invited to share his experiences with us.
The HD2 is a very beautiful mobile phone, but this problem is really annoying.
I made a lot of tests to find the reason of this problem.
Things, that I did without getting clear results:
1. Dirty sensor
It could be possible, that the sensor or the glass plate is dirty inside and because of this, the sensor can't recognize it properly.
2. Light sensor
It was random, that I expected that this issue also depends on the light sensor. I made a call and the screen goes off, like every time. Now i take the flashlight and light it in the area of the proximity and light sensor. Instantly the screen went on and displayed everything, but if I move the flashlight away again, it goes off. and that happens as long as you make the call. If you end the call the screen stays off like it's everytime the case. If I move the flashlight now in front of the sensor area, the screen goes on and it stays on.
EDIT: It's not everytime working.
The following things I did, but brought no solution:
1. Flashing everything new
I did a task29, flashed some different radio roms, different HSPL's and also many different ROM's. Windows Mobile and ALSO Android. Nothing helps.
2. Blowing inside the case
I also read that it help if I blow inside the case near the area of the sensors. I don't know if it really helps, but it's fur sure not the reason.
3. Display protector
In my case it's not the reason, because I don't use a protector and never used one.
Questions, that I have now:
1. Proximity sensor
Everybody says the HTC HD2 has a proximity sensor, but I don't know if this is sure. Maybe the phone has only a light sensor, which works like a proximity sensor, like other newer phone's like the HTC Wildfire.
2. Production error
Could it be a failure from the factory? Encoutered anybody this problem only after some time? Or maybe anyone who can say that the problem was solved by itself?
Please don't answer like: use the forum search or something like this.
I searched a lot and not only in this forum.
Best regards Gerhard Silvio
Further test confirmed, what I said. The problem must be the light sensor. After a call and the phone don't turn on, light a fire in front of the phone or light with a flashlight to the sensors. it goes on immediately!
Strange..
EDIT:
I made a video to show what I mean. Excuse me for my bad english ^.^
Now you developers outside are asked how to fix it...
Open the phone and clean? Or maybe it's not so easy?
Best regards
There is no possibility to fix this issue, because the light sensor is not programmable (as we know now, the HD2 has no proximity sensor). The sensor decides to turn the screen off when it gets dark, so i took some black nail polish and put it under the glass surface in front of the sensor. The screen now don't turn off and automatic light won't work also, but i can compensate these problems better than the call issue.
And without doing this, you will never be able to use WP7 right, because you can only end a call if you push the on-screen button, and this button won't appear. So you must wait until the other side ends the call, and if this don't happen you can't use your phone again without remove and reinserting the battery ^^
I hope I could help you by providing these informations.
Thread can be closed, there's nothing more to say.
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
iamrv said:
The problem is isnst a problem 'cos you burned the proximity sensor with that heat.
Click to expand...
Click to collapse
What are you talking?
That has nothing to do with any heat (if you mean the lighter). It was 3cm or more, can't follow your answer, cause its unlogical. It also worked with a normal light or a laser or anything else.
the problem u have ( i have too) only happens in nand builds, i dont have this issue with Duttys_2.5_5.21916.5.0.95_3.14_HD2_ML_Family_ROM_(V12)_WWE installed.. the phone act normal completely.
so i have to say this to me is a nand build issue, why others on htc hd2 arent not having this problem is what confuses me
In my case, it was not depending of what build or os i use. It happened in wm6.5, sd android, nand android and also in wp7. I caused by the hardware, and if i can't repair it, i have to destroy or deactivate it. with software you can't deactivate the sensor so i coloured the sensor black, that he won't notice anything anymore and the problem is solved. i have no problem with the screen active, while calling.
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
The HD2 DOES have a proximity sensor but this fault does occur on some android builds
If it occurs for you everywhere, then u simply have a faulty proximity sensor, and i know this because i too have used wm.5, andoird nand and sd, and WP7
and the proximity sensor works fine on all but some (older) android builds
if the HD2 didn't have a proximity sensor there wouldn't be a second hole, next to the light sensor.
johncmolyneux said:
Firstly, the HD2 DOES have a proximity sensor and it works flawlessly in WM6.5. I know this was 100% fact for me, as I was very impressed at how well it worked. There are 2 sensors, clearly visible, next to the earpiece. One is a light sensor, as you know, and the other is a proximity sensor. This is not an opinion - it's a fact. I just wanted that to be very clear.
Also, I don't have this problem in Android, either SD builds (I don't use any more), or NAND builds (my daily driver). I will admit that there is a delay of a couple of seconds when I take the phone away from my ear, before the screen comes on, but I know that's just down to the fact that I'm using ported software.
You say that in your case this failed to work in both WM6.5 and Android. You've got a dodgy proximity sensor then. This is clearly a hardware failure.
Click to expand...
Click to collapse
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Maybe can help...
Sent from my HTC Desire using XDA App
My HD2 tmobile also has this proximity sensor problem. I use my finger to cover the sensors (light, proximity) during the call. The screen will off. But the screen cannot back to on when I moved out the sensor cover. I tried to use the torch to shine the sensor but no response.
If HD2 connected to power supply or PC USB for battery charging. The screen can switch on. I think this charging method for sensor disabled.
you already thought about a Hardware Problem and let HTC fix it?
yogya said:
Thanks for your opinion, but my proximity sensor works flawlessly in windows mobile 6.5.3 but under superram darkstone build I suffer rge same problem. Most of the times can be fixed touching the write arrow button...
Click to expand...
Click to collapse
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
johncmolyneux said:
Thanks, but that's clearly just an issue with the Android build you're using. Try another one and see if it's better.
Click to expand...
Click to collapse
Thanks for the info...
If I change my build I el let it know here... For the moment, I can survive with this...
Sent from my HTC Desire using XDA App
jackykwan said:
I tested my HD2 again. I restored WM6.5 to my HD2 tmobile. The proximity sensor was no problem. the screen can turn off when my face close to screen and my face is far to screen, the screen will turn on.
I also tested the lighting sensor. I put my HD2 under the strong sunshine, screen will light strongly.
If I re-installed the android rom NAND. This problem will be issue. I tried more than two ROMs. The result is same.
Sorry, maybe my english is not good.
Click to expand...
Click to collapse
then it can only be an issue with the nand builds unless the nand builds have use of an additional sensor not used in wm6.5..
Hi.
Readed all this thread. Also one other same situation, described on HD2 Android Q&A and General forum on thread "[Q] screen goes off if I make a phone call".
I can confirm that this issue goes active with Android NAND builds. Not matter, is it Froyo or Gingerbread. I tested lot different roms. Best results i got on PureGingerbread gpc_hd2_gingerbread_v1.3 and with SetCPU on conservative. On somewhere proposed smartass didnt work.
Actually i dont remember this same bug, when i runned Android at SD.
Now i placed back stock win rom and all works perfect. This shows that my hardware works correctly. But i dont like winmo (also winphone 7 is unripe and i dont like it too). I want use Android and not at SD. Must i go to change phone and loose todays best smartphone (my opinion)?
I dont know fundamental of Android and dont have time to learn it too (so many works and other things todo). But maybe some rom or kernel chief can handle this and overlook things that operate with Proximity or Light sensor.
I dont have so many posts yet that post this to my preferred rom thread. I dont want go spam over forum to get post count bigger. this was reason why i posted my opinions here.
Finally sorry about my poor enlish.
I heard so much meanings where the reason could be and i have to end up my whole life without solving this problem.
in my case it's not os-dependent.
i never needed my screen to turn off while talking, the hd2 is very big and with android there's nearly no chance to push any button and with wp7 the same, so why i should be angry about this problem. my sensor won't recognize anything anymore, that's enough for me ^^
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Silberpfeil3110 said:
http://forum.xda-developers.com/showthread.php?t=951858
This sounds very interesting. The proximity sensor of the Desire HD of most people was not correctly calibrated so it won't work good and they got the same issues like we do with our beloved HD2. Check out the thread and the app. I'm not sure if it works, but you can give it a try. I'm not able to use it, because i deactivated my sensor in a hardware-way xD !
Click to expand...
Click to collapse
Hello
I have this problem since 2 days
And i test it
now my phone not turn off during a call. screen stay on.
Just tips for people who might have the same issue as me.
Problem: When you are in a call, the proximity sensor turns off the screen but when you pull the phone away from your face the screen stays off.
Solution: In my case it was because there were dusts covering the proximity sensor which caused it to not be as sensitive as it should. I blew some compressed air thru the speaker (top) and everything works well.
Hope this helps, I was struggling with it for months thinking maybe a custom rom installation went haywire.
takuyaah said:
Just tips for people who might have the same issue as me.
Problem: When you are in a call, the proximity sensor turns off the screen but when you pull the phone away from your face the screen stays off.
Solution: In my case it was because there were dusts covering the proximity sensor which caused it to not be as sensitive as it should. I blew some compressed air thru the speaker (top) and everything works well.
Hope this helps, I was struggling with it for months thinking maybe a custom rom installation went haywire.
Click to expand...
Click to collapse
I have this problem too. I believe my proximity sensor is damaged. I have done a lot of reading out there and tried all solutions. This is very annoying when you want to turn on the speakerphone or use the keypad when calling #'s that require input. I tried using Pacman rom 4.2.2 and 4.4. I heard its possible to disable the proximity sensor during calls with stock Touchwiz rom, but I can't stand it. I may consider trying Goldeneye 4.4 TW Rom, but installation seems like a major hassle. I hope there is a custom rom out there that disables the proximity sensor.
Hello all, I know this issue has been raised before but there hasn't been a fix. I'm currently facing trouble putting my G2 in a waterproof ziploc bag because of the proximity sensor. It detects that something is in front of the phone and doesn't allow me to turn it on. I can't knock-knock to turn it on. The moment I turn it on using the back button the screen will time-out. This is a feature of the phone, not a defect. I want to know how to disable it. Please, if anyone knows how to do it, tell me! Your help will be much appreciated!
Edit: if you want to replicate the problem try putting your finger on top of the front camera - the phone will not turn on when knock-knock
Android App Disabler
I have found an app that may help, but I do not know how to use it! If anyone knows how please tell me!
https://play.google.com/store/apps/details?id=com.hatcyl.android.Hardware_Disabler&hl=en
Wierd, I just experienced what you are talking about by testing it out. If the phone is already on and being used and you cover the proximity sensor it doesn't turn off, but, if it is covered as you turn the phone on it will immediately turn itself back off. Even if you use the button and try to swipe the screen quickly it doesn't prevent the phone from turning off automatically.
Unfortunately, I am not able to help you with this problem as it is fay beyond my limited knowledge of linux/android etc. However, maybe this reply will cause someone who can help you with an easy solution.
One thing that would almost certainly fix it would be to switch to one of the alternatives rom not based on the stock LG software/kernel like Cynogen Mod or Android Open Source Project, etc. Those roms use a different kernel and also a standardized version of android that is open source. So the sensor problem will likely not be an issue, however, I believe you lose either knock on or knock off functionality with Cynogen Mod, not sure which one as I am still running LG based rom.
Some people prefer the open source alternatives to the LG rom, so, you might even like it better than the LG setup. However, it will require some effort/reading to learn how to root your phone. Then to flash your particular model of G2 with a custom recovery and then to install a rom/kernel. It is not that hard though, you just have to acquire the knowledge to avoid bricking your phone by doing something foolish.
DornoDiosMio said:
Wierd, I just experienced what you are talking about by testing it out. If the phone is already on and being used and you cover the proximity sensor it doesn't turn off, but, if it is covered as you turn the phone on it will immediately turn itself back off. Even if you use the button and try to swipe the screen quickly it doesn't prevent the phone from turning off automatically.
Unfortunately, I am not able to help you with this problem as it is fay beyond my limited knowledge of linux/android etc. However, maybe this reply will cause someone who can help you with an easy solution.
One thing that would almost certainly fix it would be to switch to one of the alternatives rom not based on the stock LG software/kernel like Cynogen Mod or Android Open Source Project, etc. Those roms use a different kernel and also a standardized version of android that is open source. So the sensor problem will likely not be an issue, however, I believe you lose either knock on or knock off functionality with Cynogen Mod, not sure which one as I am still running LG based rom.
Some people prefer the open source alternatives to the LG rom, so, you might even like it better than the LG setup. However, it will require some effort/reading to learn how to root your phone. Then to flash your particular model of G2 with a custom recovery and then to install a rom/kernel. It is not that hard though, you just have to acquire the knowledge to avoid bricking your phone by doing something foolish.
Click to expand...
Click to collapse
Thanks a lot for the tips but i think there should be a way to disable the proximity sensor on the stock rom. If all else fail then i will try and install custom rom like the ones you mentioned.
catfish90 said:
Thanks a lot for the tips but i think there should be a way to disable the proximity sensor on the stock rom. If all else fail then i will try and install custom rom like the ones you mentioned.
Click to expand...
Click to collapse
Yes, it would have been a nice feature for them to include, I wonder if they just overlooked it. That being said, I'm not sure if there is anyway to do it on the stock rom. Hopefully for you it will be possible in time. Good luck!
I can confirm that CM11 is not affected. I put it in a baggy and it will still respond to all input.
zero0422 said:
I can confirm that CM11 is not affected. I put it in a baggy and it will still respond to all input.
Click to expand...
Click to collapse
Really? That is good news! Sorry but im to custom roms - is aosp or paranoid android rom based on cm11? I believe those are one of the best custom roms for android. I might install one of them soon.
catfish90 said:
Really? That is good news! Sorry but im to custom roms - is aosp or paranoid android rom based on cm11? I believe those are one of the best custom roms for android. I might install one of them soon.
Click to expand...
Click to collapse
I think you meant AOKP? But either way, AOKP, PA, and CM are all AOSP based ROMs. Just different paths. PA has some really great features right now, but lacks a couple tiny things that keep me on CM11.
If you're looking for a no frills mostly stable ROM CM11 is probably the best choice, plus Delta updates make it pain free.
zero0422 said:
I think you meant AOKP? But either way, AOKP, PA, and CM are all AOSP based ROMs. Just different paths. PA has some really great features right now, but lacks a couple tiny things that keep me on CM11.
If you're looking for a no frills mostly stable ROM CM11 is probably the best choice, plus Delta updates make it pain free.
Click to expand...
Click to collapse
I heard that people are having random reboots on CM11 - is it true? What are Delta updates?
catfish90 said:
I heard that people are having random reboots on CM11 - is it true? What are Delta updates?
Click to expand...
Click to collapse
I get some here and there, nothing major. Delta updates take the nightly, and process it to pull only the changes, so you get about an 11mb update instead of a 150+ mb update. Its all in an app.
This rom solve the issue:
http://forum.xda-developers.com/showthread.php?t=2582845
Very nice ROM, works perfect, better then stock
fsi09 said:
This rom solve the issue:
http://forum.xda-developers.com/showthread.php?t=2582845
Very nice ROM, works perfect, better then stock
Click to expand...
Click to collapse
Thanks, i might test it this weekend.
Working
i have a g2 d802 and i have tried the script workaround and is fine, but when i do put the phone next to my ear the screen remains on and does not go off, is this something i can chhange?
is there another workaround?
i am using Cm11
Had the same problem.
Great temporary fix: right after you unlock the screen hit the volume button once or twice. Not a permanent fix but it works for the time being.
It usually blacks back out because something is wrong with the proximity sensor next to the front camera. Either it's covered partially, dirty, a screen protector is peeling off over it, etc. I've read that some people have problems with the screen not coming back on during calls because the proximity sensor is messed up. Some said to use a high powered suction vacuum and put it up against the screen to get debris out of the cracks or simply try wiping it clean if there's something on it. Hopefully it works!
1509
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg
Sly_North said:
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg
Click to expand...
Click to collapse
I just want to pop in and say thanks for this fix. It really helped. :good:
proximity sensor issue
i had the same issue for my lg g2 . when i searched the internet for solution , all i got was to install proximity sensor disablers , rooting apps to disable them . i have solved the issue interms of hardware . the solution goes :
1 . go watch a youtube video of teardown of lg g2
2. in the video there will be showing a plug that connects the sensor to the circuit board.
3 . pick up a screw driver , open the casing of ur phone
4. unplug the connection between the board and the sensor
5. put everything right back
6 PROBLEMO SOLVED BAYBE
thank me
Just in case someone searched and finds this thread - the easiest way to disable the proximity sensor on any rom/kernel is to go through Xposed and this module: http://repo.xposed.info/module/com.mrchandler.disableprox
Works on 4.4, 5.0.2, Cloudy's rom, Dorimanx's kernel...
Big Thanks!!!
Sly_North said:
Oh god, I just permanently fixed my proximity sensor \o/
So I had the issue where the proximity sensor would detect something near it, making it hard to wake up the phone (screen getting dark after half a second, as the phone thinks it's still in my pocket) or keeping the screen dark after a call.
An app displaying the proximity sensor output was showing the sensor always reporting 0cm when it's not working, and 5cm when it's fine.
If your get "no data" in a test app, then sorry you have another issue. Probably a dead sensor. If you do get the sensor always returning an obstacle at 0cm, keep reading!
I also noticed that pressing on the screen around the sensor kind of made it work. So I thought for a while my screen was slightly off, maybe slightly unglued.
But it's the opposite: it's actually the sensor that was moving a bit, thus getting too far from the screen surface - and detecting the screen as the obstacle. Just by a ridiculously small amount.
Now THE FIX:
I switched off the phone, and removed the SIM and the rear door,
I removed the 7 screws holding the top plastic plate and buttons
On the rear of that plastic plate with the buttons, there's a small soft pad that pushes on the sensor to hold it against the screen: that's your target! That pad is just a tad too thin.
I've put a very small piece of adhesive tape (I used a slightly thick double-face white tape, maybe a tenth of a millimeter) on that pad,
Then I put everything back together and... the sensor now works! All the time! And the knock-on too of course.
I can't post a picture of the pad below the button assembly. But if you look for "OEM Part - AT&T LG D800 G2 (WHITE) Rear Back Housing + Buttons + Camera Lens" on ebay, and look at the 2nd picture, the pad is the fully black rectangle on the top left, on the right of the empty black rectangle and below the half-circle small opening (probably for the light sensor).
Pic of the fix: reho.st/self/cb4a29e598652f925a19f05770b6f192b09af8f5.jpg
Click to expand...
Click to collapse
After almost a week trying to solve this, your answer hit right on the spot! I found it funny how the roms not based on stock LG's are not affected by this issue, but all of the LG's ones (I've tried 4 LG's stock roms and CloudyG2) so I've always assume this was a SW issue (and probably can be addressed via SW) so when I get to your answer saying that could be fix tearing the phone apart I was reluctant to do so, but as I've told you guys I was desperate. On a sidenote, the Stock JB ROM is not affected by this, but it is death slow for this times.
BTW, I've wanted to have a ROM that had the LG's camera app (any version) since the ones that came on the CM ROMs wasn't really good enough for my taste, so now I'm rocking the CloudyG2 3.2 ROM with any issues so far.
Your fix gave my phone some solid 6 more moths of life! (at least!) THANK YOU!