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.
CyanogenMod (CM) has long been the modding community's custom ROM of choice, and for good reason: it takes the goodness that is basic Android (AOSP) and adds a hearty dose of all-around improvement. The list of devices supported by CM is quite a long and impressive one (truth be told, they do a better job of supporting devices than the manufacturers do), and last night, cutting-edge nightly CM9 releases dropped for the Sony Xperia Arc (Anzu) and Xperia Neo (Hallon).
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).
This is excellent news for any ROM developers compiling their ROMs from AOSP (such as CyanogenMod) - chances are 4.0.4-based ROMs will start appearing very soon, maybe even tonight.
CyanogenMod has been growing lately. The AOSP-based custom ROM reached one million unique installs last month, and dozens of devices are currently supported, including a wide array of LG devices. It's time to welcome a new member of that family: the T-Mobile LG myTouch.
Honeycomb sources are being worked on.
Have you ever wondered what the AOSP source tree would look like if someone stitched together a video of every commit, update, and release? Ponder no more, friends, because YouTube user xcco3x has made that a reality. A visually amazing 21 minute reality, to be exact.
A little background info, per the description on YouTube:
Wow, this happened sooner than we expected - but Google just announced only minutes ago that the source code for Android 4.0.1 Ice Cream Sandwich is on its way to Google's AOSP tree right now. We'll update as we learn more. Here's the original post:
As we know, the source code for Android 4.0 "Ice Cream Sandwich" is going to be published fairly soon, which means developers of all trades will be able to download, modify, and compile it into ROMs. A few great examples of this are handset manufacturers (SE, Motorola, HTC, etc) working on incorporating ICS into new and existing devices as well as CyanogenMod developers merging the source with all the awesome modifications they've added into CM so far.
Since I'm seeing questions inquiring about Android 4.0's source code drop every 5 minutes here and there, I thought it would be a good idea to point out this blurb in a recent post by an Android engineer Dan Morrill, aka morrildl:
I'm curious to see what percentage of our readers who run custom ROMs are using AOSP (Android Open Source Project - something pretty close to vanilla Android, such as CyanogenMod), and what percentage are using something based on stock device ROMs. More specifically, I want to find out if people on certain manufacturers are more likely to go AOSP than others - in other words, is Blur/NinjaBlur pushing more people to AOSP than TouchWiz, or is there no difference?