[DEV] AOSP Dev for Zte Blade

[Guest fp30]

grrr adb is now broken for me using alpha3. anyone else have this?

EDIT: oops it was some change I made to init.rc that broke it. alpha3 is fine

Edited November 29, 2011 by fp30

[Guest abaj]

which partition size should i have to run alpha 3 and how to change it?

[Guest t181]

grrr adb is now broken for me using alpha3. anyone else have this?

It was broken for me too. But I restarted my phone, and the problem was solved.

So try restart your phone, maybe your PC, and turn on/off debugging mode. ;)

[Guest ayziaa]

which partition size should i have to run alpha 3 and how to change it?

I'm not really the expert here but in the first post t0mm13b said

"Head over to XDA's Zte Blade forum to get the TPT, Gen1 to Gen2 TPT v8 Stock which has 210Mb system partition layout as part of TPT."

[Guest fp30]

@t0mm13b I flash alpha3 and adb works fine. Then I flash replace init.rc and init.blade.rc with yours from an earlier post and flash the new boot.img and I dont have adb. why does this happen? am I missing some step here?

when I say I dont hae adb I mean adb doesnt see any connected device

Edited November 29, 2011 by fp30

[Guest hedgepigdaniel]

I'm going on schoolies for the next two weeks, so someone else might have to give their computer a kick if you want to try new code out. I expect plenty of progress when I get back!

[Guest Sami Beck]

I'm going on schoolies for the next two weeks, so someone else might have to give their computer a kick if you want to try new code out. I expect plenty of progress when I get back!

6 Core AMD Phenom @ 3.3Ghz

8GB RAM

Any use?

[Guest fp30]

6 Core AMD Phenom @ 3.3Ghz

8GB RAM

Any use?

yes :D

Right, Anyone willing to try out the patchset committed to github that was mentioned in posting #419 on previous page, and use the bootimage from post #407 on previous page again, to see if that resolves the radio telephony from getting b0rk3d up! :) :D

Edit:

Really, its a change in frameworks/base/telephony/java/com/android/internal/telephony/MccTable.java line 248, from this

 if (!country.isEmpty()) {

to

if (country != null && !country.isEmpty()) {

I added an extra checking for the WifiManager found in frameworks/base/wifi/java/android/net/wifi/ line 771, from this:

mService.setCountryCode(country, persist);

to this:

if (country != null) mService.setCountryCode(country, persist);

Errm, yes, it does require a recompile of the entire thing again :rolleyes:

Edited November 29, 2011 by fp30

[Guest hedgepigdaniel]

<br />6 Core AMD Phenom @ 3.3Ghz<br />8GB RAM <br />Any use?<br />

<br /><br /><br />

Should be ok. I have sandy bridge mobile i7 (4 cores, 8 threads) and 8G RAM and it takes an hour. For anyone who wants to build:

1. Install Linux on your computer. Ubuntu 11.10 worked well for me. 64 bit is highly recommended.

2. Follow instructions here to initialise a build environment and download AOSP source (get the master branch): http://source.android.com/source/initializing.html

3. Make a folder called something like ics4blade and clone the git repository here into it (when changes are made you can pull the latest from github, detailed instructions are on github.com)https://github.com/t0mm13b/ics4blade.

5. Copy the AOSP source files into your ics4blade folder, without replacing the files that are already there (those are the ones we have changed).

6. Follow instructions here: http://wiki.cyanogenmod.com/wiki/ZTE_Blade:_Compile_CyanogenMod_(Linux) to copy proprietary files from your blade.

7. Follow instructions here to build: http://source.android.com/source/building.html. You can run "lunch" with no arguments to select from build targets, and if you add "otapackage" as an argument to "make" it will make a. update.zip, otherwise it will make a system.img.

8. You can use dsixda's script on xda to make an update.zip from a system.img file that you build + a boot.img file that someone posts here. That way you can get an easily flashable package with the latest stuff.

9. Get the latest ics gapps zip from here: http://download.clockworkmod.com/test/ (and remove extraneous stuff if you want to save space)

10. Victory dance, post your results for the world to see.

It's worth persisting if you are a bit out of your depth - its very satisfying when you succeed in your first build!

[Guest t0mm13b]

Bad news, did not work. Kept bootlooping.

/system/bin/rild is chmod'd 0755 and running.

/dev/socket/rild present.

Its definitely related to some permission or ownership in which java's telephony cannot see the rild socket.

Will investigate shortly. B)

[Guest abaj]

I tried to install alpha 3 but it showed a message "random offset:0x1c0". What does it mean?

[Guest Maxsas360]

I can compile too. If someone could provide me with a guide how to.

Intel Core I5 2500k @ 4.5ghz

8gb ram.

[Guest furrabbit.nh]

I can compile too. If someone could provide me with a guide how to.

Intel Core I5 2500k @ 4.5ghz

8gb ram.

Take a look at post 432

[Guest FelixL]

Guys, I found that the people who are developing ICS for the Nexus One have fixed the home button behavior.

[...]

http://forum.xda-dev...d.php?t=1366897

http://forum.xda-dev...d.php?t=1348670

Haven't found anything there how they've done it, but had a look yesterday evening at the keylayouts, and found the problem myself:

/system/usr/keylayout/Generic.kl

Change MOVE_HOME to HOME for key 102

key 102 was the default for HOME all the time, they changed it with ICS, that's the reason all devices have this problem.

Editing Generic.kl is a little bit dirty since it shouldn't be changed, a new one for the device should be made and used. Don't know how to do this, editing Generic.kl works :P

Third way would be to change the identifyer the key sends to the one that is default in ICS.

Wanted to write this yesterday, but obviously had no connection with the Blade, my WAP-enabled emergency phone didn't like MoDaCo -.-

[Guest Maxsas360]

Ok then will try doing that tomorrow

[Guest Matty-p]

I'm going on schoolies for the next two weeks, so someone else might have to give their computer a kick if you want to try new code out. I expect plenty of progress when I get back!

Enjoy it ! ( but don't do anything tooooo stupid ) thanks for all the contributions so far - looks like ill' be dusting off my environment and bringing it upto date tomarow then :)

[Guest furrabbit.nh]

Haven't found anything there how they've done it, but had a look yesterday evening at the keylayouts, and found the problem myself:

/system/usr/keylayout/Generic.kl

Change MOVE_HOME to HOME for key 102

key 102 was the default for HOME all the time, they changed it with ICS, that's the reason all devices have this problem.

Editing Generic.kl is a little bit dirty since it shouldn't be changed, a new one for the device should be made and used. Don't know how to do this, editing Generic.kl works :P

Third way would be to change the identifyer the key sends to the one that is default in ICS.

Wanted to write this yesterday, but obviously had no connection with the Blade, my WAP-enabled emergency phone didn't like MoDaCo -.-

Wonderfull thanks.... works great changed with root explorer inbuilt text editor, works great.

Edited November 29, 2011 by furrabbit.nh

[Guest t0mm13b]

Haven't found anything there how they've done it, but had a look yesterday evening at the keylayouts, and found the problem myself:

/system/usr/keylayout/Generic.kl

Change MOVE_HOME to HOME for key 102

key 102 was the default for HOME all the time, they changed it with ICS, that's the reason all devices have this problem.

Editing Generic.kl is a little bit dirty since it shouldn't be changed, a new one for the device should be made and used. Don't know how to do this, editing Generic.kl works :P

Third way would be to change the identifyer the key sends to the one that is default in ICS.

Wanted to write this yesterday, but obviously had no connection with the Blade, my WAP-enabled emergency phone didn't like MoDaCo -.-

Thanks FelixL for sharing and that did the trick, why change it in the first place and cause disruption! xD :) +1 from me :)

