• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Proximity Sensor Issues

brettlewis

brettlewis

Android Expert
I have been having this issue for quite some time, but just figures it was a bug in one of the BB roms I was using. Well, since then I have been through about 10 different versions of bugless beast, droid mod, and several others.

My issue seems to be that when I make a phone call and put the phone next to my head, although the screen turns off, the touch is still activated.

I will be in a call and I will feel the phone vibrate against my head. I usually hit the pound of star key on the phone, and as soon as buttons are pressed in a call, it seems to mute my voice to the person on the other side of the call. I have to remove the phone from my face, wait for the sensor to realize i moved my face, and have to press the backspace button till all the random characters are deleted at which point the person on the other side can hear me again.

This happens to me on about 80% of my calls, and is by far the most frustrating issue I have had.

Do you think I should re-install stock and bring it in? :confused:

btw, I posted this in root sub-forum cause I am rooted, and wasn't sure if it was just a rom issue.
 
brettlewis said:
I have been having this issue for quite some time, but just figures it was a bug in one of the BB roms I was using. Well, since then I have been through about 10 different versions of bugless beast, droid mod, and several others.

My issue seems to be that when I make a phone call and put the phone next to my head, although the screen turns off, the touch is still activated.

I will be in a call and I will feel the phone vibrate against my head. I usually hit the pound of star key on the phone, and as soon as buttons are pressed in a call, it seems to mute my voice to the person on the other side of the call. I have to remove the phone from my face, wait for the sensor to realize i moved my face, and have to press the backspace button till all the random characters are deleted at which point the person on the other side can hear me again.

This happens to me on about 80% of my calls, and is by far the most frustrating issue I have had.

Do you think I should re-install stock and bring it in? :confused:

btw, I posted this in root sub-forum cause I am rooted, and wasn't sure if it was just a rom issue.
Click to expand...

If it happens with every rom you try...I'd take it back. I have never had an inadvertent keypress while on a phone call...never. If it was happening all the time to me, that would be a big problem.
 
UBRocked said:
If it happens with every rom you try...I'd take it back. I have never had an inadvertent keypress while on a phone call...never. If it was happening all the time to me, that would be a big problem.
Click to expand...

fanx.

heres your prize
cats-kitten-sink.jpg
 
I just attempted to stock my phone and now im stuck in the infinite boot loop.
Its completely uprooted, but not doing anything. How do I go about fixing this?
 
Shadowtech said:
You could try the SBF method posted here and go completely back to stock/factory install and see if the problem still exists.

http://androidforums.com/all-things-root-droid/47349-now-you-can-live-without-fear-bricking.html

Unless that's what you already meant by stock.. in that case.. not sure.
Click to expand...

Agreed. Your un-rooting anyway...Using SBF will get rid of all traces that you ever rooted. Nice pic by the way...my cats are less cute and more of a pain in the ass! Haha!
 
UBRocked said:
Agreed. Your un-rooting anyway...Using SBF will get rid of all traces that you ever rooted. Nice pic by the way...my cats are less cute and more of a pain in the ass! Haha!
Click to expand...

hm. all I did was use droid mod and used the stock option. It booted up the first time, but none of the hardware buttons were working and most of the apps were busted.

I did a battery pull, rebooted into a boot loop several times.

started up by holding down x, did the cam and volume up, and pressed "set to stock" or something like that. so I think it wanted me to clear the cache or something. It worked after that.

I guess Ill see what happens when I go in tomorrow.
 
they wouldnt replace it based on the sensor. told me to "wait one week till 2.1 came out"

however, I showed them my broken keyboard key and they replaced it based on that. sweet :D
 
You must log in or register to reply here.
Back
Top Bottom