Alright, so the Proximity Sensor in my Rezound is seriously driving me nuts. It is erratic, sometimes keeping the screen on and other times immediately turning the screen off, even when I turn it back on.
I can't enter credit card info, for example, into a phone system because the display keeps shutting off.
I couldn't find any build.prop edits to do the trick. I am on latest CleanROM Dev Edition with the latest RUU. I tried the app "Screen On", as well as the app "AppAutoSettings Beta". Neither of the apps works for me on the Rezound.
Any ideas? I would love the disable the sensor or override it so I can power the display on and off as I see fit during a call. The sensor on my Droid Charge works totally fine.
I'd much rather not get a replacement. I just want to accomplish my goal of disabling bypassing the sensor somehow.
Thanks!
**EDIT**
I found that this method works! So far I haven't had any problems.
http://forum.xda-developers.com/showthread.php?t=1626611
Just add this to your build.prop:
gsm.proximity.enable=false
My phone's irritation factor just dropped substantially. I take no credit for the method. I am highly curious what other devices this would work with.
Your sensor might be bad. I had the same thing happen to mine had to get a replacement. It happens because dust easily gets into the the speaker grill. You can try and blow compressed air in the grill and blow it out but it might be to late you might have to get a replacement.
Sent from my Sense4 ICS Rezound
LakerStar25 said:
Your sensor might be bad. I had the same thing happen to mine had to get a replacement. It happens because dust easily gets into the the speaker grill. You can try and blow compressed air in the grill and blow it out but it might be to late you might have to get a replacement.
Sent from my Sense4 ICS Rezound
Click to expand...
Click to collapse
Thanks for the reply, although I did figure that already. I don't really like the feature anyways and prefer to control it manually.
My pursuit of sensor disabling shall not be in vein!
I tried using this method, but I can't find the name of the proximity sensor driver.
http://forum.xda-developers.com/showthread.php?t=1683884
Related
So since I've moved to CM7 I keep hanging up on people when I am trying to hold my phone between my ear and shoulder because my jaw bone hits the end button. I don't recall this happening ever with Blur. Is there a prox sensor that is supposed to disable the phone when it's up against your face? Where is this setting in CM7 or is it just an issue of buttons being in slightly different places w/ CM7 than with stock? If so, is there a phone replacement app that anyone could suggest?
Have you tried turning the screen off (via the power button) before holding it to your face? That was something I desperately wished I could do on my old Moment, because its proximity sensor sucked, but the power button served double duty as the end call button.
Interesting idea. I didn't consider trying that. I also noticed under Call Settings an option "always use proximity sensor" which I enabled and will try. Maybe my phone thinks it's horizontal when I hold it that way.
It is a vertical horizontal thing I believe. Phone needs to be pretty much vertical for the proximity sensor to come on. You can test this in a dark room. Call a number and watch the sensor illuminate. It should look like a red dot near the earpiece. Then move it towards horizontal. You should see it cut off.
Sent from my MoPho. All typos are the phones fault.
ypu may need to do another fresh clean install. completely wipe everything then flash the rom again?
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
jeggen said:
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I was just going to mention that. I found the setting while tooling around in the cm7 settings. Glad you got it fixed.
Sent from my MoPho. All typos are the phones fault.
will give that a try. im having same issue on cm7.2
Does anyone else have this problem? On previous CleanROM builds and now on the latest ICS leak I have to turn the power on to see my screen. It is very frustrating when wanting to hang up or mute and unmute calls.
thanks.
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
mjones73 said:
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
Click to expand...
Click to collapse
Interesting. Thanks for the response.
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
tCizler said:
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
Click to expand...
Click to collapse
Not seeing any issues like that either. I was on a 40 min call this morning where I had to dial in an access code after making the initial call, I was able to mute/unmute multiple times and towards the end I was checking my email and facebook before it was over without any lock ups or anything.
I cannot find a setting for using the proximity sensor during phone calls. I thought my old EVO had a setting like this!?
I am having the same issue. Proximity sensor shuts the display off, but doesn't turn back on after moving away from head.
Started with latest "official" leak. 3.14.605.5 71ORD
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Thanks for the response. I am gaining confidence that it is not my phone.
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
jayochs said:
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Click to expand...
Click to collapse
I have had mixed results. Seems to be better after a reboot.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
If you really want to know whats causing it, make a phone call while you're plugged into your computer, and run logcat. It will show you whats going on with the prox sensor.
flying_pigs said:
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
Click to expand...
Click to collapse
No but I was thinking about trying it, but it's a lot of work just to test it.
Sent from my ADR6425LVW using Tapatalk 2
works fine here too... fully stock 3.14 leak, frozen bloatware.
I had this problem and like the rest of you thought it was the rom/leak I was using.
It wasn't. The HTC proximity sensor is extremely sensitive. It is right above the left end of the checkmark next to the verizon logo at the top of the phone.
If you are using a screen protector and it does not have a cutout for the proximity sensor, you're going to cause problems. I used both a crystal clear, then an anti-glare screen guard and even though they are obviously quite clear they both screwed with the proximity sensor.
I found the RND Power Solutions screen protectors DO have a cutout for the sensor and work flawlessly. No more issues.
I have this problem too I'm on the .22 ICS leak if I go back to GB it works fine might try the 5/7 leak and see if it happens on that.
Sent from my ICS Rezound
I had this problem but then soon realized it was my screen protector.
I would get a call and as soon as I answered it, without even putting my phone to my ear, the screen would shut off.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Well, i stand corrected... I took my screen protector off, no luck. I reverted back to GB, no luck. I downloaded several sensor testing apps and all said the proximity sensor was dead. I got a "new" phone coming in the mail tomorrow. As much as i didn't want to hear it was a hardware issue, you were correct. And after a very easy google search apparently this is almost an epidemic with the rezound. Oh well, here's to hoping my replacement doesn't have way more problems than just a proximity sensor.
Thanks again flying_pigs
Rezound is S-0ff.
Makes calls and allows view of keypad during calls fine with G-Bread.
However;
Did latest ICS leak, and phone won't stay lit AT ALL during calls.
Can't press "3" now because I can't see it anymore. Sometimes have to
pull the battery to get out of a call.
Last nite late I reinstalled my last nandroid of GB after doing 2.01RUU.
And now the proximity sensor is fine again.
Do any of you ROMmers have an idea, or is this specific to 1 phone?
A lot of people have reported issues with dust in the sensor, me being one of them. I piped my phone open to recolor the softkeys, and cleaned out the sensor while I was in there. Now it works great. Maybe it is just a difference in the way the two use the sensor? Try blowing it out with compressed air.
if could be that the rom you are using has a ro.rill that may delay blackscreen i was testing my rezound today and figered that out
GrayTheWolf said:
A lot of people have reported issues with dust in the sensor, me being one of them. I piped my phone open to recolor the softkeys, and cleaned out the sensor while I was in there. Now it works great. Maybe it is just a difference in the way the two use the sensor? Try blowing it out with compressed air.
Click to expand...
Click to collapse
I did the exact same thing and it worked. After I installed ViperRez the phone would sometimes stay lit going towards my ear, then go dark when I took it away. Pretty much opposite the way it's supposed to LOL. Then I read (on XDA) about dust getting in the sensor area, just below the earpiece speaker just below the speaker and a little to the left of the Verizon V logo. I wiped it clean, then when I got home I CAREFULLY blew it out with compressed air, and that did the trick. I haven't had the problem since.
I noted each time I make a call, the display immediately turned black. It auto turn black without me even taking up the hone up to my ears. I needed to press the power switch to have the display lit up again. Is this a proximity sensor defect ??
Same issue
mobile88 said:
I noted each time I make a call, the display immediately turned black. It auto turn black without me even taking up the hone up to my ears. I needed to press the power switch to have the display lit up again. Is this a proximity sensor defect ??
Click to expand...
Click to collapse
Yea I'm dealing with the same issue on my at&t model, it's definitely a proximity sensor issue. Also, I find that the proximity sensor functions relatively OK outside of the phone app when I'm on a call in terms of lighting of fading to black...I haven't found a fix yet, hopefully it's a software issue though somethings telling my it's not... Just another defect in a long line of LG phones as of late
Applez2androidz said:
Yea I'm dealing with the same issue on my at&t model, it's definitely a proximity sensor issue. Also, I find that the proximity sensor functions relatively OK outside of the phone app when I'm on a call in terms of lighting of fading to black...I haven't found a fix yet, hopefully it's a software issue though somethings telling my it's not... Just another defect in a long line of LG phones as of late
Click to expand...
Click to collapse
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
thebiker said:
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
Click to expand...
Click to collapse
I've cleaned it several times to no avail
I have noticed occasional "quirkiness" while in the phone app, but not to the point of requiring a battery pull. Example, connected via Bluetooth, while plugged to a charger in a call, no way to wake the phone without pulling the charger.
Sent from my VS990 using Tapatalk
thebiker said:
I have a same issue but clean the proximity sensor and it will work. The proximity sensor is next to the speaker. Clean with your t-shirt or jeans.
Click to expand...
Click to collapse
Thank you. Thank you. Your proposed solution works very well. Now no more this problem. Had never thought the sensor could be dirty or blocked over time. I had the phone only about 2 months
Problem update
Okay, I've found new info on the proximity sensor problem. Firstly, I noticed that my proximity sensor still works with the second screen, if I cover it up when my screen is off it goes black and comes back on when I remove my finger. Secondly, if I was on the phone but not actually in the phone app it would behave normally sometimes. Now today I found out that when I'm in the phone app, if I'm talking on the phone through the speaker the screen does not go black, as soon as I take it off speaker, the screen goes immediately blank. Still have not found a fix, but just more info that may help define what the actual problem is.
anyone have any update on this? this issue seems to be getting worse for me
Same issue, drives me nuts. This phone is a disappointment to me overall. Have an S7 on pre-order with Verizon. Can't wait to get my hands on it!
Had same issue just happen on the AT&T LG Escape 2. (Yes I know its a year since this thread was started)
It was the proximity sensor but the "T-shirt wipe" method didn't work for me.
What I did realize there was some gunk on the sensor, and I used a cotton swab (Q-tip) with alcohol and rubbed it till it was visibly clear of gunk. Now it works fine again..
odesskiy said:
Same issue, drives me nuts. This phone is a disappointment to me overall. Have an S7 on pre-order with Verizon. Can't wait to get my hands on it!
Click to expand...
Click to collapse
Turn of Gestures
Was facing the same issue
Went into settings
Call
Turn of both gestures auto answer and flip to silence
Another thread about this stupid sensor.
My screen goes black when I call or answer a call. If I use a headset sometimes randomly the screen comes on or stays on when I answer a call.
The proximity sensor is working. Looking in *#*#7378423#*#* > Service tests > Ambient Light Sensor.
Putting it to a lamp gives a value of 10.0 and putting my finger over the sensor gives 0.0 .
So its working.
This seems to not be rom related if not for the change after Android 4.4. I flashed roms from cm-12.1-20161016-NIGHTLY-togari.zip, AOSP_N_161207_togari.zip and now I am on hybrid_concept_edition_2.0.zip.
I do have a screen protector on. But with a hole for the sensor. Its not dirty in that area. And the sensor worked fine way before I installed it.
This started happening during the last two months or so.
I tried numerus of apps from play store. None did anything. Of course I could force the screen to be on. But with the risk of pushing some buttons when I'm in a call.
My temporary fix so far has been to enable end call with power button
Do you have any idea what to do?
Thank you
I'm facing this same problem, I'm on stock.
hypergp said:
I'm facing this same problem, I'm on stock.
Click to expand...
Click to collapse
yup.. I had mine apart today. But you need to remove the battery in order to flip the motherboard around to get to the connector.
I don't have time for that. Perhaps the battery will explode if I try to remove it..
So I cut a piece of foam plastic to fit around the usb connector so there is a constant pressure applied to the motherboard when screwed down the NFC antenna because there is a screw just around this area that sets the NFC antenna in place.
Hang on. I just made a call just for the sake of it that you answered to my thread and it freakin works!!!!!!!!!!!
I got the idea from this guy/gal: https://forum.xda-developers.com/xp...olution-proximity-sensor-fix-z-ultra-t3595525