[HD2 Android NAND Development] Bas2ct:
Flashin'

Heyy AngelDeath,

If you like AngelDeath, that's the name I shall use.

Still have not been able to open the tools in GPS Status. my hardware buttons react on the same way in every app. Meaning they are set to three buttons (green is call, red is standby / power down, back, windows and home are all home or recent apps). That is probably why I can't get to the tools, I can't open the menu for them because my hardware buttons are designated to other functions. maybe I could change that, I'll have to look in to that.

As you explain, the BMA150_usr should be in the ROM. In my ROM it was not present until I put it there. If it should be there on first boot (or flash), I can put it in the ROM and try that. I already started backing up my apps so I can put them in there as well. That way I still have the same ROM, but I cut out some of the standard apps and put in my 'own'. I will firt try that, after that go for the EU ROM option.

You mention AMK89783 is created on initial boot up, Is this because of addressing by the kernel or the BMA150_usr? I will probably find that out soon enough, as I will be compiling and flashing tonight. As for the button designation, I'll have to look in to that later. I would love it if I could give every button its own designation, but that will probably mean finding an app for that or writing it myself, and I'm not near to ready to writing it myself. I did manage to find some e-books about Java and Android, so I will be studying soon ;)

Just installed Droid Explorer, that's exactly what I meant. That is a lot quicker when it comes to working on my phone. Thanks for the hint. It actually led me to explore my log some more as I could now easily get to it. I noticed that during the initial boot it tried to read to my G-sensor even earlier than the error code appears. It looks like it fails to contact even there, but I'm not sure what it says exactly:

[ 2.376373] Android kernel panic handler initialized (bind=kpanic)

[ 2.376495] spi_bma150_probe: G-sensor connect with microP: start initial, kvalue = 0x0

[ 2.412506] msmfb: full update completed

[ 2.412567] msmfb: turning on panel

[ 2.412597] lcdc_unblank: ()

[ 2.412628] auo_panel_unblank

[ 2.430419] __spi_bma150_set_mode: BMA get into SLEEP mode!

The errors come somewhat later...

[ 2.857635] AKM8973 compass driver: init

[ 2.857757] msm_i2c msm_i2c.0: error, status c8 (1C)

[ 2.857818] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.867950] msm_i2c msm_i2c.0: error, status 43c8 (1C)

[ 2.868011] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.878051] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.878112] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.888153] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.888183] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.898223] msm_hsusb_phy_reset

[ 2.898254] msm_i2c msm_i2c.0: error, status c8 (1C)

[ 2.898345] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.908416] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.908447] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.918518] msm_i2c msm_i2c.0: error, status 43c8 (1C)

[ 2.918579] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.928619] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.928680] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.938720] msm_i2c msm_i2c.0: error, status 63c8 (1C)

[ 2.938751] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.948822] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.948852] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.958862] AKI2C_TxData retry over 10

[ 2.958892] AKM8973 akm8973_probe: set power down mode error

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

Like I said before, there is

no

BMA150_usr in the ROM when clean. Maybe putting it in makes some difference. Weird thing is, I don't see an init for the first probe. or I'm not seeing it reading my log. Could be because I don't know the code. I'll attach the log so you can see what I mean, it's too long to post here.

View attachment DMESG.TXT

>Just took a peak in the system\bin and noticed that BMA150_usr is executable, akmd is executable? two drivers for one device?

Again, I really really appreciate your efforts to help me (us, I reckon there are more HD2's with the same problem)!!

I'[ll be flashin' now.

Best,

Sebastian

Tried flashing with BMA150_usr in system\bin, failed (bootscreen hang for about 30 min.). Back to the same ROM, will check log, probably same.