489 replies to this topic

[BlcakFox]

trying to download the source... the speed is about 5 kB/s, so long time to go...
any ideas what soft will I need to compile/build it?

[Sebastian404]

BlcakFox, on Jan 6 2011, 15:10, said:

trying to download the source... the speed is about 5 kB/s, so long time to go...
any ideas what soft will I need to compile/build it?

Unfortunatly the Froyo Source for the Blade also was pushed out at the same time, so theres a riot broken out over that with everyone in the world downloading it at once..

Theres loads of tutorials around the net for how to do it.... but basicaly.. unzip it, then

make ARCH=arm CROSS_COMPILE=~/android/prebuilt/toolchain/arm-eabi-4.4.0/bin/arm-eabi- $1

you need to adjust that for your enviorment of course...

and based on experience with the ZTE Blade, it wont compile from the off, so you'll need to fix the bugs/typos in their source.

[BlcakFox]

finally downloaded. now installing linux on virtual machine, and then I'll try to build it.
if anybody wants, I can upload the source to some filesharing (ie depositfiles)

[Sebastian404]

BlcakFox, on Jan 6 2011, 16:45, said:

finally downloaded. now installing linux on virtual machine, and then I'll try to build it.
if anybody wants, I can upload the source to some filesharing (ie depositfiles)

It might be a good idea

[BlcakFox]

building died at

  CHK	 include/linux/version.h
  CHK	 include/linux/utsrelease.h
  SYMLINK include/asm -> include/asm-x86
ln: creating symbolic link `include/asm': Operation not permitted
make: *** [include/asm] Error 1

alternate url to download the source
http://depositfiles....files/uxouqywz6

[serialmonkey]

BlcakFox, on Jan 6 2011, 18:08, said:

alternate url to download the source
http://depositfiles....files/uxouqywz6

Ta, I'll have a play later today.

[serialmonkey]

Sebastian404, on Jan 6 2011, 13:11, said:

Is that with your build? or my b8?    if its mine let me know what you did so I can fix it and promote it to 'final'

Nope, mine - I had my own init.rc which wasn't setting permissions on /system

[Sebastian404]

serialmonkey, on Jan 6 2011, 22:13, said:

Nope, mine - I had my own init.rc which wasn't setting permissions on /system

Cool, I've removed the old builds and promoted b8 to 'final'

Im trying to get the kernel built, so I can then rebuild another version with EXT3 support

[serialmonkey]

Spent 5 minutes on it this morning. I can get it to compile with the attached patch, but it doesn't boot (surprise surprise). I just spliced it into my recovery.img.

Might have time later today to have another look - I'm currently fighting with java compiliation issues with cyanogen-froyo-stable

Edited by serialmonkey, 07 January 2011 - 12:43 AM.

[Sebastian404]

serialmonkey, on Jan 7 2011, 00:40, said:

Spent 5 minutes on it this morning. I can get it to compile with the attached patch, but it doesn't boot (surprise surprise). I just spliced it into my recovery.img.

Might have time later today to have another look - I'm currently fighting with java compiliation issues with cyanogen-froyo-stable

I've remebered why I hated JAVA so much... its scary how much of my Unviersity course has come flooding back... along with memories of the pain and suffering.....  Im starting to think I blanked a lot of the horror out....

[serialmonkey]

Sebastian404, on Jan 7 2011, 00:43, said:

I've remebered why I hated JAVA so much... its scary how much of my Unviersity course has come flooding back... along with memories of the pain and suffering.....  Im starting to think I blanked a lot of the horror out....

This is something they have broken - lots of people have reported the issue, but I can't google up a solution at this stage. Might just have to remove the offending code and see what happens. It's basically this problem here - http://pastebin.com/VunEG4d3

[Sebastian404]

serialmonkey, on Jan 7 2011, 00:45, said:

This is something they have broken - lots of people have reported the issue, but I can't google up a solution at this stage. Might just have to remove the offending code and see what happens. It's basically this problem here - http://pastebin.com/VunEG4d3

your building the froyo branch, not the gingerbread or eclair?

[serialmonkey]

Sebastian404, on Jan 7 2011, 00:46, said:

your building the froyo branch, not the gingerbread or eclair?

Correct, both the froyo and froyo-stable branches fail with the same error.

[Sebastian404]

serialmonkey, on Jan 7 2011, 00:47, said:

Correct, both the froyo and froyo-stable branches fail with the same error.

you could try grabbing an ealier commit version I guess... tho Im not sure how you'd know when they introduced that bug

[hajj_3]

is this available to buy in UK or U.S? if so what price?

[serialmonkey]

So Sebastian, let's say you got the cryanogen froyo stable branch to compile into an update zip and convinced the recovery to load it. You reboot and get the ANDROiD text for 60 seconds, then the device just reloads into recovery. USB never comes up.

Where would you start ? :-)

P.S. we néed to add ro.product.name to the props file of the recovery so it accepts an update zip.

P.P.S. Backup/recovery definitely works :-D

Edited by serialmonkey, 07 January 2011 - 11:29 AM.

[raniah]

@Sebastian404 & @serialmonkey:

It would be really nice if you guys succeed in what you're trying to do; ZTE support doesn't seem much enthusiastic in the 2.2 upgrade. I'll be following this thread

[Pegaxs]

serialmonkey, on Jan 7 2011, 22:26, said:

P.P.S. Backup/recovery definitely works :-D

I will second that... recovery definatly working...

[Sebastian404]

serialmonkey, on Jan 7 2011, 11:26, said:

So Sebastian, let's say you got the cryanogen froyo stable branch to compile into an update zip and convinced the recovery to load it. You reboot and get the ANDROiD text for 60 seconds, then the device just reloads into recovery. USB never comes up.

Where would you start ? :-)

harsh language mostly...  have you tried swearing at it?

First thing I'd do is try the image you made in the emulator... see if that gives you any better results..  

Next thing I'd try using the 'standard' boot.img with your built system.img see if its something to do with your kernel/boot build...

serialmonkey, on Jan 7 2011, 11:26, said:

P.S. we néed to add ro.product.name to the props file of the recovery so it accepts an update zip.

it is in usb.conf.. it should get picked up/set by the usbconfig process....

I've been using clockworkmod on the blade for a while without having it set... sorry still not got around to building some update zips for the V9 yet...  been hella busy this week..

Edited by Sebastian404, 08 January 2011 - 01:04 AM.

[serialmonkey]

Not alot of success today.

Tried to build a base android froyo (not cyranmod). Good news is that it kinda booted - hung at the green screen but adb was alive. At that point I decided to restore back to my backup and everything went downhill.

Getting into 'adb shell' is a real hit-and-miss. 90% of the time I get the '#' prompt, but then it just hangs (like we saw in the past). Recovery is also having troubles seeing all my partitions. I get errors like 'Can't mount /dev/block/mtdblock4 (File exists)'. My backups won't restore and nothing boots.

So at 3am, it's time to sleep and hopefully I'll work out how to revive it in the morning.