A differenza di quanto dicevano i rumors questa mattina, sono già disponibili i sorgenti di Android 4.0 Ice Cream Sandwich.
Tali sorgenti saranno utili a chiunque, come Cyanogen, che si cimenta nello sviluppo di firmware per i vari dispositivi e questo vuol dire che presto Android Ice Cream Sandwich arriverà sui vari Smartphone e Tablet sia in modo ufficiale che non ufficiale.
Di seguito trovate l’annuncio ufficiale e qualche piccola istruzione per scaricare tutto il pacchetto sorgente, ovviamente per chi e capisce :-)
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code for Android version 4.0 (Ice Cream Sandwich) is now available.
Here’s how to get it:
Follow the instructions at http://source.android.com/source/downloading.html
Check out the ‘ics-release’ branch:
repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That’s it! However since this is a large push, please be aware that it will take some time to complete. If you sync before it’s done, you’ll get an incomplete copy that you won’t be able to use, so please wait for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which is the specific version that will ship on the Galaxy Nexus, the first Android 4.0 device. In the source tree, you will find a device build target named “full_maguro” that you can use to build a system image for Galaxy Nexus. Build configurations for other devices will come later.
Unfortunately we still don’t have our Gerrit code review servers back online. That remains our top priority though, and we hope to have them back soon.
This release includes the full history of the Android source code tree, which naturally includes all the source code for the Honeycomb releases. However, since Honeycomb was a little incomplete, we want everyone to focus on Ice Cream Sandwich. So, we haven’t created any tags that correspond to the Honeycomb releases (even though the changes are present in the history.)
JBQ, on behalf of the AOSP team.
[Grazie a Simone della segnalazione]