The one and only Jean-Baptiste Queru (JBQ) has been much beloved by the Android community for his work on the Android Open Source Project at Google, where he was the technical lead. Following a dispute over missing open source drivers a few weeks ago, JBQ departed from Mountain View. Now he's announced his new position... at Yahoo.
It was just the other day when it came out that complications with Qualcomm licensing was keeping Google from posting the binaries and full factory image for the new Nexus 7 tablet. The issue was so irksome that Jean-Baptiste Quéru (JBQ), Google's Android open source manager, decided to leave that post. Well, that must have lit a fire under someone, because Google just posted the image and drivers for the Razor hardware.
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.
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.
You know the Android codenames, right? Starting with Android 1.5, they're alphabetical snacks - Cupcake, Donut, Éclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich, and Jelly Bean. But what about before 1.5? What were those called? And why did they start with C? We've got real answers from real Googlers.
Wikipedia's Android Version History is a pretty awesome article, but, as of a few days ago, it was erroneously calling 1.0 and 1.1 "Astro" and "Bender." We had never heard of this, and there wasn't a good source attached to it, so we took to G+ to set the record straight.
In a gesture of good faith, Sony, on its developer blog, has announced the company is releasing the software binaries for the Xperia S. It has done so explicitly in support of Android developer JBQ's "experimental" support for the device in AOSP (found here). If you're unfamiliar with the project, we covered it earlier this month when it was announced.
- Download: Xperia S software binaries
The software binaries Sony released consist mainly of drivers for the hardware on the Xperia S's chipset.
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:
Earlier today, the Jelly Bean source code rolled into AOSP (Android Open Source Project). This is a big deal - one we've been waiting for since the great Google I/O unveiling. What does it mean exactly?
It means that ROMs that are built from AOSP, like CyanogenMod, can now start integrating the Jelly Bean code and release the first true JB nightlies. Not broken ports from the Galaxy Nexus builds - real ROMs.
If you follow AOSP code drops long enough, you're eventually going to hear about JBQ (as well as a ton more acronyms). Jean-Baptiste Queru, Technical Lead of the Android Open-Source Project took to Google+ today to talk about Android update rollouts, as well as to praise one of the manufacturers that he sees as leading the pack in aiding the AOSP: Sony.