Hi all !
My proximity sensor stopped working after 1 month with no apparent reason . I did search the forum for the people with a similar problem and I found that there are so many and no real solution .
Could this be a hardware fault? What should we do next?
My ROM is 1.43 WWE , no screen protector installed , in the registry the lightsensor is ON .
Thank you in advance !
Well, today I tested it with hair and it didn't work at all.
So can this be the case with your HD2 ?
No, its not that either ... Now it acts strange , sometimes I push the red button for ending a call but no effect while all the others buttons are working well and I have a huge battery drain
I've done various postings on the subject.
The latest is here http://forum.xda-developers.com/showthread.php?t=605956
bump................
My sensor was a bit weird (didn't work occasionally or did the Christmas lights jingle) with the 1.43 ROM but now with 1.48 I have no problems with it whatsoever.
I think that I`m gonna reflash ... Thank you guys !
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
Dont know if this helps...but I had my Hd2 screen replaced few months back...and dont have this problem... screen is much better than before though with beter colour saturation....check with HTC as this might be an error on their part..
Sent from my HTC HD2 using XDA App
G-Sensor Not Working after Screen Replacement
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
I have this same problem with one of my HD2's that had the screen replaced.. Everything works perfectly except the "G-Sensor"...
I posted the problem in this thread http://forum.xda-developers.com/showthread.php?t=902129 a while ago, and been watching ever since... Havent seen any solutions, but more reports of the same problem been added to it daily... I'm also assuming that they changed the G-Sensor hardware along with the screen... Beacause it works perfectly in WinMo, and it dont in none of the Android Builds I've tried (CMYLXGOs all versions, Imilka's all versions, RAFDROID, CyanogenMod, etc)...
Everything works good on my Primary HD2, no problems at all... I'm hoping some Chef/Kernel developer might just take some time to check this out...
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
T-Macgnolia said:
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
Click to expand...
Click to collapse
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
cmcmyers said:
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
Click to expand...
Click to collapse
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
T-Macgnolia said:
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
Click to expand...
Click to collapse
It's a good point You have there... But I would be assuming that was the problem if the G-Sensor wasnt working in Windows Mobile... Everything works perfectly in WinMo, including the calibration... Thats another reason we have come to believe its a hardware upgrade or something similar...
I have the same problem. I bought an HD2 from someone in the Marketplace, and I can see from the pry marks on the bezel and the broken adhesive that the screen had been replaced at one point. I also believe there must have been some hardware revision that is still compatible with WinMo, as the same driver works unilaterally, but not with Android. Definitely tried most of the recent ROMs and different combinations of kernels, and cLK/MAGLDR, but it never works.
Charnsingh alludes to the G-Sensor code in the kernel in his [DEV] thread here: http://forum.xda-developers.com/showthread.php?t=1049170 (don't post unless you're a dev though), and says that it's pretty minimalistic. So maybe there's a solution out there, but the developers haven't gotten to the bottom of it. I'm watching that thread intently to see if there's anything cooking or if there's something I can help with.
I think there are quite a few users who are suffering from this.
If the devs need anything they have plenty of people to ask for debug info, etc.
I just wish someone had the time to have a look at this
have got the same issue, new screen, sensors stopped working, all the sensors that is, light, proximity, g-sensor, compass. and everything works in winmo (except the compass, don't know why) the interesting thing is, the proximity sensor does work, it just doesn't turn off the screen, but it does turn off the touch screen, and the g-sensor actually seems to work, i can calibrate, and the relevant files are updated (in /data/misc the bma150_usr and the akmd files are created and/or updated) and if i move during calibration, it is aborted. it seems as if there is something broken in software because the chip data is still being read and used somehow, just not piped to the right places...
Every sensor work fine here with except the g sensor
I guess its a kernel issue and not hardware relates
it work perfectly on wm6.5,but not work on any andriod rom.
i have the same issue
so no one is helping us???
i have the same issue too...
Same here works fine in windows but android will not work.
Also have screen replacement
SOLVED
my issue is solved now after motherboard replacement.
a few notes:
- as i eventually discovered, there was in fact a problem with the compass (aka the magnetic field sensor) which didn't work in any os. with this issue i had a good reason to send the phone back to the repair shop and they replaced the motherboard under warranty.
- i don't know what solved the issue, it's either [A] the working compass (which is somehow needed for auto-rotation to work - in android) or the new motherboard (which does not have compatibility issues with the new screen - in android).
so, please check wheather your compass is working or not.
if not, reflash to stock and send it back for a warranty repair.
I replaced the digitizer in my phone myself and the G-sensor works for me in Android.
LOOOOOOOOOOOOOOOOOOTS of threads and posts since 6 months and still nothing. About those sensors problems / screen replacements and still nothing... It's so sad, the HD2 is dying slowly. Lolz, let's keep the faith!!
+1 same problem...
Any solution???
Thx.
Same.
perfect on Windows.
not working, gyroscope, compass, screen rotation on any android.
no problem with proximity and light sensors.
I had tried screen rotations witout main flex (that holdss, vibration, camera, volume, wifi, buzzer)
And the sad point is I had replaced LCD-Digitizer together these are taken from a dead hd2. So my replaced LCD is 100% orijinal. I did not seperate chasis-button flex also.
Hi,
I own HTC HD2 and recently it stoped working and i had to send it to be repaired. They have changed the board because the CPU has malfunctioned. Since then accelrometer is not working in any rom. It only works in Windows. I could not find any answers except that the new board installed could be unsupported in android builds.
Any help is appreciated.
Help
duh2010 said:
Hi,
I own HTC HD2 and recently it stoped working and i had to send it to be repaired. They have changed the board because the CPU has malfunctioned. Since then accelrometer is not working in any rom. It only works in Windows. I could not find any answers except that the new board installed could be unsupported in android builds.
Any help is appreciated.
Click to expand...
Click to collapse
I also found out that several more users in Serbia have this issue. Anbody else? Plese help?
This is a Driver issues, maybe the new board has some different Component, but is not only the g-Sensor, the Magnetic Field and Orientation aren't Working, this kind of problem take to long time to be fixed, now that the developers are Focused on ICS. I'm thinking to sell my HD2 and Buy Another one.
ataria2 said:
This is a Driver issues, maybe the new board has some different Component, but is not only the g-Sensor, the Magnetic Field and Orientation aren't Working, this kind of problem take to long time to be fixed, now that the developers are Focused on ICS. I'm thinking to sell my HD2 and Buy Another one.
Click to expand...
Click to collapse
Maybe it will work in ICS if only we had the patience to wait.
It is wery strange to use a phone that does not have any rotation whatsoever. You have to try and take a picture or to watch a klip that is stuck in portrait mode and want turn. I cant belive that no one has solved this yet. PLEASE HELP!
Recently, I had my EU HD2 repaired (while on android) due to a malfunctioning digitizer, however, after it was replaced the promixity sensor would not work, and when they fixed the promixity sensor, the backlight stopped working.
Eventually, they gave me a replacement TMOUS HD2 (It looks like an old, refurbished or used one, although it has the new desensitized-but-messed-up-at-the-bottom digitizer). Although everything works perfectly in WinMo 6.5, the gps, accelerometer/g-sensor, magnetometer, and orientation sensor was not working at all in any NAND android (showed 0/10 no change in sensor test). Apps had detected it as non-existent, or force closed because some sensors were necessary.
After looking on similar threads on xda, where people have come to the conclusion that it's because the replacement parts don't have the right drivers in android, this is probably the problem with both of the HD2s. I'd think this would be a significant problem for many (albeit a small fraction of people) They also say that it would not work for any SD build either.
Has any devs bump into this problem as they got their HD2 replaced or repaired? This issue may get more prevalent as all our HD2s get older.
Atm, I am going to try to install Mango on it, as i heard that WP7 works too.
Could that mean that parts are from, like an HD7 or something? Or because TMOUS and EU parts were mixed together?
Also I'm wondering if I should return it and say the sensors are not working? lol that may be the only way to try get it working for me.
Hello.
This topic has already been talked about few months ago. No one paid attention on it, except the people who were facing this problem. So I'm writing about it once again - maybe someone will finally hear our calling for help.
What I'm talking about is the problem with G-sensor under Android. It works fine on Windows Phone, it works great on Windows Mobile, but it doesn't respond on Android. The problem usually occurs after digitizer replacement in HD2s. I'm facing it after changing the motherboard. I believe there must be some drivers missing for the accelerometer. So, can anyone try to fix it? I can provide help. Please.