Has anyone tried to build Donut or Eclair using dell source???

[Guest rza.android]

Hi has anyone managed to make a working build of Donut or Eclair for Streak using dells source ???

im wondering if i get donut and it builds is it going to boot ??? just from including the kernel source ???

or do i have to make specific streak changes ???

Edited September 11, 2010 by rza.android

[Guest zelman]

Hi has anyone managed to make a working build of Donut or Eclair for Streak using dells source ???

im wondering if i get donut and it builds is it going to boot ??? just from including the kernel source ???

or do i have to make specific streak changes ???

readme

[Guest fards]

that was my plan, but I ended up repoing the froyo instead.

I may grab the eclair to try it, trying to find my spare external hard-drive, laptop one is nearly full :P

[Guest Stephen Hyde]

fards have you managed any sort of workign boot.img yet

[Guest fards]

nope. but I was playing with froyo, just started repoing the codeauroura eclair_strawberry so I'll do what dell say, drop the kernel into that and build from there.

Otherwise, I wonder about grabbing that, making the kernel, then stick the created zImage into the main android source from that git, and build android from there, with the kernel as a prebuilt..

but hey ho, repo first...

If anyone has a way of speeding up grabbing the sourcetree please let me know ! 59kbs is doing my head in :P

[Guest Stephen Hyde]

i tried building the kernel and it wont build using the streak .config

[Guest fards]

what about dropping the entire folder in ?

build against what version and git?

[Guest Stephen Hyde]

i tried building the kernel outside any tree (ie on its own) and it failed and dropping it into the froyo source fails also with a totally different error

[Guest fards]

hopefully it won't take too long to build with the eclair and we can see then :P

when it finishes repoing in about another hour or two

[Guest fards]

buid fails here on ubuntu x64 GCC 4.4.4

got a gcc4.5 update ready I may try that.

dalvik/libnativehelper/include/nativehelper/jni.h:489: note: the mangling of 'va_list' has changed in GCC 4.4

make[2]: *** [fs] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/media/disk-1/dell_cooking/kernel'

make: *** [out/target/product/qsd8250_surf/obj/KERNEL_OBJ/arch/arm/boot/zImage] Error 2

make: *** Waiting for unfinished jobs....

[Guest crash6]

try gcc-4.3 and g++-4.3 and create symlinks

ln -s gcc-4.3 gcc

ln -s g++-4.3 g++

This is how I was able to get past but now Im stuck here.

host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.4/libstdc++.so when searching for -lstdc++

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.4/libstdc++.a when searching for -lstdc++

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.4/libstdc++.so when searching for -lstdc++

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.4/libstdc++.a when searching for -lstdc++

/usr/bin/ld: cannot find -lstdc++

collect2: ld returned 1 exit status

make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp] Error 1

make: *** Waiting for unfinished jobs....

host SharedLib: libneo_cgi (out/host/linux-x86/obj/lib/libneo_cgi.so)

EDIT:

ok found a fix for that

sudo apt-get install g++-multilib

now she is building

Will post update shortly

Edited September 12, 2010 by crash6

[Guest fards]

Cool

I'll give it ago with gCC 4.5 later see if that works, if not I'll drop back to 4.3.

I remember reading that 4.4 had issues, but I thought someone had got a better way around it. Maybe not :P

I did update to 4.5 last night and do make installclean before make j -4 again, and it seemed to complete with out errors, but couldn't see zImage in the /out

But then I had fallen asleep by the time it had finished..

[Guest rza.android]

Right it seems the big problem is the generated boot.img is incorrect for working on the streak.

on acer liquid they had to use a custom mkbootimg setting the correct base address and alter the bootimg header

Does anyone have custom mkbootimg for streak?

anyone know streaks base address?

anyone know what to change in the bootimg header?

if any of the above is slightly incorrect device will hang at dell logo as the data and locations of bootloader kernel ramdisk is corrupt.

I also tried unpack*.pl and repack*.pl

On superboot and the values seem incorrect for streak as gzips didnt open

[Guest Stephen Hyde]

