Johan de Koning
Inside the Android repository there is a new branch available with the name cupcake-release. On the Android Platform Forum (http://groups.google.com/group/android-platform/browse_thread/thread/4853d33c28abb5f5) this is what being said about this new branch
cupcake-release is the branch that is used to build devices, whereas
cupcake is the branch that is used to build the SDK (we separate them
for a variety of reasons). Until 1.5r2 (mid-May) they were identical
for all practical purposes, so the distinction (which had existed on
our internal servers for a long time) didn’t get reflected on the
outside, but since mid-May they’ve been drifting a bit and we decided
to reflect the differences on the outside.
The current state of cupcake-release is a loose match for the CRC01
release that is being deployed to some consumer devices.
Admittedly, we still need to do a better job at matching the various
forms of the version numbers, especially for the device builds.
I updated the blogposts about building Android 1.5. It will now use the cupcake-release branch. So read the blogposts (again) if you want to build your own Android version based on this source.
Hi,
Does this branch include the correct WiFi & LED drivers ?
Or do I need to extract those files from the real device as described in your blogposts ?
Also - do you think there's a chance this will work on the HTC Magic device (g2) ?
And - does it include the various apps (email, calendar, ...) ?
Thanks !
Does the cupcake-release work with the new kernel 2.6.29
Did not tried out yet and I think it will not work. There are problems with the camera and I think this has something to do with the proprietary files.
I placed a question on the Android Platform Disccusion Group about the Camera issue http://groups.google.com/group/android-platform/browse_thread/thread/224666a8f79897f0
I still compiled the Wifi driver by my own (as described inside the blogpost). I will check out later if the correct driver is part of the source tree
Te led drivers was never part of the source tree and should still be extracted from the device
BTW I don't have a HTC Magic so i cannot check if this is working. I think there is a difference in hardware between those devices meaning that other drivers are needed. Can you confirm that the HTC Magic can be flashed just like a HTC Dream?
JBQ say in the platform group http://groups.google.com/group/android-platform/browse_thread/thread/2d496adb75997d2
build for dream is straightforward, no local_manifest necessary, no patching, anybody checking
I'm syncing...
This means that cupcake-release also downloads the HTC Dream project. If that is the case they had better call the project cupcake-dream to make this clear
Looks like building is not that straight forward as promised.
First there is the discussion with the branch name. It though that cupcake-release was for devices and cupcake for general development. But now cupcake automatically gets the vendor/htc/dream-open project.
Inside the dream-open project the extract-files.sh and AndroidBoard.mk are not updated as patch 10501. This way you will miss some proprietary files.
The SdkSetup is still needed (when not using the Google Apps) to make it possible to answer/make calls.
The Google Apps are still not part of the tree. So if you want those you still need to add those by hand.
I think that my build procedure is sill relevant. I will check it this weekend to see where things have been changed.
I am a little bit worried about the Open Sourceness of Android on a device. Because there are rumours that the G1 is not capable of getting another update (after 2.0). With the Dev Phone this can be different because space can be allocated differently (don't know the details yet). This will probally result in a device which will not get updates from HTC for the proprietary files and the radio stack (I am not meaning the 2.0 version but after that). And then we are stuck when we want to compile a newer version and the libraries are not supplied by HTC. And also now we don't know for sure if for example the Camera issue with 2.6.29 is a kernel problem or for example inside the libqcamera.so module?
When will there be a device for which those parts will also be open sourced? Or can we develop our own kernel modules based on hardware or (probally not legal) decompiling stuff? BTW Does anybody knows what is inside the radio image?
Just another update on my last command to make my opinion more clear
With the openess of Android I don't mean the Android OS by it self. But I mean the openess of the Android Dev Phone. This is official the only phone which can be used to try out own builds but it depends on closed parts at the core level which can stop/interrupt development.
I don't think the 2.6.29 Kernel has an issue with the Camera, you just have to revert to the old I2C drivers. I have the 2.6.29 Kernel working fine with the Camera on my G1 using AOSP and HTC sourced builds. Let me know if you have any questions.
What do you mean with the old I2C drivers. Those are part of the 2.6.27 kernel?
I asked myself for hundred times now what AOSP stands for?? And did you build your build alone or is it a custom build of another developer?? Where do we get this driver? Also JBQ at Google Platform group said it would be a problem with missing prorietary files.