[Guest fp30]

So does anybody know why adb stops recognising my phone if I flash an edited boot.img?

[Guest t0mm13b]

What's in your init.blade.rc?

# Setup android gadget

   write /sys/module/g_android/parameters/serial_number ICS-Blade

   write /sys/module/g_android/parameters/product_id 0x1351 

It's the last line that should do the trick :)

[Guest Sami Beck]

yes :D

Tell me what I need to do and its yours!

[Guest fp30]

What's in your init.blade.rc?

# Setup android gadget

   write /sys/module/g_android/parameters/serial_number ICS-Blade

   write /sys/module/g_android/parameters/product_id 0x1351 

It's the last line that should do the trick :)

its there for sure. no idea why its not working, I guess its the way im packing the boot.img.

anyway on another note. I raplaced boot.img with your experimental boot.img from the previous page but i STILL dont get rild sockets open.

srw-rw---- bluetooth bluetooth 2011-11-29 22:48 bluetooth

srw-rw---- bluetooth bluetooth 2011-11-29 22:46 dbus

srw-rw---- bluetooth bluetooth 2011-11-29 22:48 dbus_bluetooth

srw-rw---- root inet 2011-11-29 22:46 dnsproxyd

srw------- system system 2011-11-29 22:46 installd

srw-rw-rw- root root 2011-11-29 22:46 keystore

srw-rw---- root system 2011-11-29 22:46 netd

srw-rw-rw- root root 2011-11-29 22:46 property_service

srw-rw---- root mount 2011-11-29 22:46 vold

srw-rw-rw- root root 2011-11-29 22:46 zygote

what else did you do?? or what else do I need to do to open? was it only the boot.img that you changed?

[Guest davidnintendo]

Great news, everyone! Apparently hardware acceleration is now working on the Desire and the HTC HD2, both with the Adreno 200 GPU like the Blade!

http://forum.xda-developers.com/showthread.php?t=1354309

This is the github repository with the fix. Apparently, what they did was changing the graphics system so it could use the old drivers.

https://github.com/TwistedUmbrella/android_frameworks_base/commit/0ff021ed0d258074ef6d87597e9e74591458bfc3

[Guest fp30]

Great news, everyone! Apparently hardware acceleration is now working on the Desire and the HTC HD2, both with the Adreno 200 GPU like the Blade!

http://forum.xda-dev...d.php?t=1354309

This is the github repository with the fix. Apparently, what they did was changing the graphics system so it could use the old drivers.

https://github.com/T...e9e74591458bfc3

sweet. we're getting there... just the radios to go and we will have a fully functioning ROM that just needs tweaking to the max!

[Guest fp30]

Tell me what I need to do and its yours!

here we go... some compiling for you to do :P

you could make the patches given here: https://github.com/T...e9e74591458bfc3 (thanks davidnintendo)

and compile to see if we can have harwdware acceleration going.

also (maybe as a separate build) you try adding t0mmi13b's patches:

Right, Anyone willing to try out the patchset committed to github that was mentioned in posting #419 on previous page, and use the bootimage from post #407 on previous page again, to see if that resolves the radio telephony from getting b0rk3d up! :) :D

Edit:

Really, its a change in frameworks/base/telephony/java/com/android/internal/telephony/MccTable.java line 248, from this

 if (!country.isEmpty()) {

to

if (country != null && !country.isEmpty()) {

I added an extra checking for the WifiManager found in frameworks/base/wifi/java/android/net/wifi/ line 771, from this:

mService.setCountryCode(country, persist);

to this:

if (country != null) mService.setCountryCode(country, persist);

Errm, yes, it does require a recompile of the entire thing again :rolleyes:

if anyone else has any other thoughts let us know but I think we're getting there :D