Here comes Android 4.1 (Jelly Bean) to AOSP. JBQ announced within the hour that today is the day.

Go build those ROMs, boys.

Via:  Google Groups

With the release of Android 4.0.4 to the Open Source Project, custom ROM developers have begun the scramble in working all of the newest features into their current work. One of the more well-known developers, Roman and his team from the Android Open Kang Project, have released Build 29 for the Galaxy Nexus and there are also builds floating around from other mentionable developers, inlcuding a stock 4.0.4 build from Birdman.

AOKP Build 29 | Stock 4.0.4

For downloads and flashing instructions, just click the thread link you wish to read up on and go from there. But do note, that when flashing a newer version of Android, you must wipe data/cache in order to have a clean install. We don’t want anyone bootlooping when trying to perform these tasks.

Cheers K!

The Android Dev team just announced that Android 4.0.4 Build IMM76D is being pushed into AOSP this very minute. This would be the same (or very similar) build to what was released to the Motorola XOOM WiFi this morning. This doesn’t necessarily mean that the Galaxy Nexus will see it any minute, but it is certainly a hell of a sign. If anything, it means that a new round of your favorite ROMs will be built within a few hours.

We should point out that this new build is already becoming available for the T-Mobile Nexus S.

Update:  I could not help but point out a couple of specific notes that Jean-Baptiste Queru mentioned in his post:

The matching proprietary files will be available at https://code.google.com/android/nexus/drivers.html by the end of day (PDT). You should note that files related to CDMA devices (Nexus S 4G, CDMA/LTE Xoom, CDMA/LTE Galaxy Nexus) have not been tested in the context of AOSP. Of course, consumer support for those devices continues unchanged.

I do not know the schedule for deployment to consumer devices, especially in situations that involve additional per-operator customizations done by the device manufacturers and/or in situations that require operator approval prior to deployment.

“Grrrrr” is all I have to say to that.

Developing…

Via:  Android Building