Proximity Sensor Problem

---

Hi all,

Like many of us, I managed to kill a digitizer on my HTC Aria. Replaced the blasted thing, and now I find my proximity sensor is really sensitive. It's locked in proximity mode (Z-devicetest shows distance 0) in normal conditions.

If I pull off the digitizer, so the prox sensor has a clear path in front of it, it goes out of proximity state and Z-devicetest shows the distance as 1 (and the display works properly during calls, speakerphone works, etc) ...

If I slowly move the tip of my finger towards the prox. sensor, digitizer still removed, Z-devicetest shows it flip from 1 to 0 (out of prox to in prox) as my finger gets within ~2 inches.

So it seems the prox. sensor is working but is too sensitive.

Is this the normal failure mode of a CM3602 prox sensor (read: i dropped it, and not only broke the digizer, but took out the prox sensor too!) .. or, is there some sort of calibration i need to do?

Anyone have a USA source of the CM3602? My usual suppliers digikey and mouser don't carry this component..

*curses self* shoulda listened to my friend who warned me this phone is real easy to bust

There is a guy in the accessories board that is selling parts of his aria. I'd link ya but I don't know how from this app.

Sent from my Liberty using XDA App

Right on.

I didn't want to butcher this poor little POS more so I figured out how to turn the bloody sensor off in software.

append
gsm.proximity.enable=false

to /system/build.prop

or just uncomment the line if you have an editor.. but you can just cat >> build.prop in the shell and type in the line. No editor needed.

Must do this via adb shell with phone in clockwork, otherwise nand is lokt. boo. dev eng hardware doesn't have that problem... stupid consumer devices!

So do you just start Android sdk and then type the following.

append (enter)
gsm.proximity.enable=false (enter)

or is there more to it. I really need to get this disabled.

I tried to do it with ASTRO but it doesnt save my changes.

/system/build.prop is a standard text file.

Remember that stuff in /system is protected, I find the best way to deal with the /system partition is through clockworkmod recovery.

a. Disconnect USB, reboot into clockworkmod recovery
b. Mount the /system partition from the partitions menu
c. Connect USB to a system with adb
d. adb pull /system/build.prop
e. Edit file with your favorite text editor to append gsm.proximity.enable=false
f. adb push build.prop /system/build.prop
g. unmount /system from clockworkmod recovery partition menu
h. reboot phone, receive bacon

If you don't have clockworkmod recovery, just use unrevoked to install it

Oh, i should also say CM6 (and maybe all of Froyo images?) do not honor this setting.

Thank you I will try this when I get home..
I may have an issue because if I open build.prop with root explorer it says...

# try to disable proximity sensor in call by default
# gsm.proximity.enable=false

This is located almost at the bottom of the page does this mean I am sol. It is the liberated Rom and I haven't done anything to it.

Sent from my HTC Liberty using XDA App

Just remove the # ...
# gsm.proximity.enable=false
..to
gsm.proximity.enable=false

thank you so much..... you may be oh wait you are the FN man.

ok so if froyo images dont honor this does that mean when we get froyo I shouldn't upgrade.

anyway thank you so much now I can use my phone again, I didn't realize how much my Pure was dated till I had to use it for a few days.