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
Hey guys!
Nice to post here, you all are really good at this, that's why i'd like to ask you anything that's being a headache these days.
I ran the WP7 Moonlight rom on my HD2 properly last week. I've been using it for a couple of days and everything works fine, except the jailbreak thing.
I read that the Moonlight already contains the hack but it actually doesn't work for me. I've been trying to hack it by the famous chevronwp7 method (I followed all the steps, little by little, from even 4 differents guides) and no success at all... it says "check the USB ... check zune open... blablabla" I read lots of posts on here about this issue and none of the answers worked for me.
The main reason because I want to hack it is to stop the battery problem that makes my phone last less than 20 hours (I have 3G disconnected most of the time to prevent this but it doesn't make much!!). I've read that i could arrange this by editing the registry.
I think everything would be fine if I could hack the phone...
Any ideas?
Thanks!!!!!!
Firstly congrats. If you're seeing this post, you might have already done so or are trying to flash some custom ROM, which is absolutely ok.
Rather its fun and satisfaction that you keep your device up to date if not possible through official means. Also for some good changes.
Unfortunately, its not completely flawless. There might be some issues which are covered in the further updates of the ROMs.
Among oother small problems, one major problem I faceed when I flashed a custom ROM (actually three) is that the Android Market failed miserably when I initiated it. There were horrible search results. Also the categories were not showing the apps which would otherwise be placed under them.
Fortunately, the Android Market site was open for me which was the last option for me to go on with.
The only solution I could find to this problem was a bit of patience and some really basic info about market.
I tried to re install all the applications that were previously being shown as installed already. Though they showwed "Installed" status but you can install them again.
After a lapse of almost three days, I tried to access the Market app and it was actually accessible with all the search functionalities and EVERYTHING running smooth.
A thing I would like to advise on is try not to wipe out all the data (the 4 wipe out options while flashing) from your device. It might, might help you not to lose data and possibly, the Android Market too.
Have fun.
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
antjmon said:
I've been on a custom rom for greater than a month now and have not experienced any market issues. The only problem that I've ever had was wifi stopped connecting for me. But it was an easy fix. Sorry you've had problems... Perhaps something else is to blame?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yes, as I have solved the problem anyways.
DawoodMunir said:
Yes, as I have solved the problem anyways.
Click to expand...
Click to collapse
عزيزي منير
Please let me know how did you fixed this issue?
I really need to know because i have the same issue.
firstly i have tried the search function but have had no luck.
im running the last cm9 nightly build from last november and everything is working ok apart form the camcorder??
it records a bit flakey and after X amount of seconds/minutes it just mutes the recordings?
ive tried learning sign language as a temporary solution but think it would be easier for someone to point me in the direction of a fix.
thanks much
I see nobody reply. I was never on CM9, but I can tell you this. I did not do full wipe of the phone and full sbf reinstall and I had GPS issue that nobody could solve. When I did that, everything started working like it should. Maybe this could help you.
ezantera said:
I see nobody reply. I was never on CM9, but I can tell you this. I did not do full wipe of the phone and full sbf reinstall and I had GPS issue that nobody could solve. When I did that, everything started working like it should. Maybe this could help you.
Click to expand...
Click to collapse
i did everything to the book when installing (all wipes etc). its just super annoying cause its the one thing i actually use on the daily lol
Had this phone for a few months and let me say I love it, but it gives me a major headache with all the hassle it gives me as far as things that come after rooting and things like Viper4Android. Never had so many problems in the past with things like this.
I can't for the life of me get this to work and was hoping that someone here on the forums can help me. Seeing as I'm in the military right now my schedule is kinda hectic.
So I installed busybox, and I am rooted. At the time I rooted there was just systemless root which is a pain in my ass.
When I open the apk it asks if I wish to install the drivers, and I click yes and it hangs for a second or two then quickly says it's installed when I know it's not. Im almost positive its suppose to ask which driver I want to install but it doesn't? What am I doing wrong here or how can I fix it? Also trying to use the app provided from XDA to change my selinux or w.e doesnt work either. Says it cannot get access to root from my super user manager which I find strange because everything else works.
Thanks for any help you guys can assist with!
This thread should give you all the answers you need for installing V4A.
http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
ViPER install is a bit janky on the MXP for some reason, the only method in which I have gotten it to properly install is this one, written specifically for the MXP rather than the one above:
http://forum.xda-developers.com/mot...iod-moto-x-t3249388/post64303350#post64303350
Be aware though that the libfiles .zip seems to be the culprit of some random, temporary bootloops that can be solved by simply hard rebooting again. I've tried to find a fix for this but sometimes it happens less often than others, and seems to be only an occasional occurrence.
Been testing Orion rom and it's very smooth and stable and... comes with viper.
Is there any alternative I can use? I don't want to go through some annoying bootloops and prefer to stay on my stock ROM. I'm mainly wanting this so i can be able to use an equalizer over Bluetooth with my Bluetooth earbuds. Anybody know any good alternatives? Thanks for the quick replies. You guys are awesome
That's funny the only boot loops I've had is on stock.
Do you know of any alternatives or a way I can get my stock equalizer to work over bluetooth?