yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Bas2ct:
bma150_usr

Heyy AngelDeath,

I just thought about this, how do the drivers for Android work? Are they installed through the kernel or the ROM? (And the kernel being provided in the ROM, but has updatability, is the kernel the main driver package?)

Because íf bma150_usr is the driver, maybe I could try and incorporate it in the flash sequence? I'm not sure I will be able to with the knowledge I have now, but hey, leaning is an ongoing process anyways. Could also speed it up and focus it to this for a while...

Oh, and is there a way to connect and recognize my phone, not just my SD mount, but the whole shabang? I would like to be able to edit things through my computer because of the hardware (keyboard, mouse, big screen).

Best,

Bas
[HD2 Android NAND Development] ryu-lamp:
Hey! nice one!!!

Good job
[HD2 Android NAND Development] AngelDeath:
What Dont like AngelDeath? Morbid Oxymoron huh? :D

Okay first things first. The GPS Status program has options, when you hit the windows key, you should have several options: Tools, Radar, Share, Settings, if you have none of these, then either your using the wrong program, or there is a more serious problem. Under tools you have You have 3 options Compass Calibration, Calibrate pitch and roll, and Manage A-GPS State.

The BMA150_usr file is not part of the kernel, its actually part of the ROM, its located under system/bin. Also, there is another file associated with the G-Sensor, the AKM8973 doesnt exist in a rom that isnt installed, it seems this is created during initial bootup of the rom, the file that controls checking the G-Sensor is the "akmd" also located in the system/bin folder.

In your log you posted this is the key to the G-Sensor error:

[ 2.958892] AKM8973 akm8973_probe: set power down mode error

[ 2.958953] akm8973: probe of 0-001c failed with error -5

Which in my eyes validates my point of the akmd file query.

From my gathering, the akmd file queries or checks for the G-Sensor, when it gets no response it assumes there is none and fails. My guess at this point is finding the right 'akmd' file so that the G-Sensor works correctly.

I would suggest as a test to try a EU rom, just for EU, and see if the G-Sensor works, IF it does, then I would suggest to pull the akmd and bma150_usr from that rom and put it in a rom that you are currently trying to use. I'll try to do more digging on this.

And as for recognizing your phone, dont know what you exactly mean, if your talking about syncing, then if you are not using a sense rom, then download a free app called 'MyPhoneExplorer' from market, if you are using an htc sense rom, then 'HTC Sync' works fine.

If you talking about being able to explore your file system, then their are several, I personally use 'Droid Explorer', but be careful the program can be tricky at times if you have Android SDK installed, since the adbshell/server doesnt close properly at times, you would have to go into the task manager and kill the process of all adb.exe for it to work at times. If you do use Droid Explorer, there is a wealth of features that could help in debugging and makes it easy to push files onto the phone instead of using adb push thru the adb shell.
[HD2 Android NAND Development] johndoe99:
This NAND build works great and does not have any G Sensor problem that I have noticed.

http://xdaforums.com/showthread.php?t=915159
[HD2 Android NAND Development] AngelDeath:
Okay here is the first thing:

In your log ytu posted (havent looked at the txt file yet)

[ 2.430419] __spi_bma150_set_mode: BMA get into SLEEP mode!

There's why the g-sensor is disabled.

The rest of the errors of course will come because the sensor is in sleep mode. (Disabled my belief)

the amk8973 is created either with the values of the g-sensor, or its created after calibration is done, never delved too far in that.

You might have already done this, but I would say take the working rom and put the bma150_usr file in there without making any changes to the rom. Now the other thing that could cause the hang is how you re-compiled the zip file. The best method I can tell you to do is use your fav archive program (7zip, winrar, etc) and OPEN the zip file, DONT EXTRACT it. once opened then drag the file to the folder you want to put it in, this way it will keep the folder intact, and the compression intact, and just adds the file, then when you close the archive it should be in there. The reason is if you extract and then re-zip it, you run the risk that it will compress it different then what it is (especially in windows) and that will and can cause the boot hang.

Now as for Droid Explorer, this is much more powerful then you even know, if you plug the phone into your system and turn the phone on and then run droid explorer, and then click the icon that is the dalvik debug, you can actually see the boot up process, if in droid explorer while its hanging you see the file system load you can rename I believe the file bma150_usr to bma150_usr.old once you do that the system should load if its that file.

