[TESTING] XDAndroid GBX0C 2.3.7 Build

[arrrghhh]

Originally Posted by Sc/ant864

Arrrghhh which version of Eclipse is relevant to this build? And should I start a different thread for these questions so I don't fill up the thread with this? Also did you have time to check the log I pmed you?

Sent from my ppcT7380 Ti/GBX0B via PPCG app

Same dreaded error everyone gets:

01-17 21:13:13.740 W/AudioTrack( 1298): obtainBuffer timed out (is the CPU pegged?) 0x46dd50 user=000012c0, server=00000000

I don't know where the "actual" error is. I don't know if anyone has found it yet... Bleh.

I'll see if some others can take a peek, as your logs do capture it well it seems... And Eclipse..? That's for development, you don't need it. You're on Windows right? Droid Explorer & you're done.

I also have a new build (check the site, the link will be the same but timestamp will update... Not on the filename, on the actual site.) Sorry, I didn't want to make it look like a whole new build, so I kept the filename the same.

Everyone should grab the full bundle. It includes a new .27 acoustic kernel that should fix some problems, and there's a lot of userland fixes:

• MMS should be fixed for Sprint users
• XDAndroid will now show as the provider
• GLES put back in (whoops)
• Network-based location put back in (which was working before, but this last boot it didn't...? Let me know on this guys, I might need another update... Definitely seems broken!! What the heck. There'll be another update, sorry folks.)
• hyc's dmesg binary baked into the rootfs (timestamps... in dmesg!)

Uploading now, should be live soon.

[wizardknight]

I am not sure what changed, but when I tried this most recent mini-update I have my sound working correctly.

[arrrghhh]

Originally Posted by wizardknight

I am not sure what changed, but when I tried this most recent mini-update I have my sound working correctly.

There was A LOT of acoustic changes in this build. Glad it's working correctly - everyone else, download the full bundle, and REPLACE EVERYTHING!! I've added a lot of updates across the board, and I don't want people running partial stuff.

You should be able to reuse your data.img...

I'm still not able to get netloc to work... I am just scratching my head as to why it worked at first and now it doesn't. I'll keep working on it, but so far that seems to be the only thing I set out to fix that isn't.

Bring on that feedback guys!

[Sc/ant864]

Originally Posted by arrrghhh

Same dreaded error everyone gets:

01-17 21:13:13.740 W/AudioTrack( 1298): obtainBuffer timed out (is the CPU pegged?) 0x46dd50 user=000012c0, server=00000000

I don't know where the "actual" error is. I don't know if anyone has found it yet... Bleh.

I'll see if some others can take a peek, as your logs do capture it well it seems... And Eclipse..? That's for development, you don't need it. You're on Windows right? Droid Explorer & you're done.

I also have a new build (check the site, the link will be the same but timestamp will update... Not on the filename, on the actual site.) Sorry, I didn't want to make it look like a whole new build, so I kept the filename the same.

Everyone should grab the full bundle. It includes a new .27 acoustic kernel that should fix some problems, and there's a lot of userland fixes:

• MMS should be fixed for Sprint users
• XDAndroid will now show as the provider
• GLES put back in (whoops)
• Network-based location put back in (which was working before, but this last boot it didn't...? Let me know on this guys, I might need another update... Definitely seems broken!! What the heck. There'll be another update, sorry folks.)
• hyc's dmesg binary baked into the rootfs (timestamps... in dmesg!)

Uploading now, should be live soon.

Ok, Thanks man I'll jump on that and the new build tonight....excited!
Edit- I forgot to ask you if you still need CSV files?
Sent from my ppcT7380 Ti/GBX0B via PPCG app

[arrrghhh]

Originally Posted by Sc/ant864

Ok, Thanks man I'll jump on that and the new build tonight....excited!
Edit- I forgot to ask you if you still need CSV files?

Yea, CSV's are still needed at the root of the SD card.... We haven't done much work on unifying the CSV's to be honest. Just squashin bugs right now, once we get down to a level where we're at least matching FroYo for oustanding bugs (IE fixed all regressions) I think work can start on implementing the CSV's into the system image and an actual release can be done!

Thanks to everyone for testing. Keep up the feedback, so we can get a solid GB build!

[boneskid1]

not seeing the new build when i click on the download from the for the build it brings up the date of 12-31-2011 which was the first version of this build. if i am wrong please excuse me i can be a bit blind sighted at times

[arrrghhh]

Originally Posted by boneskid1

not seeing the new build when i click on the download from the for the build it brings up the date of 12-31-2011 which was the first version of this build. if i am wrong please excuse me i can be a bit blind sighted at times

Read what I said. Filename won't change. Timestamp on the file, however, has.

Originally Posted by arrrghhh

I also have a new build (check the site, the link will be the same but timestamp will update... Not on the filename, on the actual site.) Sorry, I didn't want to make it look like a whole new build, so I kept the filename the same.

[EyeB]

don't know if it matters, saw it on last startup file for Rhod400 (Didn't check other ones)
but the line that says

set initrd initrd.gzset initrd_offset 0x00a00000

Shouldn't it be

set initrd initrd.gz
set initrd_offset 0x00a00000

I don't know if the startup thing sees the set part when it is part of another word, I put the space in mine though when I saw it, just forgot to comment on it until I looked to see if anything changed in startup with this update

[wizardknight]

Found what might be a minor issue. I tried to run updates from the market, and superuser gave "Package file was not signed correctly."

Anyone else get this error?

It is not that big of a deal, but might want to peek at it before it is is released.

[EyeB]

the superuser error is common, there is an app in market called superuser fix or something like that, it happens when devs put superuser/root roms that uses an older signed thing (don't know correct name), but the superuser app guy talks about it on his webpage