latest
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.
A little bit of connecting the dots has revealed that Qualcomm is the reason behind the new Nexus 7's lack of factory image / driver binary support. This has long-time AOSP maintainer Jean-Baptiste Quéru pretty upset. Upset enough that he is "quitting AOSP."
Update: Looks like we were right.
[Achievement Unlocked] Google: Nexus 4 And Nexus 7 Are The First Ever AOSP Devices That Have 100% Of The Proprietary Binaries Available
Google: Nexus 4 And Nexus 7 Are The First Ever AOSP Devices That Have 100% Of The Proprietary Binaries Available
As an addendum to the announcement of Google completing AOSP rollout for Android 4.2.2, I wanted to highlight a big milestone for the Nexus program - something that has never been the case before today.
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.
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.
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.
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.
Sony Xperia S Added To Android Open Source Project As First Experimental Device
The head of Google's Android Open Source Project (AOSP), Jean-Baptiste Queru, made an interesting proposal recently. He added a new device to the AOSP
The head of Google's Android Open Source Project (AOSP), Jean-Baptiste Queru, made an interesting proposal recently. He added a new device to the AOSP repository, but this is no Nexus variant. Queru created an empty git project for the Sony Xperia S, but he needs the community to get behind the initiative. This will be the first device not designed under Google's supervision to be supported under AOSP, and that could be a big deal.
Sprint Had This To Say About AOSP Support For Galaxy Nexus
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
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.
Verizon Galaxy Nexus Is Closer Than Ever To Full AOSP Support - But It's Not There Yet
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
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?
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.
Thanks again to the venerable JBQ of Google, the unmodified factory image of Android 4.0.4 for the Nexus S 4G (sojus, Android 4.0.4 IMM76D) is now available here. As JBQ states on Google+, this image is for those among you who have flashed to custom versions of AOSP and want to get back to factory state. No, by the way, there's still no word on an OTA update yet.
Source code for Android 4.0.4 (AOSP tag android-4.0.4_r1.1), the latest incremental update with "a few hundred changes over 4.0.3," is being pushed to AOSP (Android Open Source Project) as we speak by JBQ, one of AOSP's main sourcerers (yes, I just made that word up).