I have tested many things (Especially the gps drivers) and I have my system hang on the white boot screen, and I'll replace the files I was testing while its hanging, and as soon as I drag and overwrite the file, the phone will boot normally. So believe me, its much more powerful then it seems. I will look at the log and if anything stands out I'll let you know, but I would say back up your system and try a EU rom, or even download on and see if in the zip under system/bin the bma150_usr file is there even before flashing, if its there try it.
[HD2 Android NAND Development] AngelDeath:
Just downloaded the rom your using, will test it out tomorrow on my backup HD2, going to look at the file system too.

Your log from what I see isnt a boot log, looks more like a recovery log after flashing. But will keep you posted tomorrow.

*EDIT*

I just looked at the rom, your right there is no bma150_usr file, but I dont think that the one provided on the first post can be used either, because the one in Tytung's Nexus is Gingerbread, the one on the first post is NOT for gingerbread.

I have one for gingerbread, but before I have you try it, I want to flash this rom and see what happens. But rest assured I have one for gingerbread.
[HD2 Android NAND Development] Bas2ct:
Heyy AngelDeath,

So, I flashed with BMA150_usr in the ROM, no changes. Probably because it is not for Gingerbread.

I did figure out why I couldn't get to tools in GPS Status. It was not because of designation of hardware buttons, they all work fine as I discovered in CWM (keycheck). It was not working because the button needs dome delicate handling. If the windows button is pushed directly, the home button is also pushed. So some tenderness and careful aiming avoids the problem (like so many;)).

