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.
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
Hy all
I have a strange problem with my X10! The will not go off in a call! (or at least most of the times it won't) The sensors should turn the screen off while the phone is to to my ear but most of the time it will not!
There is a hidden menu that have tests for almost every hardware component but the test for the proximity sensor only shows that the sensor is OFF and won't do the test!
Ideas?
The sensor is the little black circle (sort of) above and to the left of the "n"
e.g. Sony Ericsso'n'
Have you tried putting your finger over it during the test?
same problem here i tried the finger-trick doesnt work
I tried it and the test shows ON while my finger is there! So the sensor works properly but why the dialer is not using it to control the screen?
As stated before, if you cover the 'hole', the screen would not react to any of your finger touches. The screen would still be on but would turn off according to your settings (like 30 seconds or 1 minute or whichever). Try it. Call someone, cover the hole and try to hit 'end call' or slide up the keypad and then cover the hole and try to hit numbers.
The purpose of the proximity sensor is to turn the screen off in a call while the phone is to your ear! if i cover the sensor it must turn the screen off! but it doesn't! There is some kind of timeout set to this! The screen will turn off but after some time! this makes the proximity sensor almost useless!
No, it is to disable touchscreen buttons. It will turn off when time you've selected is over and turn on again and enable touch buttons when you take the phone out from your face.
Though i think you're right, it should turn the screen off to save battery, it is silly to have the screen on when you are using it.
Sent from my X10i using Tapatalk
Zenghelis said:
No, it is to disable touchscreen buttons. It will turn off when time you've selected is over and turn on again and enable touch buttons when you take the phone out from your face.
Though i think you're right, it should turn the screen off to save battery, it is silly to have the screen on when you are using it.
Sent from my X10i using Tapatalk
Click to expand...
Click to collapse
Quite right!
I guess the expectations are again set by Apple's standards. Their proximity sensor functions as one would expect.
However the sensor on the X10 does what it was designed to do, and that's to deactivate the touchpad whilst the device is held up to your ear.
The screen timeout is a different setting all together (unfortunately).
Baggyb said:
Quite right!
I guess the expectations are again set by Apple's standards. Their proximity sensor functions as one would expect.
However the sensor on the X10 does what it was designed to do, and that's to deactivate the touchpad whilst the device is held up to your ear.
The screen timeout is a different setting all together (unfortunately).
Click to expand...
Click to collapse
Not the expectation set by Apple. It's expectation for any right minded individual.
SE software is just well known as one of the worst top players in the industry.
FFS, they spent all the time on DRM, lock the phone, developing battery hungry useless software on 1.6 rather than push out 2.1 asap, that tells you something.
superprelude said:
Not the expectation set by Apple. It's expectation for any right minded individual.
SE software is just well known as one of the worst top players in the industry.
FFS, they spent all the time on DRM, lock the phone, developing battery hungry useless software on 1.6 rather than push out 2.1 asap, that tells you something.
Click to expand...
Click to collapse
Why not go through the Manual once before abusing Company left - right.....
Let me copy and paste it for you guys........
Sensors
Your phone has two built-in sensors – a light sensor and a proximity sensor. The light sensor is used for automatic LCD backlight control. The proximity sensor turns the touch screen off when your face touches the screen. This prevents you from unintentionally activating phone functions when you are engaged in a call.
TechGuru_x10 said:
Why not go through the Manual once before abusing Company left - right.....
Let me copy and paste it for you guys........
Sensors
Your phone has two built-in sensors – a light sensor and a proximity sensor. The light sensor is used for automatic LCD backlight control. The proximity sensor turns the touch screen off when your face touches the screen. This prevents you from unintentionally activating phone functions when you are engaged in a call.
Click to expand...
Click to collapse
Yes and this is plain stupid use of the sensor! Take the HD2 for instance! Its proximity sensor turns the screen off the second you take the phone to your ear! This is done with every HTC device having the sensor! It is just misused on the X10! I hope that somebody here would correct this with a little program some day!
OrionBG said:
Yes and this is plain stupid use of the sensor! Take the HD2 for instance! Its proximity sensor turns the screen off the second you take the phone to your ear! This is done with every HTC device having the sensor! It is just misused on the X10! I hope that somebody here would correct this with a little program some day!
Click to expand...
Click to collapse
This is the main problem with us ,,, we start to compare and complain rather than think why did SE will give two sensors instead of one.
Answer is not known to me but this much I know they know better than us.
If you think you know better, be my guest and throw some knowledge here. I am new to Android but not to SE.
So im new to the forums, but I was having a problem with the proximity sensor...
As stated in a lot of threads, the proximity sensor does work and will "lock" the screen so that once your face is near the screen it will not allow any clicking of the buttons.
Also the screen is supposed to turn off about 15sec into the call. Mine turned off, but then all of a sudden turned on again...this would happen repeatedly.
I found out the solution...it seems advance task killer was not allowing the screen to turn off.
I had auto kill enabled and set it to when the phone was locked to kill apps.
I turned off auto kill, and everything seems to be working fine with the screen and proximity sensor now..
hope this helps anyone having this issue!
thx, same problem here !!
so its pretty clear none of us know the answer to this, but yet we're still bashing each other. LOL! ppl let's get constructive, we dont have the answers so lets accept the fact and seek help some where else.
o2 Germany told me, that Sony Ericsson will bring us an update within the next 4 weeks to all devices.
It will be an update with alot of bug fixes (e.g. proximity sensor ) and speed improvements.
So, be cool. Sony Ericsson is working on that and with Eclair in autumn, our battery will perform very well.
Hey,
I'm having a problem with my proximity sensor. If I make a phone call, the screen turns automatically black, even if sensor isn't covered. And I can't turn the screen back on during call, only if the conversational partner hangs up, then it turns back on normally. If I try to hang up, the phone the display stays black for about 2min.
I'm having this problem only with WP7 & Android, works normally on WM6.5.
Hope somebody can help me.
Thanks in advantage.
You saying it works fine with winmo, it has to be a setting or bad flashing. You can try wiping your phone and starting over. I haven't played with WP7, but in some andriod roms there is an opition to use proximity sensor in the phone settings. Goto settings/ call settings. You might want to check and see. might be able to help you more if you were to tell what rom and how you installed.
This setting montecarlo5 mentions is available in cyanogenmod roms.
Are you sure there's no dirt covering your proximity sensor? Maybe Android is more sensitive than WM/WP.
I'm using RAFDROID HD 2.3 and like u allready said, the setting isn't available.
I'm having this issue on every NAND build i ever tested, but the sensor is 100% clean.
Please guys, don't open everytime a new thread before searching, if some one did the same -.- I made some tests to find out the reason of this issue and how to solve it (more or less).
Pls follow: http://forum.xda-developers.com/showthread.php?t=913134
I have a really annoying bug in my WP7 HD2. When i make a call, the screen goes black and i cannot access anything. The call connects fine but the whole phone locks up. I can't access the dial pad for using automated services, nor can i hang up. Hardware buttons do not work either, but light up briefly if i push one. I think its something to do with the light sensor, sometimes if i cover it and uncover, the screen quickly comes on then goes off again. Any ideas? I am using the latest radio from the stock HTC WM 6.5 ROM, and the newer (51t?) radio for WP7. I have tried older versions of both, and a few different WP7 roms all with the same problems.
WP7 Mango (xboxmod/yuki)
UK HTC HD2
This problem also happens on android.
Uhh, sounds awful 'cause you experience also on different Android...
Do you experience this also on a Stock WM 6.5 Rom (of course with the original radio and without hpsl)? If not, you can be relaxed cause it's no hardware fault then. If it's also present on WM 6.5, then it's very likely to be an hardware error.
a little update on my problem. it appears that if i tilt the phone at a 30 degree angle downwards, while in a call, the light sensor functions normally. so at least navigating those phone menues can be done! i think this is a hardware problem, my HD2 did suffer a pretty nasty fall (which resulted in a new screen!) so maybe there was some other damage beside the screen.
matthewharmon102 said:
a little update on my problem. it appears that if i tilt the phone at a 30 degree angle downwards, while in a call, the light sensor functions normally. so at least navigating those phone menues can be done! i think this is a hardware problem, my HD2 did suffer a pretty nasty fall (which resulted in a new screen!) so maybe there was some other damage beside the screen.
Click to expand...
Click to collapse
there are two sensors together to the left of the earphone at the top of the screen, one is a light sensor, the other a proximity sensor. It seems to be the proximity sensor that is at fault. When you put your ear to phone it switches screen off so you dont push buttons.
I have read that the prox sensor can become misaligned when replacing screen. Did it occur after this? warranty?
as soon as i make a call the screen switches off. also the auto brightness doesnt seem to be very responsive. the issue had happened before but it was more of a driver issue than a hardware fault. i noticed it more after the repair, but it was not instant. maybe one of the sensors was lose and after a few months of use it is now misaligned? the phone is out of warrenty, and the 3 month warrenty on the repair is also up, and i have no insurance anymore i am holding out for a new phone. just started a new job so hopefully i can get something outright without being tied to a contract
Same problem
I'm having the same problem I think I noticed it when it was running windows 6.5 but I really noticed it after 7 upgrade. as soon as I make a call I cant access anything. THe bad thing about it is this phone is a replacement. I just got it. Maybe they sent me a badly refurbished one. Has anyone found a solution to this. If i'm smart I know this is not as simple as changing a setting sound like re flash, erasing, re installing, etc.
did you try tilting the phone downwards towards you? when i do this the menu appears and i can access everything. normally i put it on speaker then the screen stays lit then i cna use it as normal
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?