I purchased a used HD2 a few months ago which was preinstalled with Android 2.1 Sense. Everything was working perfectly (also the accelerometer). Then, after a few days of purchasing the touch screen digitizer was not working (i mean, no touch), so I gave it for repair and it was fine. But, the accelerometer was not working on the Android build (Nexus HD2 ICS v2.1 NAND) I was using (previously it worked before repair). So, I installed WinMo just to confirm and found that the accelerometer was working fine. Then, I installed WP7 Rom (HD2o) and again the accelerometer was working fine. I booted Android from SD (ParanoidAndroid) and the accelerometer was not working. I tested a few more builds and it was not working.
As it is working in Windows, I guess it is not hardware issue.
The Great folks at XDA, Please Help!
I think this is an Android related problem, so I posted here.
So how can we help you? Most of people got working accelerometer out of box on android, so don't get too fast assumptions, it MIGHT be hardware issue(it's more complicated than it's working or NOT)
As for help, try using several kernels, start especially with stable ones, like Tytungs then go off for another kernels.
By this service, are you sure they havent replaced more parts, like motherboard etc? What version of radio and HSPL have you used before and are using now?
As I mentioned, the Accelerometer was working PERFECTLY in WP7 and Windows Mobile.
What is the issue with Android ?
netchamp.faris said:
used HD2 a few months ago which was preinstalled with Android 2.1 Sense. Everything was working perfectly
Click to expand...
Click to collapse
So I'm assuming it WORKED in android. Try using GPS status app or Tricorder, they show info about accelerometer data, then you'll know if it's working partially or not.
Oh, there is a chance that in repair service they replaced some parts in your HD2 with china counterfeit and drivers are not working correctly under android. But hell knows.
Check if it's working anyway.
actually, you're not the only wich have that problem, in this POST, much people, including me, are trying to do work the g sensor
berseker1 said:
actually, you're not the only wich have that problem, in this POST, much people, including me, are trying to do work the g sensor
Click to expand...
Click to collapse
Well, its not a g-sensor calibration problem.
Its just that the accelerometer doesn't work in any of the android builds.
Sent from my HTC HD2 using xda premium
Related
I am a freasher here, I have flashed several times with WM6.5 roms to get my camera work, I have even tried various c.cabs without success.
I need desperate help!!!!!!!!!!!!!!
First off, welcome to XDA.
I've moved this thread to general discussion forum as its not related to rom development.
As for your issue. If you've followed this guide correctly to flash your roms, then it sounds like your camera issue is due to hardware and not software, therefore its not related to roms.
When did you camera fault first appear? Was it after flashing a rom?
If by 'not working' you mean that the zoom no longer functions then that is the same in most cooked ROM's now as they are using the camera software from elsewhere. If it totally doesn't work then as said, sounds like a hardware issue.
Hi Thnx, The Camera stopped working soon after I flashed the 6.1 rom to 6.5, since I have tried various roms and c.cabs.
I agree that it is most likely hardware issue, do u think I should try a 6.1 rom to see if it works again?
First question is what Touch HD do you have the T8282 or the T8285. Several people have had issues with their cameras here. I was able to send mine in under warranty to get it fixed, granted it took over a month to get it back but it was worth it to get my camera working again. I also tried several different roms and sometimes it would work a couple times then would disappear again. After a while changing the Roms didn't work, then I re-hardspl'ed the device and got the camera working again for a short time but that didn't even last. Eventually I sent it back to HTC and they repaired it for me. Good Luck.
Thanks for all comments, I am not going to send it back for repairs as I cannot live without it now, thinking of the HD2 on the 11th NOV maybe, but keep the suggestions coming.
HW prob, try reconnecting flat...
Not quite sure what u mean? "reconnecting flat"
Any other solutions??
Hello, I've been following this thread since I'm expiriencing the same problem. The camera on my 8282 it is simply not responding. It worked without any problems for almost a year. The only time I have flashed my phone was 3 months ago with the official ROM update realeased by HTC and nothing more. There is no way to send the phone to HTC since there is no official service representative in my country. I would like to know if there is something else that I can do to get the camera working again. Thank you in advance for the help.
Hi,
I'm using a Tmous HD2, Energy for WM, shubcraft 1.5 for Android.
G-sensor worked fine in both OS, until one day I got stuck with the rain without the raincoat and my HD2 was wet a little bit. I dried it for one night. Everything still works ok but the G-sensor in Android.
I checked it again in WM. There's no problem with G-sensor (I can play games with it or rotate the pictures in gallery tab), but when I turned back to Android the problem still there so I assumed that it should be software's trouble. I booted again into WM, tried to do the callibration, turned on and off the G-sensor. Android's g-sensor kept not working. Home screen (Launcher Pro), browser, games, etc. can't use it either.
After that I downloaded another ROM of Android (JDMS 1.5), erased the old one, hard reset WM's ROM, installed JDMS 1.5: it didn't work as well.
What I haven't tried yet is trying another WM's ROM or re-installing Hard SPL.
So what do I need to do now?!
Can any one help me?
already reinstalled HSPL 3, nothing happened.
Vladikox said:
already reinstalled HSPL 3, nothing happened.
Click to expand...
Click to collapse
Did you try having Android build a new data.img just to test default settings?
jmmmmm said:
Did you try having Android build a new data.img just to test default settings?
Click to expand...
Click to collapse
I have deleted all of Android's files in SD card, then copy the original one --> problem not solved.
I am having the exact same problem. The G-sensor works in WinMo but not Android. I've tried re-formatting the SD card and doing a fresh Android install.
Were you ever able to find a solution or does anyone else have any other ideas of things to try?
My problem has been solved few weeks ago.
At that time I was going to lose hope and came to a decision of giving up trying and willing to say good bye to Android's g-sensor. I turned off the auto-rotate in Android for (about) a week. One early morning waked up, turned it on again and a wonderful thing happened: it was in land-scape mode.
In next few days the sensor was not working so well (but at least it worked). Now it run smoothly and I don't get trouble with it anymore.
Wish you can fix it successfully!
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
pvdw50 said:
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
Click to expand...
Click to collapse
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
I've also got this issue after installing a new kernel and no matter what combination I use now it won't work again. I've tried all of my previous working combinations and none of them have fixed this, I've tried turning off auto-rotate and on again but again nothing happens. This is pretty useless if it's stopping on multiple people for no reason.
Anyone know the script in g-script lite to enable and disable the g-sensor to see if this works as I've used this in the past on one of darkstone's builds but don't have the script anymore?
Thanks
RenaissanceMan said:
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
Click to expand...
Click to collapse
I'm using Sergio's core droid V0.8 desire wich is very stable and the camera is working, but I tried many others and I never had any BSOD's.
Can anyone tell us where the G-sensor hardware is located in the HD2? there should be a logical explanation to this problem.
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
AvRS said:
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
Click to expand...
Click to collapse
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
RenaissanceMan said:
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
Click to expand...
Click to collapse
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
AvRS said:
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
Click to expand...
Click to collapse
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Up .......
RenaissanceMan said:
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Click to expand...
Click to collapse
I've never seen any files called that on my device so what I'd try is first make a backup of that file then rename it to sensors.qsd8k.so and then restart. All of my files in that folder are all .qsd8k. With some builds/kernels they name things differently and say to rename according to your device for example when you get lights.htcleo.so which you need to rename to lights.qsd8k.so to make it work. If this doesn't work definitely try a different build to see if it's working in that and if it is try going back to your one you're on now and maybe it'll wake it up again.
Hi, I have same problem with sensors on my HTC HD2.
A downloaded Sensor Test app from Marketplace and it give me this values:
Accelerometer (BMA150)
Accel X Waiting... M/S
Accel Y Waiting... M/S
Accel Z Waiting... M/S
Magnetic Field (AK8973)
Mag X Waiting... Deg
Mag Y Waiting... Deg
Mag Z Waiting... Deg
Orientation (AK8973)
Az Waiting... Deg
Pitch Waiting... Deg
Roll Waiting... Deg
Proximity (CM3602)
Near/Far Waiting... Prox
Light (CM3602)
Light Waiting... Lux
Battery
Charge 94 %
Temp 35 Deg
Voltage 4.1 V
It looks like a problem with some communication bus or something like that. Can someone try Sensor Test app and check values.
All of these sensors are not working and I dont know how to fix them
Last edited by pawlish; Today at 02:57 PM..
I'm in the same boat as yall. Sensor works in WM 6.5 and even Windows Phone 7, but still no Android. I have also noticed that the proximity sensor isn't working as well. Do yall think the 2 might be related?
My G-sensor function of HD2 can't use after installed Andriod. I changed many other ROM versions to try if its available ,but still it doesn't work. The game teeter show that can't find G-sensor facility in your phone and will quit..
Could you please help me and suggest me some solution, it depressed so much.
My radio version is 2.15.50.14.version FRG33
only HTC, not T-mobile.
THANK YOU!
me too ,it diever me crazy!!!
help!!!!!!!!
Try Calibrating the G-sensor in windows mobile, maybe that would work
it does work in WP6.5 ,but when I switch to Andriod ,no matter which version,system can't find G sensor... I depress me so much,cus it seems like a brick without gravity function.
Why dont you post which android version you are using and or ask for help in that versions thread?
I have the same problem, I've done all that I was able to do but nothing happened..
G-sensor works in WM but doesn't into android.
HTC HD2 LEO
Radio : 2.15.50.14
excuse my poor english
Well I am using the T-Mo US HD2 and have HSPL-ed it and put Android on it using the Evo Carbon Rom from Motoman, and the G-Sensor Calibration works perfectly to set it, and Teeter works flawlessly as well (Just tried both after reading the thread).
I would have to agree with the above postings, you might want to look at the threads of the roms and see the whats working, whats not, or check to see if a app you installed might have corrupted or changed the default app. But if you have tried multiple roms and still have this issue, and not in WinMo, I would have to speculate you didnt clean your SD card of prior files.
same problem here. need help!
I got the exact same problem. mine is a tmo-us hd2. g-sensor works fine under wm no matter if it's stock rom or custom roms. cannot detect g-sensor when switch to android. tried several different android roms resulting the same.
btw, i did format my card every time before installing new android rom. when i put my card in my friend's HD2. g-sensor works fine under android on his phone. clearly, something is not right on my phone, but everything works fine under wm.
Me TOO ~~~~~~~~~
i have the same damn issues at first i was using a custom rom then i stock back my leo phone then try installing android using MOTOMAN234 EVO CARBON REMIX V0.5 but still no G-SENSOR !!! I Dont see hows its the phone when evrything works right when im in windows mobile DOES NE ONE KNOW HOW TO FIX THIS???
Thanks a lot for your suggestion ,Let me try if it available on my phone.
UP please ! I'm going to be crazy.. Same issues :'(
I also have the same problem on my replacement TMOUS HD2. Both G-sensor and light sensor is not working on Android but works flawlessly on WM. On the original HD2 I didn't have any of these problems. Did you all recently purchase the HD2 or got a replacement of it? Anyone knows if there is a recent change of hardware in the HD2? I got my replacement right before Christmas.
Same problem here its definitely not SD related as I'm running from nand now and still nothing has anyone figured it out yet.........
Is there any developers reading that could possibly offer us their knowledge? I just don't understand why it doesn't work for such a small handful of users,
Sent from my HTC HD2 using Tapatalk
whynot66 said:
Is there any developers reading that could possibly offer us their knowledge? I just don't understand why it doesn't work for such a small handful of users,
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Same here. Looks like we are not the only one who has this problem. Hope there is a developer can notice this problem.
The compass on wm 6.5 doesn't seem to work either on my replacement TMUS HD2 am I the only one?
Need Help
Could someone (a dev) please take notice of this thread and maybe take some time to see what the issue might here? We would also like to enjoy fully functional Android on our HD2's
Would be much appreciated...
giurca said:
Could someone (a dev) please take notice of this thread and maybe take some time to see what the issue might here? We would also like to enjoy fully functional Android on our HD2's
Would be much appreciated...
Click to expand...
Click to collapse
UP i hope some one can see
hi, ive used android on my hd2 pretty much since day one,
ive never been able to get the g-sensor to work in android. i dont get freezes or anything at all it just simply doesnt work, ive tried all sorts i was hoping nand would fix it for me but it doesnt can anyone be kind enough to offer me any solutions?
it works fine in windows mobile so its definatly related to android
ive tried loads of builds and most kernals still nothing, ive tried scripts to disable and re enable and nothing im totally mythed :/
Sorry for bump
Sent from my HTC HD2 using Tapatalk
Are you still using SD?, if so try calibrating with it upside down, screen facing down.
I'm running NAND, when I go to caliberate the bubbles don't move at all, until I press caliberate then the just move left and right and it says complete.
....
Sent from my HTC HD2 using Tapatalk
Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.
oddly I got it to calibrate with the phone on its side, facing sideways. IT rotated ok afterwards but then got stuck. Best thing to do here is not to calibrate at all as it seems to work fine without any calibration - too late once you have done it though?
pvdw50 said:
Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.
Click to expand...
Click to collapse
I can't find the script but all it does is renames the akmd file to stop and start. Your the only person I've found with the same problem we need to figure this out man
Sent from my HTC HD2 using Tapatalk
There's 2 more topics on this for a while now, but there's no luck on a solution. The biggest problem we all have is likely the fact that anyone reading a G-sensor thread is having the same problems. The one with the solution isnt looking for our threads.
solution - working for me
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem
Spartn said:
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem
Click to expand...
Click to collapse
Did it already, it seems there maintains a hardware differences in every HD2, some of can work properly, some of like us can not. Hope that the dev. who also has this problems can work this out.
i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~
有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论
朋友,你也是重力出了问题吗?
Just keep subscribed to this post and we'll find something eventually
i hope so~~~~~~~~~
hen_43 said:
i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It looks like so, but it works in WM, so it may be HARDWARE DIFFERENCE let the drivers cause issues? I must talk about, I have never calibrated g-sensor after flashing NAND ROM.
hen_43 said:
有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论
Click to expand...
Click to collapse
hen_43 said:
朋友,你也是重力出了问题吗?
Click to expand...
Click to collapse
Please use English on this forum, thank you.
whynot66 said:
Just keep subscribed to this post and we'll find something eventually
Click to expand...
Click to collapse
Hope that we can eventually find something useful.
ye~~i try but my english is poor
BTW,,i hope we'll find something eventuallye,too
seem like no one can solve this problemT_T
honestly this solution didn't help me - first time, i calibrate my HD2 facing down about 3 times, and finally 3rd shot was done successfully
So your g works?
Me and others in this thread have no g at all baby caliberate as the g sensor doesn't work at all :-/ please can some one help
I was using WP7 Mango with ICS dual boot, after upgrade the WP7 & ICS both I have new problem with touch screen.
Its working 2-3 mins after reboot, but suddenly touch is not working, again when I have pull the battery and restart the phone its working for 2-3 mins, and again same.
I have tried to go back Tmous stock rom, there is also the same issue.
Can any one help me out in this??
Thank you in advance
If the problem exists in stock windows mobile 6.5 then it is highly probable that it is a hardware issue.
It is a hardware issue, but the reasons could be a few. Most likely the heat of a working device expands the digitizer connectors and flex cable, which is why the issue appears after a few minutes.
Replacement needed
Anyway a new touchscreen is needed!
Thank you for replyssssssssss
I was using Stock rom from yesterday, working fine now. I went to WP7 same issue.
can it be virus issue??
May be some virus is in 1GB memory (ROM).
I don't know anything though
SOHOM said:
Thank you for replyssssssssss
I was using Stock rom from yesterday, working fine now. I went to WP7 same issue.
can it be virus issue??
May be some virus is in 1GB memory (ROM).
I don't know anything though
Click to expand...
Click to collapse
Not a virus. You mentioned you went back to stock rom and had the same issue, so now there is no issue? I guess it's solved then.
enigma1nz said:
Not a virus. You mentioned you went back to stock rom and had the same issue, so now there is no issue? I guess it's solved then.
Click to expand...
Click to collapse
Yes there was some issue, don't know what was that but after Wipe(TASK29), there is no issue with touch. Working perfectly with "HD2_Pdaimatejam_Rom_Wp7.5_mango_7.10.8107.79_v7.3_L2_r5.51"
Issue starts from v7.5 for me though,
And touch is working perfectly with Protadroid.
I knew that was not a HARDWARE Issue.
SOHOM said:
Yes there was some issue, don't know what was that but after Wipe(TASK29), there is no issue with touch. Working perfectly with "HD2_Pdaimatejam_Rom_Wp7.5_mango_7.10.8107.79_v7.3_L2_r5.51"
Issue starts from v7.5 for me though,
And touch is working perfectly with Protadroid.
I knew that was not a HARDWARE Issue.
Click to expand...
Click to collapse
Lucky you!!!