Using the tools, everything stays the same (as expected, the sensor isn't recognized).

One weird thing keesps happening with Droid Explorer though:

Insert USB

Startup Droid Explorer

Connect after phone is found, starts loading

Gives me error saying not sufficient memory.

I get it is not enough mem on the phone, but what mem is it aiming for? Ever had that experience?

Best,

Sebastian
[HD2 Android NAND Development] AngelDeath:
Bas2ct,

I just tried this rom, I didnt install anything, just the rom, and it doesnt have under display the calibration section. And not every part of the system does landscape, for the most part it is in portrait mode, msgs are in landscape, and a few other things.

Please tell me exactly what you are trying to do and I will see if I can create the same issue, as it stands right now from what i see, you wont be able to do any calibration with this rom at all. But tell me whats making it wacky or not working right, and I will see if I can duplicate it.
[HD2 Android NAND Development] Bas2ct:
AngelDeath,

I'm sorry for the late reaction. You are right, the ROM does not support calibration in the menu. But that should not affect calibration in GPS Status? This week I won't have any time to work on it, crazy busy. Will probably till next week. Thanx for trying, will get back next week.

Best,

Bas
[HD2 Android NAND Development] theletterj:
Upping this.

Anyone want to start a bounty to see if any of the more talented programmers can get to the bottom of this?
[HD2 Android NAND Development] turjo_ssmc:
what are you talking about man, my system/bin doesnot even contain bma150_usr, AK8973Prms.txt, AK8973.Prms.txt.tmp.

i am in deep ****. same problem, had a screen replacement, now in every android build g sensor. proximity sensor, mangneto sensor not working. im winmo 6.5 even 7 everything works fine. WTF... please help us XDA..
[HD2 Android NAND Development] sasha1911:
Присоединяюсь к вопросу, тот- же досадный глюк ( на winmo всё работает.
[HD2 Android NAND Development] boflynn:
Having the same problem

Ok so this seems to be a fairly widespread problem. My phone worked perfectly until I had to get the touchscreen replaced and then the g-sensor stopped working (with the same ROM on it)

What can I do to help get to the bottom of this issue? What logs, system dumps, etc. can I provide so this gets sorted.
[HD2 Android NAND Development] AngelDeath:
Boflynn,

Your post might be the answer, I have said all along that I suspect a hardware revision, I dont know if I am right, but your post just might support that.
[HD2 Android NAND Development] wtbt:
hi angeldeath

hi,maybe you can post all your solved methods on the fisrt page,we can try them all.thx.

now i try any ,but without resort
[HD2 Android NAND Development] turjo_ssmc:
we are all having the same problem, someone help us.
[HD2 Android NAND Development] wtbt:
new thinking

i guess this issue depend on the touchscreen and the touchscreen's film.

it's new thinking about the problem
[HD2 Android NAND Development] wtbt:
strange

from yesterday to 9 am today,g-sensor work perfect.but now it's invalid again.

omg
[HD2 Android NAND Development] turjo_ssmc:
did u have the same problem? i mean you did any screen replacement recently? i also heard somewhere that this problem seems to fix spontaneously.
[HD2 Android NAND Development] boflynn:
Ok so if it is due to a screen replacement - how do we go about getting the G-Sensor working again?

What do we need to give to the ROM chefs/kernel gods to get this issue sorted out?
[HD2 Android NAND Development] JMacSp:
Okay I have the same problem... On WM 6.5 & 7 rotation works... BUT !!!

it works only in 2 different side..

1. The regular portrait mode

2. and when I flip the phone to the left for Landscape mode...

BUT when I flip it to the right it doesn't go into landscape mode....

Normally if i'm not mistaking it's supposed to rotate all 3 side right ?

it's been like that since I bought it from T-mobile....

the G-sensor in WM works..

but when I go into android... the G-Sensor doesn't work at all....

I tried A bunch of different roms.... Bunch of different Radio FW the G-sensor does not work in android....

I will believe that... Some HD2 devices have a different hardware... because on stock WM it doesn't flip the normal 3 ways to begin with.... ???

I'm just gonna sell it... I have for just a few weeks now... it's brand new...
[HD2 Android NAND Development] wtbt:
nobody can deal with this issue.i forgot my hd2 had g-sensor once.
[HD2 Android NAND Development] formatboy:
My HTC HD2 has the same issue, no g-sensor in android, but pefect g-sensor in WM6.5 and WP7.

I tried to find out why this happened for a long time, but nothing I've get.

Yesterday, finally, I decided to disassemble my HD2. Is the akm8973 right there?

mmm......................

Yes, it is akm8973s, neither akm8976 nor akm8975. And all parts of the mainboard is the same as the normal HD2 with great g-sensor.

I'm perplexed at the result.
[HD2 Android NAND Development] turjo_ssmc:
one strange thing, actually proximity sensor does work, touch function stops but screen doesnt goes off. that means it is working obviously but not properly. will some one help us?
[HD2 Android NAND Development] wtbt:
no i donot touch anywhere,it work for 24hours suddenly.now it not work
[HD2 Android NAND Development] sfxram:
HTC HD2 LEO USA T-mobile - G -sensor not working

G -sensor not working....

MY phone config : HTC HD2 LEO USA T-mobile version

ROM Info BUILD ON THE LATEST 1.9.16 MIUI ROM android 2.3.5

http://xdaforums.com/showpost.php?p=12769856

Kernel version:

2.6.32.15_tytung_r12ga11a1a8

i tried with bma150_usr file.. no use .. nothing.. happened..

i tried to replace that file in system/bin but there is no such file in that folder...

so i just copied over there( system/bin)... rebooted and test with Bubble APP

but no luck ... nothing.. has changed...

auto rotation also not working ... but in my rom there is application called Campus... its also not working....

Not able play games..

Help me ....

Thanks
[HD2 Android NAND Development] Faith_G:
Another g-sensor not working

Same issue as above, deleted and replaced files, calibrated in all positions, still nothing.

I'm using http://xdaforums.com/showthread.php?t=1205969 as the ROM currently. Any other suggestions? :(
[HD2 Android NAND Development] selvag:
Help us .... to fix

G sensor issue

S ent from my HD2 using xda premium
[HD2 Android NAND Development] Stroid01:
Just got another HD2 for my sister and I am having the same exact issue and did the steps you did with no results either. Stinks my other HD2 works great! Any devs willing to look into this again?
[HD2 Android NAND Development] tavanthuc_a11:
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~~~~~~~~~~~~~~
[HD2 Android NAND Development] YZ:
I have tried:

- bubble calibration

- File replacements

- Going back to wm, calibrating

- Editing files in data

still not working..
[HD2 Android NAND Development] davidjanda:
nice. good job.
[HD2 Android NAND Development] YZ:
the file replacements worked for you?
[HD2 Android NAND Development] AngelDeath:
Okay I see this topic has been moved, and it still alive.

Again let me say this to refresh for everyone:

There are revisions from what I see with the G-Sensor, this is most likely the reason why this year old topic is still re-surfacing. Also either the MIUI or the CM rom (forgot which) doesnt have the G-Sensor capability module in it, so in short you wouldnt find it in these roms, this is why I suggest a 3rd party rom, like Bubble, because by re-calibrating the bubble in the past has fixed the G-Sensor issue, because that was how I was fixing it before I fixed it.

Since my suspicision has been there is a revision to the G-Sensor the MFG Date would confirm this, Also another confirmation is that people who have had touch-screen problems (Non-Responsive, also in my sig about the discussion) sent in their HD2 and when it returned fixed they would have the G-Sensor problem.

Which leads me to believe that the driver we are using for the HD2 is outdated and needs adjustment to add this revision hardware for the margin error compensation.

I still to this day do not have a g-sensor problem, but my screen hasnt been replaced either. I am using the sybran Runnymede 4.01 rom (Sense) and have no problems. The reason why this is probabaly working in WM is because the drivers for the G-Sensor probably includes the hardware already in its list.
[HD2 Android NAND Development] Stroid01:
Any devs willing to work on this again? I am willing to provide any logs or necessary files associated with this problem to help resolve it. I have 1 HD2 that works and one that has no g-sensor very frustrating.

Also the one that does not work has never had a screen replacement or anything like that.....Launch T-MO HD2
[HD2 Android NAND Development] ThiefZero:
Got my HD2 back, they fixed the non-responsive touchscreen and now I'm suffering from a non-functional G-sensor in Android.

Any help would be greatly appreciated.
[HD2 Android NAND Development] Faith_G:
My girlfriend and I both have HD2's on android - mine has the g-sensor problem (works in WinMo, totally unresponsive in android), while hers works perfectly. No matter what ROM or fix I have tried, mine will not work. Hers works on everything. Frustrating...
[HD2 Android NAND Development] :
@ all: http://xdaforums.com/showpost.php?p=22673845&postcount=145 Try it out
[HD2 Android NAND Development] Faith_G:
Wouldn't you know it, 2 days after I put Windows Phone on the HD2 with the funny G-sensor. I'll try it when her tied of playing with Windows Phone.
[HD2 Android NAND Development] ThiefZero:
Well, I finally managed to get my G-sensor working again after my HD2 came back from repair.

Inspired by this post: http://xdaforums.com/showpost.php?p=22813060&postcount=148

I did the following:

1) Used ES File Explorer explorer to go to /system/lib/hw/

In this folder, there should be a file named: "sensors.????.so"

Write down what it says in the ???? part.

2) Go to /system/ and open the "build.prop" file.

