[TESTING] - NAND OMGB (1.2.3)

[mbellot]

Originally Posted by arrrghhh

Ping me if you want some help testing/triaging. You know where to find me .

+1 on this.

If you need help working through CSVs I'm more than happy to play the part of guinea pig via PM.

[anish88]

Originally Posted by arrrghhh

Ping me if you want some help testing/triaging. You know where to find me .

+1, i would be interested too

[[ACL]]

Originally Posted by arrrghhh

Ping me if you want some help testing/triaging. You know where to find me .

I had to revert back some code to begin from scratch. It's not the same issue as haret so this is going to take some research. I can't release this build without some sort of hack around this. It would set us back so for now i'm just going to continue butchering away.

Edit: I saw that sometimes the missing ringinger has nothing to do with acoustic, but the error below.

"E/RingtoneManager( 202): Failed to open ringtone null"

This unfortunately is deep in android and i'm not sure if it was on the 12/24 builds. But it only happens randomly or mostly early on.

[anish88]

I know it does not say in the change log, but is there gps support in this one?

edit - i know its asking a lot but does the 3.5mm detect the mic too? just wondering if i should check

Sent from my Touch Pro 2 using Tapatalk

[[ACL]]

Originally Posted by anish88

I know it does not say in the change log, but is there gps support in this one?

edit - i know its asking a lot but does the 3.5mm detect the mic too? just wondering if i should check

Sent from my Touch Pro 2 using Tapatalk

Unfortunately i don't have the 3.5mm with the mic to test. This shouldn't be that difficult to implement since i think this portion is shared with the h2w headset which has working mic.

No, gps is still not included. Need to stabilize acoustic before i go that route, but i do plan to release an gps update for those animals who want to test it.

[arrrghhh]

Originally Posted by [ACL]

No, gps is still not included. Need to stabilize acoustic before i go that route, but i do plan to release an gps update for those animals who want to test it.

Yea, just provide a flashable ZIP for us animals to apply GPS .

[mbellot]

Oh craaaap!!!

I can't seem to get the new system installed.

C:\adb>fastboot erase system
              erasing 'system'... FAILED (command write failed (Too many links))

and on the phone it shows

skipping @ 1477 (bad block)
cannot erase @ 1477 (bad block?)

Erasing recovery seems to be OK, but when I try to flash the recovery.img I geth the following error:

C:\adb>fastboot flash recovery recovery.img
  sending 'recovery' (4100 KB)... FAILED (status read failed (Too many  links))
finished. total time: 0.031s

and on the phone it shows

fadtboot: erase:recovery
fastboot: download:00401000

I started with a Task29, had these problems so I reloaded an old WinMo ROM (which worked fine) then reloaded the new RHODIMG.nbh via SD and I'm stuck here unable to write the recovery partition.

Help!

[[ACL]]

Originally Posted by mbellot

Oh craaaap!!!

I can't seem to get the new system installed.

C:\adb>fastboot erase system
              erasing 'system'... FAILED (command write failed (Too many links))

and on the phone it shows

skipping @ 1477 (bad block)
cannot erase @ 1477 (bad block?)

Erasing recovery seems to be OK, but when I try to flash the recovery.img I geth the following error:

C:\adb>fastboot flash recovery recovery.img
  sending 'recovery' (4100 KB)... FAILED (status read failed (Too many  links))
finished. total time: 0.031s

and on the phone it shows

fadtboot: erase:recovery
fastboot: download:00401000

I started with a Task29, had these problems so I reloaded an old WinMo ROM (which worked fine) then reloaded the new RHODIMG.nbh via SD and I'm stuck here unable to write the recovery partition.

Help!

Wow, well this is an odd one. You could always get creative and flash the recovery.img into the boot partition

fastboot flash boot recovery.img

This way you will boot into recovery automatically withot needing to press the power button. Once you are there, run the update and see if it flashes everything else. Not sure what else to suggest.

[mbellot]

Originally Posted by [ACL]

Wow, well this is an odd one. You could always get creative and flash the recovery.img into the boot partition

fastboot flash boot recovery.img

This way you will boot into recovery automatically withot needing to press the power button. Once you are there, run the update and see if it flashes everything else. Not sure what else to suggest.

No luck, looks like boot isn't big enough...

C:\adb>fastboot flash boot recovery.img
      sending 'boot' (4100 KB)... OKAY [  1.094s]
                writing 'boot'... FAILED (remote: flash write failure)
finished. total time: 2.203s

and on the phone

fastboot: download:00401000
fastboot: flash:boot
writing 4198400 bytes to 'boot'
flash_write_image: out of space

[anish88]

Originally Posted by [ACL]

Unfortunately i don't have the 3.5mm with the mic to test. This shouldn't be that difficult to implement since i think this portion is shared with the h2w headset which has working mic.

No, gps is still not included. Need to stabilize acoustic before i go that route, but i do plan to release an gps update for those animals who want to test it.

im all for the zip file

and for the mic, if i can suggest something (again i dont know how hard it is to code) but if there is a mic on the headset then enable that, but if there is no mic on the headset, then enable the mic on the phone( the on board one). just a thought. i dont know if thats hard or not. also if you need one, here is one i can think of thats really cheap. Black Stereo Headset with microphone for Apple iPhone First Generation/iPhone 3G iPhone 3GS/iPhone 4

edit: because i checked it and when there is headphones without an inline mic plugged in, the other person on the phone can not here you, as in the mic on the phone is not automatically turned on. as soon as you unplug those headphones you, and u use the handset, the other person can hear you