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.
Related
Is anyone having issues with the Tbolt hanging up by shifting the phone around during a call? This is getting frustrating as its happening a lot. I'm using BAMF 1.6.3.
Any suggestions would be appreciated!
Eric
Yes...methinks it has something to do with the proximity sensor?
Under sound settings, try unchecking "flip for speaker". It may be too sensative.
Sent from my TB using XDA Premium App
zander06 said:
Yes...methinks it has something to do with the proximity sensor?
Click to expand...
Click to collapse
My proximity sensor is horrible.
so no solutions?
pnd4pnd said:
so no solutions?
Click to expand...
Click to collapse
None that I know of yet. It is the proximity sensor, as my bolt is also plagued by this issue. Hopefully someone will take the time to adjust the sensitivity of it in a ROM so that it doesn't wake up the phone so easily while on a call.
I have that same issue. I got in the habit of hitting the home button before I put the phone up to my face. By the time I end the call, my browser or something is opened, but at least I don't hang up on the person I'm talking to.
Another solution: after the call comes in and you answer, just hit the power button. The screen will turn off (and won't turn back on until you hit the power button again).
I saw another thread about this. Someone said that lint gets into the speaker grill and messes with the sensor. Just lightly blow onto the grill to get the lint out of the way. I had issues with the screen not turning off when I put the phone to my face. This solved my issue... for now.
I hate to create a new thread for this, but creating as it didn't get the right attention in the bugs thread.
My Infuse backlight doesn't respond(on or off) to the proximity sensor when I am on a call. The backlight goes off after the preset time of 30 secs in the settings. But the light doesn't come on when I move my ear away from the phone. I have to press the power button to turn the backlight on to end the call. Proximity sensor it self works fine. Tested by covering the sensor with my finger, all the buttons are disabled even when the light is on.
Is there a way to fix this? I never had this issue with any of my Andriod phones before including the latest Inspire & Atrix.
Is this a bug with this firmware or just my Infuse issue?
Can someone please check this?
rapidstar said:
I hate to create a new thread for this, but creating as it didn't get the right attention in the bugs thread.
My Infuse backlight doesn't respond(on or off) to the proximity sensor when I am on a call. The backlight goes off after the preset time of 30 secs in the settings. But the light doesn't come on when I move my ear away from the phone. I have to press the power button to turn the backlight on to end the call. Proximity sensor it self works fine. Tested by covering the sensor with my finger, all the buttons are disabled even when the light is on.
Is there a way to fix this? I never had this issue with any of my Andriod phones before including the latest Inspire & Atrix.
Is this a bug with this firmware or just my Infuse issue?
Can someone please check this?
Click to expand...
Click to collapse
My backlight responds immediately after I pull the phone away from my face. The light turns on about the same time that I pull the phone back infront of me. The problem may be uncommon, or unique to your phone.
bragOS said:
My backlight responds immediately after I pull the phone away from my face. The light turns on about the same time that I pull the phone back infront of me. The problem may be uncommon, or unique to your phone.
Click to expand...
Click to collapse
+1. I, thankfully, haven't had any problems with the proximity sensor on my Infuse either.
Chika Da China Da Chinese Chicken?
rapidstar said:
I hate to create a new thread for this, but creating as it didn't get the right attention in the bugs thread.
My Infuse backlight doesn't respond(on or off) to the proximity sensor when I am on a call. The backlight goes off after the preset time of 30 secs in the settings. But the light doesn't come on when I move my ear away from the phone. I have to press the power button to turn the backlight on to end the call. Proximity sensor it self works fine. Tested by covering the sensor with my finger, all the buttons are disabled even when the light is on.
Is there a way to fix this? I never had this issue with any of my Andriod phones before including the latest Inspire & Atrix.
Is this a bug with this firmware or just my Infuse issue?
Can someone please check this?
Click to expand...
Click to collapse
If you answer an incoming call from a previously screen locked state the backlight does not come back on. It goes back into a screen off locked state.
If you initiate the call from an unlocked screen state, when the call ends the backlight fires up.
Thanks everyone for your response. My phone was defective, got it exchanged at the at&t store this morning & the new one is working fine!
Thank god for the carrier support!
I think I may have this same issue.
As a side note, if my phone is on speaker, and I am talking, then the other person ends the call, shouldn't my phone give some indication? Either a vibrate, a light or something?
knight4led said:
I think I may have this same issue.
As a side note, if my phone is on speaker, and I am talking, then the other person ends the call, shouldn't my phone give some indication? Either a vibrate, a light or something?
Click to expand...
Click to collapse
Yes, the backlight should come on. You might want to exchange it.
My works perfect..
Sent from my Infuse 4G using XDA Premium
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
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
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor.
Click to expand...
Click to collapse
No, mine isn't doing that. You might have a dud.
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
Click to expand...
Click to collapse
I've had that happen on my Pixel 2 XL. Only once or twice and restart fixed it every time.
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
fury683 said:
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
Click to expand...
Click to collapse
I had a case with a built-in screen protector on it and I thought that might be what was causing it but after taking it off it still did it. Weird thing though once I put it on the wireless charger it stop doing it. Hasn’t done it all day even with case on. Weird. Still thinking about taking it back to Best Buy and swapping it out.
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
tonic1080 said:
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
Click to expand...
Click to collapse
Had this very issue with my pixel XL and blowing on the top speaker grille of dust with compressed air solved it.
But if this is out of the box that sucks. It should not be like that. My pixel was approaching two years when that happened.