In here, locate the following lines:

ro.product.name=X

ro.product.device=X

ro.product.board=X

Replace whatever it says as X with what you wrote down earlier.

3) Save and exit (If you can't save it, make sure you've checked the "Mount File System" box in ES File Explorer settings.)

4) Reboot your phone, your G-sensor should be fully functional again. (Don't forget to enable it in settings if you've turned it off before.)

Hope this helps, and if it did, don't forget to give thanks to the original poster =].
[HD2 Android NAND Development] DOVIZ:
Man, thank you sooooo much, my g-sensor is working !!! The problem was that i edited that build.prop , to load some games, which is not supported for HD2, like six guns :)
[Vibrant Q&A, Help & Troubleshooting] bobn4burton:
Ok...so I've been putting off updating my vibrant to a custom rom for awhile now. I know there is lots of info on how to install a custom rom...but I'm wondering what everyone does to prepare?

1. How do you backup your apps? Titanium? Just reinstall from market?

2. Other than installed apps, what other stuff do you backup?

3. Is there a way to do a 100% backup(like an image) so I can go back to my phone a it is right now? If for some reason I wanted to...

4. What else needs to be done to prepare before starting the update process?

5. How long does it usually take to backup, install new rom and then tweak and reinstall everything to get you back to where you were before beginning?

