Last Updated: February 12th, 2013
Earlier today, both the Nexus 4 and the Nexus 10 started receiving small ~1MB OTAs to Android 4.2.1 with fixes to the missing month of December in the People app, among other things. The corresponding open source files are being pushed by Google to the Android Open Source Project (AOSP) as we speak, Android release engineer Jean-Baptiste Queru just announced in the Android Building group.
The build number is JOP40D and the tag is android-4.2.1_r1.
Last Updated: November 14th, 2012
The new Nexus devices just went live, and, as promised, Google has simultaneously started pushing the code for the latest iteration of our favorite mobile OS - Android 4.2 Jelly Bean - to the Android Open Source Project. Jean-Baptiste Queru, chief Android release engineer, announced the news via a post to the Android Building group.
Update 11:22am: Android 4.2 source just finished replicating to AOSP. "The platform source files for 4.2 have finished replicating, you can now sync." -JBQ
The build number is JOP40C, while the AOSP tags is android-4.2_r1.
Last Updated: October 10th, 2012
Google's chief release engineer Jean-Baptiste Queru just announced via the Android Building group that version 4.1.2 of Android is being released to the Android Open Source Project (AOSP) today.
The release follows Android 4.1.1, which was the final version of Jelly Bean, and is marked as minor. The build number, which we spotted in the logs yesterday, is JZO54K, while the AOSP tags are android-4.1.2_r1 and jb-mr0-release.
It's also a good time to bring up the fact that the LG Nexus prototype that we saw yesterday was also running 4.1.2.
Last Updated: October 22nd, 2012
OK, OK, that's actually Linus Torvalds expressing his feelings about NVIDIA, but there's no better way to articulate the continued frustration with the complete lack of Sprint Galaxy Nexus support in AOSP. Verizon is [almost] there. Sprint, however, is not. Try finding it (hint: its codename is toroplus) - specifically, the CDMA/LTE binaries.
If you still have doubts about the above notion so eloquently conveyed by Linus' gesture, Jean-Baptiste Queru's comment confirms:
As far as toroplus, the situation is unchanged: there are no plans to support it as a target device for custom AOSP builds.