61 replies to this topic

[fards]

http://opensource.de...eleases/streak/

Edited by fards, 09 September 2010 - 07:27 AM.

[fards]

Although they've ALREADY got the aero source out...

http://opensource.de...eases/aero/1.5/

[Asphytxtc]

ooh, exciting stuff! looking forward to seeing what sort of things we can do with the stuff now..

I don't know much on how the android kernel world works, do you think it'll all be pure source we can tinker with? Or will we see various hardware bits done in crappy binary blobs ala nvidia?

[Meltus]

Finally!!  
I bet they will only release the 1.6 source and then take about 6 months to get the 2.1/2 source out

[fards]

Tbh i havent looked at the Aero source yet, but I guess that will give us the best clues as to what we're likely to get. Can't see there being that much proprietary in there looking at config.gz and build.prop.
References to build.Austin I guess are theirs..

Edited by fards, 08 September 2010 - 11:35 AM.

[fards]

looks like the Aero at least is using minimal proprietary blobs..

Quote

build steps of these packages
1, bluez
1)in cupcake source tree, replace "external/bluez" folder with content of
bluez.tar.gz
2)run ". build/envsetup.sh" in the root dir of cupcake source tree
3)mmm external/bluez
2, openobex
1)Extract openobex.tar.gz to "external" folder of cupcake source tree
2)run ". build/envsetup.sh" in the root dir of cupcake source tree
3)mmm external/openobex
3, webkit
1)backup and remove "external/webkit" folder in cupcake source tree
2)Extract webkit_open_source.tar.gz to "external" folder
3)run ". build/envsetup.sh" in the root dir of cupcake source tree
4)mkdir -p out/target/product/generic/obj/STATIC_LIBRARIES/libwap_intermediates/
5)copy libwap.a in webkit_open_source.tar.gz to the "libwap_intermediates" folder
6)copy Surface.h in webkit_open_source.tar.gz to frameworks/base/include/ui/
7)mmm external/webkit
4, ppp
1)Extract ppp.tar.gz to "external" folder of cupcake source tree
2)run ". build/envsetup.sh" in the root dir of cupcake source tree
3)mmm external/ppp
5, Linux kernel
1) make blaze_defconfig
2) make
6, blob (tip:must build Linux kernel firstly before build this package)
1) install arm-linux-4.1.1
2) ./setup.sh PRODUCT=BLAZE linux_kernel_path(for
example:/home/b130/work/linux/lnx2625pxa_release/)
3) make
7, wlan
1)Extract wlan.tar.gz to "external" folder in cupcake source tree
2)backup and remove "wpa_supplicant" folder in "external/" folder of cupcake
source tree
3)backup and replace "wifi" folder in hardware/libhardware_legacy/ of cupcake with
the "wifi" folder in this package
4)move "wapi" folder in this package to hardware/libhardware_legacy/ of cupcake
5)mv wapi.h to hardware/libhardware_legacy/include/hardware_legacy/wapi.h
6)run ". build/envsetup.sh" in the root dir of cupcake source tree
7)make external/wlan

Edited by fards, 08 September 2010 - 11:33 AM.

[fards]

1.12. ??

[gingernator]

fards, on Sep 9 2010, 07:05, said:

1.12. ??

[TXT] HOW-TO-BUILD.txt                  09-Sep-2010 01:36  1.9K  
[   ] streak_1.12_bluez.tar.gz          09-Sep-2010 01:37  1.5M  
[   ] streak_1.12_jpeg.tar.gz           09-Sep-2010 01:37  687K  
[   ] streak_1.12_kernel.tar.gz         09-Sep-2010 01:43   74M  
[   ] streak_1.12_wekit.tar.gz          09-Sep-2010 01:44   19M  
[   ] streak_1.12_wpa_supplicant.tar.gz 09-Sep-2010 01:44  695K

[gingernator]

Is this actually happening???

[fards]

Looks like it.. good job I freed a 25gb partition on my work PC..

[gingernator]

Someone needs to do a quick and dirty vanilla build, STAT!

[Sader0]

Cant believe it !
But in case this is not another accidental leak....then they made 1st step to grow in my eyes

Edited by Sader0, 09 September 2010 - 07:42 AM.

[Stephen Hyde]

*me starts downloading to my build pc methinks its hackin time

[fards]

its donut, so don't get too excited..

but it does show one thing, I was right when I said they were using codeauroara kernel

[fards]

now we've got this, I'm thinking of the best way to get it into a froyo or eclair kernel.

diff against the codearoura kernel to see what they changed then patch the froyo with the same ?

any other thoughts?

[Stephen Hyde]

how about trying to boot using the current kernel first as froyo *should* work with it although not perfectly

am syncing froyo tree from codearoura as i type

Edited by Stephen Hyde, 09 September 2010 - 09:47 AM.

[fards]

Stephen Hyde, on Sep 9 2010, 10:43, said:

how about trying to boot using the current kernel first as froyo *should* work with it although not perfectly

am syncing froyo tree from codearoura as i type

lol

I was going to play with eclair, but am repo syncing the donut_strawberry (as its the last donut to get some work) to diff it first

[Stephen Hyde]

fards, on Sep 9 2010, 10:53, said:

lol

I was going to play with eclair, but am repo syncing the donut_strawberry (as its the last donut to get some work) to diff it first

lol well ill stick to froyo i doubt dell have changed anything for eclair in kernel (i can swap and change between eclair and donut happily in my own android port using same kernel

[fards]

Stephen Hyde, on Sep 9 2010, 10:55, said:

lol well ill stick to froyo i doubt dell have changed anything for eclair in kernel (i can swap and change between eclair and donut happily in my own android port using same kernel

yeah I think so as well, but if I can check what they've changed, we have a better way of building froyo

[timbomfg]

I'm no programmer, but i'm pretty handy to a point. Anyone got a decent generic guide on building a copy of android? I want to try to compile a vanilla copy of 1.6 for the streak sans DellUI.

Following Dell's own guide seems simple enough, but its the precursor stuff i'm unsure of.