Title says it all. Its a very odd glitch. If i call someone, unless i quickly exit the phone app, my screen turns black but my call will continue. I cant turn the screen back on until the call is ended and i have to pull the battery. It happens regardless of what rom im on. Any help? Thanks in advance everyone
Sent from my SCH-I535 using Tapatalk 2
Have your cleaned your sensor in the front of your phone.
Sent from my SGS3 running Eclipse 2.1
No, what is/how do i do that?
Edit: I also have a ghost armor/ slick wrap sort of thing on the front of the phone. Is that the reason?
http://a248.e.akamai.net/origin-cdn...pfiles/photos/SW-GALS3-CFRED-3.jpg?1342082302
Sent from my SCH-I535 using Tapatalk 2
I would try removing that skin, it could be blocking the proximity sensor. I had the same problem on a galaxy nexus. I tried clearing phone app data, reboots, factory resets. In the end had to send it in on warranty because the sensor was bad.
Sent from my SCH-I535
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
GalaxyS3IsMeh said:
Its weird though because the screen only turns off if the app i am running and xcan interact with is the phone application. If i use firefox or anything else while making the call everything is hunky dory.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
bbelos said:
Try using an app that shows sensor readings. I like to use Elixir2 which has a sensor section. When viewing the proximity sensor readings, it should indicate "Far" when nothing is activating the sensor, and "Near" if you cover the sensor (with your finger or whatever). If it reads Near without you purposely tripping the sensor, your protector could be covering it or something else is wrong.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Yeah try this. Problem with my phone was intermittent, clearing the phone app data seemed to fix it but it always came back.
Just out of curiosity did you ever install an app called facebook contacts?
Sent from my SCH-I535
Not an app besides messenger and the actual fb app persay, but i did sync them to my contacts
Sent from my SCH-I535 using Tapatalk 2
The app was actually facebook contact sync. It's a third party app and I had originally thought it may of had something to do with the problem. That's why I asked.
I don't think it's a software problem because you said it happens on all of the roms you've tried. My nexus was stock and I did several factory resets, even waited for the jellybean update. Nothing I did was ever a permanent fix.
So I think either something is blocking the sensor i.e. dirt or the screen protector, or the sensor is bad.
Sent from my SCH-I535
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Not to keep this thread alive or anything, but I gave my dad my old phone and he complained to me a few days later that the screen kept going off as well so I met him only to find out that he had the case on wrong and it was blocking the proximity sensor. He definitely is not cut out for a smart phone.
Sent from my SCH-I535 using xda app-developers app
galets said:
My proximity sensor went bad after I replaced a screen lens by heating up and unglue technique. I turned it off in the phone app, and now it's fine, but for me it's very irritating that I have a high-end device which is somewhat broken, so I started researching what's wrong and how to fix.
It does work, I tested it by enabling hidden menu ( *#22745927 ) and then diagnostic mode ( *#0*# ) + click "Sensors". It does show proximity sensor at ADC 16 or more (I think it triggers at 15, so always on). When I bring the hand to the sensor, ADC goes to 100, so the sensor is somewhat working, but it always does sense something which isn't there, which is causing it to misfire. I have another good S3, and ADC value on it is 0 or 1 when nothing is in front of it, so my sensor could clearly be better.
I have no idea what ADC is, by the way
I have another broken front panel laying around, so I took the phone apart and replaced a sensor with the one from that panel. I did see a slight improvement, which is: ADB value went down to 11-12, so the sensor was not ALWAYS in triggered state, but clearly still no bueno.
What I'm going to do now is get a new item and try replacing with a new one. It's not overly expensive, like 10 bucks when shipped from china (search for "Front Facing Camera s3" on ebay). Should that be a success, I will post my results here.
I also am not sure if it is possible to recalibrate sensor to not trigger if ADC value is, say, below 20 and such. I would imagine there could be a configurable value. Somewhere this value of 15 is coming from, isn't it? So, idk, if some guru here is reading this post, maybe could advise where to go to configure it
Click to expand...
Click to collapse
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
galets said:
UPDATE: I bought a brand new sensor/camera block, and same issue there: minimum ADB is ~12. So, it's glass. It is possible that the sensor openings are either slightly shifted, or too dark.
Anyone knows how to configure the threshold value?
Click to expand...
Click to collapse
You shouldnt have to go through all this man. You should get a new phone
Sent from my SCH-I535 using Tapatalk 2
Solved, yay!!!!!!
GalaxyS3IsMeh said:
You shouldnt have to go through all this man. You should get a new phone
Click to expand...
Click to collapse
Nope, I got it resolved!!!!!!!!
Here's how, with pictures: http://blog.galets.net/2013/01/fix-proximity-sensor-on-samsung-s-iii.html
Related
Guys, I have a problem with the proximity sensor on my Captivate.
The issue is that while on a call, when holding the device between my ear and my shoulder, the proximity sensor causes the screen to turn on, and starts randomly hitting buttons. So I tested it.
The proximity sensor works perfectly when the phone is "standing" on end and the proximity sensor is covered. It does NOT work (the screen does not turn off) when the phone is laying flat and you cover the sensor.
So bottom line, when the phone is standing 90 degrees, the proximity sensor turns the screen off when there's no light. When the phone is 180 degrees (or anywhere near it), even when there is no light, the sensor does not turn the phone off.
Is there any way for me to tweak the sensor at all using an app? Or is my phone defective?
Thanks.
With the phone flat on the table and I make a call, using my finger to cover the sensor the screen goes off. I try to twist and turn the phone in all angles and the screen is still off. Not sure if it's related but I had the same problems with the screen coming on when using my shoulder and cheek to hold phone.
My hair was a little longer and I think the hairs blocked the sensors.
baseballfanz said:
With the phone flat on the table and I make a call, using my finger to cover the sensor the screen goes off. I try to twist and turn the phone in all angles and the screen is still off. Not sure if it's related but I had the same problems with the screen coming on when using my shoulder and cheek to hold phone.
My hair was a little longer and I think the hairs blocked the sensors.
Click to expand...
Click to collapse
I just did the same thing. With the phone flat on the table and I make a call, cover the proximity sensor with my finger, the screen stays ON. The minute I put the phone up 90 degrees, the screen shuts off.
What's going on?
ajm786 said:
I just did the same thing. With the phone flat on the table and I make a call, cover the proximity sensor with my finger, the screen stays ON. The minute I put the phone up 90 degrees, the screen shuts off.
What's going on?
Click to expand...
Click to collapse
Perhaps you are running a different combination of kernel/rom? One that takes into account the devices orientation when engaging the proximity sensor?
I've never actually tested this, but I know I had various degrees of proximity sensor problems running certain ROMs. So maybe try a different combination?
Shammyh said:
Perhaps you are running a different combination of kernel/rom? One that takes into account the devices orientation when engaging the proximity sensor?
I've never actually tested this, but I know I had various degrees of proximity sensor problems running certain ROMs. So maybe try a different combination?
Click to expand...
Click to collapse
I'm running Cognition 2.3b, if that helps.
ajm786 said:
I'm running Cognition 2.3b, if that helps.
Click to expand...
Click to collapse
Doesn't actually sorry...
Haven't used any of the Cognition ROMs in quite a while. DesignGears has a nice IRC channel though where lots of people tend to hang out. Maybe hop over there and politely ask around to see if anyone else has had the same problem? Asking within a group of Cognition users might get you more help than the XDA population in general.
All I can say is that with my i9000 kernel/radio/rom combo, my proximity sensor is not affected by the device orientation. Also, you could try running a proximity sensor test and see what happens, just to rule out defective hardware.
*#*#0588#*#* – Proximity sensor test
Hope that helps.
Shammyh said:
Doesn't actually sorry...
Haven't used any of the Cognition ROMs in quite a while. DesignGears has a nice IRC channel though where lots of people tend to hang out. Maybe hop over there and politely ask around to see if anyone else has had the same problem? Asking within a group of Cognition users might get you more help than the XDA population in general.
All I can say is that with my i9000 kernel/radio/rom combo, my proximity sensor is not affected by the device orientation. Also, you could try running a proximity sensor test and see what happens, just to rule out defective hardware.
*#*#0588#*#* – Proximity sensor test
Hope that helps.
Click to expand...
Click to collapse
I can confirm using the proximity sensor test that it works fine. Proximity sensor only has two states, 1 and 0, correct? No matter the way I hold the phone, the proximity sensor test shows it running perfectly.
Does this mean that there's a problem with the ROM? Is it possible for me to simply replace the phone.apk?
Edit: Here's the EXACT problem I'm having. http://code.google.com/p/cyanogenmod/issues/detail?id=1916
I have this same issue!! I HATE IT! I have considered going BACK to my iphone because of it! I get tired of muting people and ending calls
ETA: I am using the leaked 2.2 Froyo not cognition
Does anyone know how to fix this? It's getting REALLY annoying!!
Does anyone know if dg is going to fix this in Perception?
ajm786 said:
Does anyone know if dg is going to fix this in Perception?
Click to expand...
Click to collapse
Does it work if you flash back to the stock ROM? If it works on stock then it's a problem with the ROM, If it doesn't work on stock then it could be a problem with your phone...
jhernand1102 said:
Does it work if you flash back to the stock ROM? If it works on stock then it's a problem with the ROM, If it doesn't work on stock then it could be a problem with your phone...
Click to expand...
Click to collapse
Yes. Flashing back to stock ROM it works perfectly. Any of the Froyo ROMs, it does not work. Cyanogenmod fixed this in his ROMs, but I am not sure if dg plans to implement this in his ROMs. :-( Unfortunately, this behavior is by design in Froyo. Google decided that during a call, it makes more sense that as soon as your phone is put in a horizontal position, that the accelerometer overrides the proximity sensor and disables it. Their decision makes no sense, because it then invalidates the need for a prox sensor in the first place.
ajm786 said:
Guys, I have a problem with the proximity sensor on my Captivate.
The issue is that while on a call, when holding the device between my ear and my shoulder, the proximity sensor causes the screen to turn on, and starts randomly hitting buttons. So I tested it.
The proximity sensor works perfectly when the phone is "standing" on end and the proximity sensor is covered. It does NOT work (the screen does not turn off) when the phone is laying flat and you cover the sensor.
So bottom line, when the phone is standing 90 degrees, the proximity sensor turns the screen off when there's no light. When the phone is 180 degrees (or anywhere near it), even when there is no light, the sensor does not turn the phone off.
Is there any way for me to tweak the sensor at all using an app? Or is my phone defective?
Thanks.
Click to expand...
Click to collapse
i think its cognition. i didnt test it but i had the problem during calls, i figured it was sesitivity not position but like i said i never tested it . i think its a jj4 bug. now im using perception and it works better.
Dani897 said:
i think its cognition. i didnt test it but i had the problem during calls, i figured it was sesitivity not position but like i said i never tested it . i think its a jj4 bug. now im using perception and it works better.
Click to expand...
Click to collapse
It's not Cognition. It's Froyo. Google made the choice to have the accelerometer disable the prox sensor as soon as the phone was oriented horizontally. I can't see in what situation that would make any sense at all.
Still no answer for fixing this? I am not using cognition, I am using the leaked Froyo...
FYI, im in stock eclair. I have this issue.
sent from my Captivate
I'm running cognition b7 and have the same issue but just hit the power button to manually toggle the screen in a horizontal position during a call. Hardly an inconvenience.
fooldog01 said:
FYI, im in stock eclair. I have this issue.
sent from my Captivate
Click to expand...
Click to collapse
Eclair does not have the problem at all. Tried, tested and true. If you have the problem with stock Eclair, something is physically wrong with your phone.
silver2wind said:
I'm running cognition b7 and have the same issue but just hit the power button to manually toggle the screen in a horizontal position during a call. Hardly an inconvenience.
Click to expand...
Click to collapse
That's not the point. The point is that they gimped Froyo on purpose, and for what, I don't know. It's counter-intuitive.
Just so you know, my co-worker has the Nexus S, which is basically the exact same phone as ours, except with Gingerbread. Guess what? It's FIXED on Gingerbread. Figures.
Got a brand new DS couple of days back and....right from opening the box..the first call..proximity sensor is playing up. Most times i have to pull out the battery to end the call.
Tried the following with no result
1) Installed DHD Proximity re-calibrator
2) Factory reset
3) Installed Vitrous Unity 1.27
4) Back to factory rom, blew hard between ear piece and sensors
5) Removed screen protector and tested
I have S- Off and really dont want to go through the pain of visiting HTC. Would greatly appreciate some help here ...as always !
did you press the back button in between the call?
this has happened to me on stock rom only if i press the back button during the call
i haven't tried it on LBC rom yet
sujitht said:
Got a brand new DS couple of days back and....right from opening the box..the first call..proximity sensor is playing up. Most times i have to pull out the battery to end the call.
Tried the following with no result
1) Installed DHD Proximity re-calibrator
2) Factory reset
3) Installed Vitrous Unity 1.27
4) Back to factory rom, blew hard between ear piece and sensors
5) Removed screen protector and tested
I have S- Off and really dont want to go through the pain of visiting HTC. Would greatly appreciate some help here ...as always !
Click to expand...
Click to collapse
I noticed that only half the proximity sensor is visible, the other half is covered by what appears like black plastic part. Is this how it is supposed to be?
My proximity sensor is completely visible.
No..i haven't pressed the back button.
mikeyd85 said:
My proximity sensor is completely visible.
Click to expand...
Click to collapse
Is it the left sensor of the two sensors?
I have exactly the same problem. The issue seems to be that Desire S proximity sensor active distance is 9cm, when on my older Desire ir is only 1cm.
When working with some Proximity sensor tools, I have discovered, that you need to put your phone like 25cm (have no idea, how many inches) away from any obstacle in 30degree radius. If that is followed, I haven't been able to recreate a battery pull ocasion of sensor failure. However in real life talking, it is impossible to guarantee.
That there must be some sensor configuration possibilities, so that we could decrease sensibility to minimum distance. Such change should solve this sensor bug, as it would be normal operation distance.
Maybe some dev knows, how to play with proximity sensor?
Yeah, I have had this problem a long time with this phone didn't happen that much at first then it became more and more apparent.
Found the problem and solution, it lies with the screen protector, yes it might be transparent but the sensor detects it. Using a sensor testing app from the market it suggested the sensor was covered almost all the time.
So the solution was replace the protector with new one but cut an arc at the top just big enough around the sensor at the top left, easy fix now in call screen is more responsive.
Sent from my HTC Desire S using XDA Premium App
Totaly plausable question,but where is the sensor?
bleach1 said:
Totaly plausable question,but where is the sensor?
Click to expand...
Click to collapse
Top left of the screen in opposite place to led, if you tily screen under light you should see the sensor reflect back at you
Sent from my HTC Desire S using XDA Premium App
Thanks will adapt my screen protector
Sent from my HTC Desire S using XDA Premium App
Proximity sensor
I've been having the same issue. I gave my DS to the HTC workshop and they said it was faulty hardware. They will be replacing the system board since the sensor is soldered to it (under waranty).
Before sending it in, I tried a few roms and hacks but it was never resolved. I recommend you visit your local HTC warranty center.
I have the same problem with the proximity. I installed an app called Anyunlock which seems to have solved the problem. It seems to be able to wake it when the screen turns off after a call. The app allows you to unlock with the volume key and replaces the lock screen with its own. I hope this keeps working
The lights for my three softkeys don't always turn on, unless i cover the front cam/light sensor with my finger. any way to fix this so that the backlight turns on when i'm using the phone?
usmelllikecheez said:
The lights for my three softkeys don't always turn on, unless i cover the front cam/light sensor with my finger. any way to fix this so that the backlight turns on when i'm using the phone?
Click to expand...
Click to collapse
its automatic with light sensor
yeah, i get that...
but, i'm sitting in complete darkness right now, and the soft key lights aren't coming on. the only way it does is if i cover the front camera with my finger.
does that mean it's faulty? or is there something i can do to make the lights come on when they're supposed to?
Mine are hit or miss. Most of the time I find myself covering the sensor like you said. Didn't see an option to adjust sensitivity or anything. Pretty lame.
I noticed this too. They should make settings option to be selected by user...miss the perfection of the NEXUS one
usmelllikecheez said:
yeah, i get that...
but, i'm sitting in complete darkness right now, and the soft key lights aren't coming on. the only way it does is if i cover the front camera with my finger.
does that mean it's faulty? or is there something i can do to make the lights come on when they're supposed to?
Click to expand...
Click to collapse
I think it is faulty, my key light is on whenever the surrounding light condition is poor. Don't think there is a setting for this but I might miss something here.
Bottom line, if you fully checked the setting cannot find anything, just exchange it.
Mine also seem to be inconsistent. Sometimes they come on immediately (like they should), sometimes I have to open an app, and sometimes they won't come on at all.
One wacky theory that I have is that the sensor is getting tricked by the reflection of the screen from my glasses. It may be in my head, but I feel like the issue comes up less when I am wearing contacts.
Maybe a solution
Have you tried this one? I did on my cm9-ed U8160, maybe it works on your devices too.
Mine are perfect, never have to cover the proximity sensor. Probably just a thing with different batches of devices. Got mine early summer around June.
Sent from my HTC VLE_U using xda app-developers app
First time poster, though been a regular lurker.
It seems I have a slightly dodgy proximity sensor. Have checked with one of the proximity sensor apps and while the sensor detects if I have my hand over it, it is very unreliable when I take my hand off. It can take from anywhere from 1 to 30 seconds or sometimes never.
While ive been through other threads where people have a completely failed sensor, does anyone have this intermittent problem. Also is this a hardware or software issue.
Im currently htc-dev unlocked running Pacman v15.0.
Out there is a tool for recalibrating the sensor, but you would need to be S-OFF I think and it's done with a service tool (a special PG88DIAG.nbh)
Let me know if you are willing to try it, but it is VERY dangerous if you do the wrong things.
I had the exact problem from the very beginning. Got a phone and the very next day had a screen protector applied. For a few days proximity sensor created problems. The screen would go black when the call started, but until the call did not end, there was no way to bring the screen back. So, I used an app just like yourself to check and saw the same thing happening. Ultimately read extensively and realised it was due to screen protector. Took a scissor and cut off the protector above the sensor. A few months later when I had a new protector (of a different company) applied the same problem reappeared, so I had to cut it off from the top. Except that this time around I was sort of expecting it. I hope this help! :fingers-crossed:
I had the same problem and it continued no matter whether i remove the protector or cut the portion....im unable to most awesome ROM's.......only n sense 4.0 im able to re turn on the screen using power button.if there a way to completely disable this turn off during calls irrespective of the ROM its highly appreciated......
Looking forward for the solution
Jann F said:
Out there is a tool for recalibrating the sensor, but you would need to be S-OFF I think and it's done with a service tool (a special PG88DIAG.nbh)
Let me know if you are willing to try it, but it is VERY dangerous if you do the wrong things.
Click to expand...
Click to collapse
An update to my situation.. I ordered a new proximity sensor on e-bay and have replaced the same on my phone now. While I was at it, I cleaned up the window as it was pretty grimy and could have been the source of trouble. Also cleaned up the contacts with Isopropyl alcohol. End result.. Im still having the same problem!!
Im pretty sure now that its not a hardware problem and has to do with the calibration. What I have noticed that the sensor works fine in bright sunlight but not when there is less light around. Also am not using a screen guard!
Would it be possible to guide me to the right tools to recalibrate please?
Sorry, I haven't done this myself, but I'll search a bit how it's done by HTC.
They are using a special holding station where the devices are calibrated.
Running 5.0 on AT&T model. I have auto brightness turned on with baseline at dimmest setting which as most know is bright enough for most indoor situations. When I go outside into broad daylight, the brightness does not change. I can manually increase to full (and then the display is readable) but nothing happens on it's own.
Is this normal, am I missing something else? Defective light sensor?
EDIT: According to the following apps, I don't have a light sensor and my proximity sensor is failing. Can anyone confirm good data from them? -- Sensor Box for Android, Sensor Test, Phone Tester, Sensor Kinetics
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Ace42 said:
If your screens turns off during calls that means the proximity sensor *is* functioning. I tried a sensor test and don't see fail anywhere.
Sent from my LG-H950
Click to expand...
Click to collapse
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Neo42 said:
Yea, my screen doesn't turn off during calls (unless I knock-knock on my head/ear). Also knock on constantly turns the screen on when I have the phone in my pocket (when proximity sensor should prevent it, right?) There isn't really a "failure" in those apps per se, I am just not getting any type of change in the data from proximity sensor and I am not even getting an option for light sensor test. More or less trying to verify I have a hardware issue before trying to get a replacement or warranty service. I've only had phone for 2 days.
Thanks for the feedback.
Click to expand...
Click to collapse
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Ace42 said:
Have you tried a factory reset already and is yours rooted?
Sent from my LG-H950
Click to expand...
Click to collapse
Tried factory reset last night with no change. This phone has never been rooted (and I received it new)
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Ace42 said:
This is from the sensor app. I would conclude yours is faulty if resets aren't fixing anything.
http://imgur.com/eudDXuc
http://imgur.com/xMS0hzS
Edit: Sorry about dark screen, using screen filtering to avoid burning my eyes.
Sent from my LG-H950
Click to expand...
Click to collapse
Thanks so much for the screen grabs, this confirms my results are abnormal.