Database Info

Huge proximity sensor problem

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.

broken proximity sensor

So I have been having this issue lately where after calls, my phone's screen wouldn't wake up.
I just discovered that I may have a broken proximity sensor?!?
I've been trying different roms and such to see if it would help and finally decided to download some tools that measure and adjust the proximity sensor and noticed that it will discover "far", then "near", but gets stuck on near.
Can anyone confirm that on their Sensations, it goes back to "far" when your phone is moved away (or you move your finger away)?

What kernel are you using?

StefanB86 said:
What kernel are you using?
Click to expand...
Click to collapse
Currently, Faux with Revolution. Tries IC with stock as well. Same thing.
The strange thing is that if I restart the sensor app, it will go back to default.

That's weird. I was asking because if I'm not mistaken, bricked kernel was having wake up issues that were fixed on the latest beta.
Would you mind giving me the name of the app that you are using to test the proximity sensor so I can tell you what I'm getting?

StefanB86 said:
That's weird. I was asking because if I'm not mistaken, bricked kernel was having wake up issues that were fixed on the latest beta.
Would you mind giving me the name of the app that you are using to test the proximity sensor so I can tell you what I'm getting?
Click to expand...
Click to collapse
Proximity Sensor, Androsensor and proximity recalibrator (doesn't seem to work, which also leads me to believe it may be borked).
What happens in Proximity sensor is that when i cover it, it will report 0, then stay stuck there and says that it's covered. If I restart the app, it seems to reset.

This seems to work correctly for me. The app I am using is AndroSensor, it only shows 2 readings, 0.0 and 3.5 inches, which I assume would be equivalent to near and far. I noticed that if I quickly wave my finger across the sensor, sometimes it will change to 0 and not go back to 3.5. However, if I move my finger over the sensor, wait a half second, and remove my finger, it will always jump back to 3.5.

Louer Adun said:
This seems to work correctly for me. The app I am using is AndroSensor, it only shows 2 readings, 0.0 and 3.5 inches, which I assume would be equivalent to near and far. I noticed that if I quickly wave my finger across the sensor, sometimes it will change to 0 and not go back to 3.5. However, if I move my finger over the sensor, wait a half second, and remove my finger, it will always jump back to 3.5.
Click to expand...
Click to collapse
Yeah. The problem is, mine stays at 0.
May have to restore to factory settings and send to HTC...

Are you wanting the proximity sensor to work as it should, or are you simply wanting the screen to stay lit when on a call? If you just want it to stay lit, install an app called call light. I briefly had a HTC hero, which had no proximity sensor but the screen still went off during calls. That app allowed it to stay on.

StuartTheFish said:
Are you wanting the proximity sensor to work as it should, or are you simply wanting the screen to stay lit when on a call? If you just want it to stay lit, install an app called call light. I briefly had a HTC hero, which had no proximity sensor but the screen still went off during calls. That app allowed it to stay on.
Click to expand...
Click to collapse
I want it working properly. Screen off during calls, and back on when off.

Do you use a case?
Sent from my HTC Sensation 4G Running Bulletproof

http://forum.xda-developers.com/showthread.php?t=925814&page=3 #25
http://forum.xda-developers.com/showthread.php?t=1658474

Screen Turns Off While on Phone

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

Display issues

It is normal for display to go blank due to proximity censor while making calls. In my case however,occasionally the display stays blank even after the call gets over. This also happens every now and then when I lock the phone, only to never unlock. At times, the displays backlit switches while unlocking but not all the time. The phone's processor stays awake in both the cases (calling/locking) and the phone rings & vibrates perfectly on making calls. The only option that I have in such cases is to restart the phone. Is anyone facing similar problems with their phones? I've done a factory reset off late but still the problem persists.

Are you using a screen protector? May be you haven't aligned it properly and hence proximity sensor detects it and turns off the display??

I've had similar situations happen to mine, but I figured out that after a Skype call on my phone, the proximity sensor will remain active and will sleep the screen if something's covering it. I'm not sure if you have skype running, but if you do, that might be why.

vin4yak said:
Are you using a screen protector? May be you haven't aligned it properly and hence proximity sensor detects it and turns off the display??
Click to expand...
Click to collapse
I don't think obstruction of the proximity sensor is an issue since this problems occurs even when I lock and then try to unlock the phone. Also the backlit turns on at times when I try to unlock the phone.

combatshadow said:
I don't think obstruction of the proximity sensor is an issue since this problems occurs even when I lock and then try to unlock the phone. Also the backlit turns on at times when I try to unlock the phone.
Click to expand...
Click to collapse
Well, what you're facing right now is a classic example of what people face when they keep on the protective covering used on a new phone when the phone is shipped.
If you think it's not the issue then search for any apps which you might have installed? Run the phone is safe mode and see if it acts up? Flash stock images or do a reset to rule out the possibility of a software issue.

vin4yak said:
Well, what you're facing right now is a classic example of what people face when they keep on the protective covering used on a new phone when the phone is shipped.
If you think it's not the issue then search for any apps which you might have installed? Run the phone is safe mode and see if it acts up? Flash stock images or do a reset to rule out the possibility of a software issue.
Click to expand...
Click to collapse
After few days of working flawlessly, today again the display blanked out while it was locked in normal mode. I tried unlocking the phone but only the backlit would light up. So I restarted the phone, activated the safe mode as suggested by you and then few minutes later, again the display blanked out. What should be the next step now? Please elaborate on flashing stock image. I've earlier done a factory reset but I immediately installed all the apps.

combatshadow said:
After few days of working flawlessly, today again the display blanked out while it was locked in normal mode. I tried unlocking the phone but only the backlit would light up. So I restarted the phone, activated the safe mode as suggested by you and then few minutes later, again the display blanked out. What should be the next step now? Please elaborate on flashing stock image. I've earlier done a factory reset but I immediately installed all the apps.
Click to expand...
Click to collapse
Well, if you're facing the issue in safe mode as well, any apps might not be causing it. To flash factory images, you will need to unlock the bootloader. Follow the guide which is linked in my signature.
Since you don't know about how to flash stock images, I assume you haven't rooted and undervolted? Display black outs while unlocking the device can be caused due to undervolting as well.

It could be a hardware problem on the phone I had before the n5 with my lg g2
Sent from my Nexus 5 using Tapatalk

Possible, but he should exhaust all software options before seeking out a replacement.
Sent from my Nexus 4 using XDA Free mobile app

Proximity sensor issue

As I unbox n started using my brand new Samsung S8+, i am having this popup re the proximity sensor being blocked or something. Is this a firmware issue or hardware issue? Thanks if anyone is willing to entail their story re this matter, any fix would be of good help. Sorry if this question is being raised in this thread.

The proximity sensor is left to the earpiece, and right to the IR LED (the red IR sensor used with Iris scanner).
Is that area covered with anything? Screen protector, dust, whatever?

Skander1998 said:
The proximity sensor is left to the earpiece, and right to the IR LED (the red IR sensor used with Iris scanner).
Is that area covered with anything? Screen protector, dust, whatever?
Click to expand...
Click to collapse
I find this popup whenever I take the phone out of my pocket. So because of that the proximity sensor is blocked? Its covered by my pocket. But what is the solution. Its draining battery.

ifran13 said:
I find this popup whenever I take the phone out of my pocket. So because of that the proximity sensor is blocked? Its covered by my pocket. But what is the solution. Its draining battery.
Click to expand...
Click to collapse
That's odd, can not replicate.

Not an issue with software or hardware and its not draining your battery, LOL. It's a feature mate. You likely have "Keep screen turned off" enabled in your display settings. It uses your proximity sensor to turn off the screen for you if it senses that the phone is in a pocket or bag. I think it will throw up a dialog box if it gets triggered, that's probably what you're seeing.

xeathpk said:
Not an issue with software or hardware and its not draining your battery, LOL. It's a feature mate. You likely have "Keep screen turned off" enabled in your display settings. It uses your proximity sensor to turn off the screen for you if it senses that the phone is in a pocket or bag. I think it will throw up a dialog box if it gets triggered, that's probably what you're seeing.
Click to expand...
Click to collapse
Thanks mate. That makes lot of sense to me now! Lol. Why ddnt I think of that, must have slipped off my mind haha

I also have an S8 and while i am talking on the phone the screen lights up and vibrates,no reason,no message nothing.It's annoiyng i can't talk on the phone calmly because of this.Anyone with the same issue?Thanks

Many thanks it s very useful for me