Root [rooted] proximity sensor since jelly bean

[talevo]

I see thread or 2 on here dating pretty far back about proximity sensors. I've only had the issue since we went jelly bean. Currently on Viper 3.0.1, was on MeanBean and stock. Full wipes between roms, including SD card.

The issue is, I can be on a call and I can see the screen blinking on and off and I'm not even moving the phone away from my face. When I actually pull the phone away from my face to end a call, the screen goes blank and I have to get it back on to end the call. It's clearly the sensor because I can put my thumb over it and make the screen come and go. I've had a screen protector and otterbox on since day one and had no issues until the latest official software update. I saw a thread on android central where people mentioned they made the sensor more sensitive. Is this true? How do we revert it back so the phone works like it should again?

 

[-Mike-]

I have the same prob. Drives me crazy. I wish there was/is a way to fix it. I'm currently on MeanBean 3.4 but it has always been an issue for me.

 

[ocnbrze]

no issues on aosp roms for me. i wish i could help you guys with it, but i'm more of an aosp guy as i have never really been a big sense guy.

does this happen with only this rom? or have you tried others?

 

[talevo]

It happens on stock, MeanBean, and latest viper. Worked perfectly fine before JellyBeans! It's so annoying but I haven't had any time to do more research on it. The odd thing is the last update says improvements to proximity sensor. Mine didn't need any improvements because it worked just fine before!

 

[ocnbrze]

It happens on stock, MeanBean, and latest viper. Worked perfectly fine before JellyBeans! It's so annoying but I haven't had any time to do more research on it. The odd thing is the last update says improvements to proximity sensor. Mine didn't need any improvements because it worked just fine before!

are you s-on or s-off? i wonder if the new touch panel from the latest firmware might help.

 

[talevo]

S-OFF

Hmm, this may actually be my own negligence causing this. I thought I was on the latest but ##786# shows

SW version: 3.15.651.16 CL124461 release-keys
radios: 1.12.11.1119

So I guess I'm not up-to-date!!

Capt throwback says to only update if you're using a rom that's compatible with 3.16.651.3. I assume the latest Viper is compatible with the latest firmware update? Looks like I got more checking and possibly updating to do. So odd, thought I was on the latest..

 

[ocnbrze]

S-OFF

Hmm, this may actually be my own negligence causing this. I thought I was on the latest but ##786# shows

SW version: 3.15.651.16 CL124461 release-keys
radios: 1.12.11.1119

So I guess I'm not up-to-date!!

Capt throwback says to only update if you're using a rom that's compatible with 3.16.651.3. I assume the latest Viper is compatible with the latest firmware update? Looks like I got more checking and possibly updating to do. So odd, thought I was on the latest..

yep the latest viper is compatible and recommended to be on the latest firmware. however, tp has been removed. but, he has added it separately if you like to flash it.

 

[talevo]

Well, I've been latest on this since last post and it doesn't seem much better. It almost feels like landscape mode along with the cpu scaling effect the weirdness. It probably just makes it more apparent but again, didn't have any of the issues prior.

 

[dustwun77]

Do you happen to have any sort of screen protector that could be interfering with the sensor? Have read where that was the problem for some.

I have been on all of those roms and haven't noticed the issue.

 

[Blewis13]

I'm also using the latest Viper. I've noticed that the proximity sensor works fine if you keep the auto rotate screen off. If you have it on and are in a call and tilt the phone to rotate the screen I have the proximity problem. If I keep the phone straight and don't tilt it is fine. Turning off the auto rotate will completely fix the proximity sensor but you lose the ability to rotate the screen during any application.
I know that one of you incredible folks out there can come up with a solution to this problem. Get working!