Thanks fort any help or even helpful links if you have any...!
[Vibrant Q&A, Help & Troubleshooting] bobn4burton:
Any input?
[Vibrant Q&A, Help & Troubleshooting] iynfynity:
1. yes titanium.

3. nandroid backup does that.
[Vibrant Q&A, Help & Troubleshooting] buhlerbuhler:
I typically flash in this order if things:

1. Update all my apps.

2. Open titanium backup and update busybox and check settings (i have my backup folder set to "/sdcard/external_sd/TitaniumBackup" cause I like everything on my external sd card.

3. Check filters in TB set to all.

4. Run batch "Backup all apps + all system data" (i have about 150-200 apps installed at any given time, it does take a while to process that many apps, so i make sure that "settings> applications> development> keep screen awake while plugged in." is checked.

5. Reboot into clockwork recovery and perform a Nandroid backup if you so desire, and then flash disable_voodoo if you have it and reboot.

6. Walk away for 20 minutes while voodoo is disabled, then reboot.

7. Boot back into recovery and flash a custom rom.

8. Enable voodoo and reboot for voodoo conversion then into rom.

9. Reboot again after letting freshly installed rom sit untouched for ten minutes or so then open market sign in to google account.

10. Open TB and settings were set to auto sync so were good to go after it loads all info from os. Run batch of your choice but I start with restore all user apps w/ data, then restore system data.

11. Once all is done reboot into recovery and delete cache's and reboot.

This is just what I do, I rarely make a nandroid backup image because I've yet to every need to restore from one and I've ben flashing since my htc dreem, feel free to critic.

-Buhler

EDIT: it usually takes a cpl hours to be back to normal operation where you have everything setup the way you had it.

EDIT: I also didn't mention that I also backup and restore my adw settings. (but not till after the second boot when I log in to google.)

Sent from my Samsung Vibrant

Current Rom: axura

Previous Rom: nerov3

Voodoo ext4

Storage: 8GB class 6

Working Front Facing Camera

Latest Clockwork Recovery

Constantly restoring 200+ apps cause I'm addicted to flashing.
[Vibrant Q&A, Help & Troubleshooting] Br1cK'd:
the only thing i don't agree with the above post, is backing up and restoring your system data with titanium. if you inadvertantly restore system data to a different rom, it can cause lots of problems. there are a few pieces of system data that are safe, but not all. the system data i have successfully moved without problems from rom to rom are:

Bluetooth Pairings

[Bookmarks] Browser

[Calendar] Calendar Storage

[User Dict] com.android.providers.userdictionary

[Contacts/calls] Contacts Storage

and

Wifi Access points

Basically in titanium, the system data listed in green should be safe to restore, anything in red, let it be.
[Vibrant Q&A, Help & Troubleshooting] buhlerbuhler:
Yeah your right, Im selective when restoring system data, I typically only restore:

Bluetooth Pairings

[User Dict] Bluetooth Pairings

[User Dict] com.android.providers.userdictionary

[sms/mms prefs] Messaging

[sms/mms/apn] dialer storage

Sent from my Samsung Vibrant

Current Rom: axura

Previous Rom: nerov3

Voodoo ext4

Storage: 8GB class 6

Working Front Facing Camera

Latest Clockwork Recovery

Constantly restoring 200+ apps cause I'm addicted to flashing.
[Vibrant Q&A, Help & Troubleshooting] buhlerbuhler:
The items in red and with a check mark icon won't restore anything because there's no data according to the legend... I don't know why their included in the list? Or am i missing something. I'm sure there's a thread for this topic somewhere and I would look If I wasn't so gd lazy! haha but anyway I haven't had any problems restoring select system items in TB when restoring apps and data after a custom rom install. I've flashed between all the major roms on xda since the phone's release.

Thanks for commenting on my post.

-buhler

Sent from my Samsung Vibrant

Current Rom: axura

Previous Rom: nerov3

Voodoo ext4

Storage: 8GB class 6

Working Front Facing Camera

Latest Clockwork Recovery

Constantly restoring 200+ apps cause I'm addicted to flashing.
[Vibrant Q&A, Help & Troubleshooting] bobn4burton:
Awesome buhlerbuhler! Thanks for the very detailed steps... I think I'll follow tory steps when I install nero 3!