Build froyo_almond QSD8250

[Guest rza.android]

hi im building froyo_almond (choosecombo: qsd8250_surf) from codeaurora

i get a lot of warnings and errors due to depricated api.

Im just wondering if anyone has built this yet and once its built how do i create a working boot.img ???

i also noticed there is a froyo_test branch at codeaurora where they have a manifest for building froyo_almond on qsd8250, but havnt tried this yet

[Guest fards]

hi im building froyo_almond (choosecombo: qsd8250_surf) from codeaurora

i get a lot of warnings and errors due to depricated api.

Im just wondering if anyone has built this yet and once its built how do i create a working boot.img ???

i also noticed there is a froyo_test branch at codeaurora where they have a manifest for building froyo_almond on qsd8250, but havnt tried this yet

are you using any of the source from Dell? I think to get a working froyo build we're going to have to port it manually, when we've worked out what changes there are to the donut source. :)

I did diff the donut yesterday, so that should help a bit, but its still likely to take a while to sort out.

I've finally sat down to look at it, but my head is already spinning from trying to please 8 people who wanted their own input on a flyer for work. :P

Q8650BSDCANLYA5040.xml is the manifest I repoed adn am aiming to build with the 8250_surf vendor.

don't think there's enough difference between the 8650 and 8250 to cause too many issues.

[Guest rza.android]

ive built froyo_almond for qsd8250 and all three .img's fail including the recovery.

im building a BUILD_TINY_ANDROID=true debug kernel build

i think maybe we need to configure the kernel a little i used make oldconfig and somehow we need to specify memory locations and partition locations and the offset for the bootloader

[Guest rza.android]

ok ive built a debug tiny build which is the boot.img kernel and system.img cut-down version.

I loaded it onto the device using fastboot and and it hangs at the dell screen with dell logo. no reboots though.

I tried to adb but it couldnt find device.

boot.img is generated from kernel + ramdisk, so these need to be sorted first before building the whole froyo source and take about 5-10 mins to build.

First i need those magic numbers if anyone can help :P

the partiotion sizes and memory sizes and offsets, not sure where they are configured though.

Edited September 11, 2010 by rza.android

[Guest fards]

ok ive built a debug tiny build which is the boot.img kernel and system.img cut-down version.

I loaded it onto the device using fastboot and and it hangs at the dell screen with dell logo. no reboots though.

I tried to adb but it couldnt find device.

boot.img is generated from kernel + ramdisk, so these need to be sorted first before building the whole froyo source and take about 5-10 mins to build.

First i need those magic numbers if anyone can help :P

the partiotion sizes and memory sizes and offsets, not sure where they are configured though.

There's a thread with a modified mkbootimg

[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