Database Users

Proximity Sensor Problem 1.61 :-( Is this the issue?

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

[IMPORTANT][HELP NEEDED] HD2 Proximity Sensor - WakeUp Problem

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.

[Q] Proximity sensor funkiness?

This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?

I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App

I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.

I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.

ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?

Yeah, ditto that - how do recalibrate the sensor?

Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.

I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#

Ok, mine says No Detection. Is there anyway to set the value?

One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.

If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.

ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?

samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....

Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps

What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?

BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?

another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?

rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned

[Q] Proximity Sensor Fails

Just wanna ask if there is any temporary fix to the proximity sensor of nexus 4.
During calls the screen doesn't turn off when placed close to the face.
I didn't get the chance to test it on stock 4.2 because when i turned my phone on it updated first to 4.2.1. Ever since then it has had proximity sensor not working during calls.
And i have never had any screen protectors on the screen.
Tried many custom ROMS as well but no difference at all.
Sent from my Nexus 4 using xda premium

how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken

I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.

isnt there a proximity senor app which lets you test it on the market?

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
Click to expand...
Click to collapse
Using stock. No issues on the sensor. Turns off on calls and turns on when I remove from the face. Have a spigen protector on with a cutout for it
Sent from my Nexus 4 using Tapatalk 2

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
Click to expand...
Click to collapse
I was on stock 2 weeks ago when I started noticing it.
I am on cm now as well and its very much messed up.
Sent from my Nexus 4 using xda premium

bobola said:
isnt there a proximity senor app which lets you test it on the market?
Click to expand...
Click to collapse
There is.
I've installed and tested.
According to the app results, The proximity sensor seems to know when my hand is on it and when its off it. The value changes from 1.0 to 2.0
It just won't work on phone calls.
Sent from my Nexus 4 using xda premium

noobdeagle said:
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
Click to expand...
Click to collapse
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium

slimldj said:
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mine is stock and during calls it usually goes to my settings menu and changes my clock setting. When I get off the phone, screen is blank and I hit power button to end call. Still annoying at times when the clock changes.

any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I'm suffering this same problem too, hope they fix it soon..

slimldj said:
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes I think the fact that the app testing showed the sensor working so it points to software. Something is missing when the phone is in a call its not connecting to turn off. I thing Jellybean was flawed in many ways. My drop down brightness slider doesn't work for me nor auto brightness its OK for me cause I don't use either but still makes me mad.
Using Tapatalk 2

meetoo
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.

treaty said:
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
Click to expand...
Click to collapse
Having the exact same issue here too on stock ROM.
Good idea on the accessibility settings! Will work until/if they fix it..
Also no screen protector.

I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.

Dav_prime said:
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Click to expand...
Click to collapse
It was the same fix for mine when I first got my bse it worked fine for about a week but then over time it got worse. It was the screen protector just that lil bit worth of it wear caused enough blockage of the sensor. I got some new bse's and they now have a cutout for the proximity sensor and are screen optimized.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2

use Proximity Actions by Novum Inceptum in playstore

rat99 said:
use Proximity Actions by Novum Inceptum in playstore
Click to expand...
Click to collapse
That won't fix anything.

[Q] Proximity Sensor / Autorotation Not working after Screen Replacement

So I dropped my nexus 4 cracking the screen which required me to replace the LCD assembly. After putting it back together and firing it up I noticed that the Auto Rotation (Yes the setting is checked in the settings) and the proximity sensor are not working. I installed Android sensor box and it is getting no reading from the proximity sensor or the gyro sensor. I have taken the phone apart multiple times to ensure everything is connect and everything looks correct. I have also unlocked the phone and have re flashed the stock rom with it not fixing the problem. Any help would be much appreciated.

My wife destroyed her display. Did same but gyro works fine but proxy is the problem. Work around so far is to set power button to end calls becasue screen just goes black when making/receiving calls kind of makes phone useless if you can't see screen.
I too have taken it apart several times and still nothing. Next plan is to find a new sensor unit and replace it.
From what I have been able to see in all my searching the proxy is extremely sensitive any deviation in placement, smuge on unit or display, minor deviation on color of display, screen protector, any interference from skins can affect it so check all those also.
In one of the threads on the Galaxy Nexus there is a patch to turn off sensor and there is mention of app in market that does the same, haven't tried yet have to get phone from wife to try, could be possible solutions also.
Will post back with findings as I get to try them.
Found great app in market Sensor Kinetic Pro shuts off proximity sensor or any other sensor no more problem with black screen after making calls. Still going to try replacing sensor however found it on Amazon less then $5.00.

silvagroup said:
My wife destroyed her display. Did same but gyro works fine but proxy is the problem. Work around so far is to set power button to end calls becasue screen just goes black when making/receiving calls kind of makes phone useless if you can't see screen.
I too have taken it apart several times and still nothing. Next plan is to find a new sensor unit and replace it.
From what I have been able to see in all my searching the proxy is extremely sensitive any deviation in placement, smuge on unit or display, minor deviation on color of display, screen protector, any interference from skins can affect it so check all those also.
In one of the threads on the Galaxy Nexus there is a patch to turn off sensor and there is mention of app in market that does the same, haven't tried yet have to get phone from wife to try, could be possible solutions also.
Will post back with findings as I get to try them.
Found great app in market Sensor Kinetic Pro shuts off proximity sensor or any other sensor no more problem with black screen after making calls. Still going to try replacing sensor however found it on Amazon less then $5.00.
Click to expand...
Click to collapse
Somewhat comforted to see others are also having the same problem... I recently replaced my nexus 4 screen only to have my proximity sensor fail on me too. Interestingly enough, i disassembled my phone multiple times to test if the sensor still works, turns out it does, but it is super sensitive. In my first experiment I had the sensor dangling out of the socket to see if it was still receptive to light, it worked perfectly - I used my hand as a 'face-simulator' to test for sensitivity. I then tried to place it back in the rubber grommet with the grommet seated firmly in the socket and what I found was that it worked, so long as there was only limited pressure on the enclosure. For example, it only works when there are no adjacent screws (for the plastic motherboard cover) applying pressure in the nearby area. I thought I could live with that, but then I tried putting the rear plastic cover back on and,... back to square one, dead screen on-call. I figure it has something to do with either pressure sensitivity or perhaps the pressure from the screws or the rear cover pushes the sensor too close to the glass?
Anyway I'd be keen to see if replacing the audio jack will actually fix the problem, any of you guys had any success with that? Meanwhile i'm going to just use the power button for ending calls. Any tips for how to use the speakerphone during a call?
Cheers fellas.

New sensor arrived yesterday changed out my wife's non functioning sensor and new one working great. Old sensor was bad !!!! She had dropped the phone several times and last accident she unintentionally threw it. Suggest no one do that
Sent from my Amazon Kindle Fire HD using xda premium

silvagroup said:
New sensor arrived yesterday changed out my wife's non functioning sensor and new one working great. Old sensor was bad !!!! She had dropped the phone several times and last accident she unintentionally threw it. Suggest no one do that
Sent from my Amazon Kindle Fire HD using xda premium
Click to expand...
Click to collapse
New sensor arrived the other day, I have since swapped out the old one, everything works great now!

17
dhaub said:
New sensor arrived the other day, I have since swapped out the old one, everything works great now!
Click to expand...
Click to collapse
whered u get the sensor?

chamilun said:
whered u get the sensor?
Click to expand...
Click to collapse
I know this is old but I'm having the same issue. How did you guys make out? Were did you get the sensor? Saw one on ebay $109 seems pricey

btack said:
I know this is old but I'm having the same issue. How did you guys make out? Were did you get the sensor? Saw one on ebay $109 seems pricey
Click to expand...
Click to collapse
I put a case on mine and it started working. It always would work if i put a bit of pressure on different parts of the phone. So im not sure if bad contact on sensor or if more some type of alignment issue. But it does work now. speakerphone is terrible since cracked screen tho..