[Q] g-sensor and light sensor still can not work,please help me~~! - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

please help me everybody~~~my phone still can not work g-sensor,light sensor and automatic shut-screen when i calling. i have try all new versions or wm rom,radio.but still can not work too. but they can use well in wm. so i don't what de matter,please~~thank you~~sorry for my poor english~~~

---

Please post your build and rom information, preferably compactly in your sig.
Did you try to calibrate your g-sensor? This can hose some builds.

---

dbh369 said:
Please post your build and rom information, preferably compactly in your sig.
Did you try to calibrate your g-sensor? This can hose some builds.
Click to expand...
Click to collapse
i did try calibrate my g-sensor,but it can not work too.
my ROM is ChuckyDroidROM,
Radio: 2.12.50.02_2,
build: NexusHD2-FRG83 V1.5 PPP + RMNET (Android/Froyo 2.2.1).
i did try too many build,such as FroyoStone_Sense_V3.2,d4_Sense_Classic,Mdeejay eVo Sense v. 1.1 Warm,Mdeejay eVo Sense v. 1.8 Revolution.but none of them can fix my problem.......wm rom driver i have try 3.14,2.14.2.10,1.80。radio i have try 2.08,2.10,2.12,2.14,2.15 too.....so i relly don't know what the problem i have.

---

Many people said never calibrate the g-sensor inside Android....
So if you already do so, you can try to follow the instruction on a thread here focus to fix the g-sensor
Sent from my HTC HD2 T8585 using XDA App

---

ctrlaltdel said:
Many people said never calibrate the g-sensor inside Android....
So if you already do so, you can try to follow the instruction on a thread here focus to fix the g-sensor
Sent from my HTC HD2 T8585 using XDA App
Click to expand...
Click to collapse
i have try many method...Even the first time just entering the android is still not available g-sensor,lisht sensor too....

---

i also have this problem, g-sensor seems to work fine but light sensor never worked in android for me.it doesn`t matter what android build,wm rom or radio i`m using it doesn`t work. Now I have mdeeja 1.8 revolution on VBN ROM reloaded*2 with 2.15 radio and it`s doesn`t work

---

Yes, if you run the calibration sequence in android, you lock it gain numbers taht are too high and the g-sensor goes unusable. I don't know why you are getting that specific error, but two possibilities:
1) you are not getting a good initiation from WM before booting Android
If so, you need to wait a bit before running clrcad and haret
2) the calibration messed you up.
If so, there's a thread on how to undo that, but I don't remember where (search android general I think). Or you will need to rebuild android since this data is stored in your dataimg.
Otherwise, it sounds like it might be hardware related, and you need a new phone.
editted: I've never used a Nexus build, so I would try an EVO. I would also reformat the sd card and go with a clean install just to see. You can tell real quick if it is working be opening email and turning sideway. If the screen autorotates, you have g-sensor. It is possible you have a disabled g-sensor too as that was a common way to address the bad g-sensor response in the early builds. Again a complete clean re-build might find this issue.
If I remember correctly, Chucky boots you straight into Android, you might try a different ROM and see if that helps...
My $0.02...

---

I have the same problem，too！I try all kinds of wm rom and Android rom！It always didn't worked on the Android，but work perfect on the WM！

---

dbh369 said:
Yes, if you run the calibration sequence in android, you lock it gain numbers taht are too high and the g-sensor goes unusable. I don't know why you are getting that specific error, but two possibilities:
1) you are not getting a good initiation from WM before booting Android
If so, you need to wait a bit before running clrcad and haret
2) the calibration messed you up.
If so, there's a thread on how to undo that, but I don't remember where (search android general I think). Or you will need to rebuild android since this data is stored in your dataimg.
Otherwise, it sounds like it might be hardware related, and you need a new phone.
editted: I've never used a Nexus build, so I would try an EVO. I would also reformat the sd card and go with a clean install just to see. You can tell real quick if it is working be opening email and turning sideway. If the screen autorotates, you have g-sensor. It is possible you have a disabled g-sensor too as that was a common way to address the bad g-sensor response in the early builds. Again a complete clean re-build might find this issue.
If I remember correctly, Chucky boots you straight into Android, you might try a different ROM and see if that helps...
My $0.02...
Click to expand...
Click to collapse
I do not think a hardware problem, because they can work well on wm,just can not work on android...all of your method i have try again...but still can not work...I'm going crazy...but the Compass can not work, in wm always point on 6076 or 101,in android can not move....

---

no sensors
same problem. i tried ozy,vbn with 2.10, 2.12, 2.14 and 2,15 radios (with >12 i got ~57mA batt drain) with many sense (mdeejay clean 1.1, evo 2.0, desirehd) / cm6 (jdms, subcraft, hyperdroid) based builds without any success. I always calibrated gsensor and waited for a fixed gps before booting into android.
I'm keen to help to fix but someone should tell how to debug
R, Janos