on a related note i was looking through the config.gz from my streak today and noticed that it has all cgroup/cpuacct options disabled, i thought that these were requirements for eclair to work properly. and may explain speed issues to in theory

[Guest crash6]

so i've managed to compile the kernel

  OBJCOPY arch/arm/boot/zImage

  Kernel: arch/arm/boot/zImage is ready

make[1]: Leaving directory `/home/crash/codeaurora/kernel'

Built the boot.img

when booting I do not get the Dell logo. I get

ANDROID _

The phone is in portrait and upside down.........

Edited September 12, 2010 by crash6

[Guest fards]

so i've managed to compile the kernel

  OBJCOPY arch/arm/boot/zImage

  Kernel: arch/arm/boot/zImage is ready

make[1]: Leaving directory `/home/crash/codeaurora/kernel'

But for some reason there is no zImage.

Anyone have any ideas?

Have you tried make from inside the kernel folder?

Stephen I really don't know, I'm still busily reading up on android as much as I can.

At the mo I'm getting baffled, the more I read.

Have you compared the beta builds, at best I suspect they just reused the same kernel for 1.6 and 2.1

Still can't believe they let an eng compiled build out.

[Guest Stephen Hyde]

fards feel free to drop me a pm with any questions you have- android and it's internals are something i know a fair bit of so can probably answer any questions,

if anyone who still have a 1.6 or leaked 2.1 devcie can grab me /proc/config.gz it would be appreciated too

[Guest fards]

so i've managed to compile the kernel

  OBJCOPY arch/arm/boot/zImage

  Kernel: arch/arm/boot/zImage is ready

make[1]: Leaving directory `/home/crash/codeaurora/kernel'

Built the boot.img

when booting I do not get the Dell logo. I get

The phone is in portrait and upside down.........

What do you do to get a working boot.Img?

[Guest Stephen Hyde]

how did you mange that one ? im lucky to get a working boot.img ;D tho i found a fairly reliable way to build ones with new initrd's now not so

[Guest crash6]

how did you mange that one ? im lucky to get a working boot.img ;D tho i found a fairly reliable way to build ones with new initrd's now not so

That was the easy part.

Using the changes to mkbootimg outlined in another post:

Besides "makebootimg.c" must be modified because "-base" argument is not working in Dell Streak:


CODE

		/* default load addresses */

	//hdr.kernel_addr =  0x10008000;

	//hdr.ramdisk_addr = 0x11000000;

	//hdr.second_addr =  0x10F00000;

	//hdr.tags_addr =	0x10000100;


	hdr.kernel_addr =  0x20008000;

	hdr.ramdisk_addr = 0x24000000;

	hdr.second_addr =  0x20F00000;

	hdr.tags_addr =	0x20000100;

This seems to work fine for a completely stock kernel but any modifications to the kernel (any at all) seem to cause it to not boot. My kids are driving me crazy to go to the park. Gotta shut this down for the day but Ill do some debugging at work tomorrow and see what I can find.

[Guest fards]

smokku has just said he made a boot image using the mkbootimg from froyo source, which is promising :P

[Guest Stephen Hyde]

yup very true problem is we have issues with booting anything other than dells android build at moment- anyone fancy getting nexus1 2.1 system binaries and comparing them to dells in hexedit asi suspect thiers edits in them

[Guest fards]

yup very true problem is we have issues with booting anything other than dells android build at moment- anyone fancy getting nexus1 2.1 system binaries and comparing them to dells in hexedit asi suspect thiers edits in them

we could compare the 1.6 source of the nexus v the streak :P

[Guest Stephen Hyde]

1.6 is possible but i said 2.1 as thats a good place to start id say - just we are getting weird memory errors on froyo at moment so i suspecting dell have changed some android source files to get around it

[Guest vladistan]

So any update on this?

Did anybody managed to compile and boot a custom kernel for Streak?

All the Custom ROMs I seen out there seem to re-use the Dell's binary either 2.6.29 or 2.6.35.

Just looking for confirmation to know that I am not hacking alone in the dark.