08
May
image

While the Google Developers site received its massive redesign quite a while ago, its sibling AOSP one at source.android.com has remained an ugly duckling. Until about an hour ago.

The difference is huge - it's like it went from Cupcake days to Jelly Bean in the blink of an eye. It would be nice if you could update Android the same way, wouldn't it?

Here are some images of the old (visible at archive.org) and new sites side-by-side (can you guess which one is which?):

image image

image image

Source: AOSP

17
Apr
image

Earlier today, Google started pushing some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.2_r1.1 and android-4.2.2_r1.2. The build number corresponding to the 4.2.2_r1.2 release is JDQ39E.

image

The dates you see here are commit dates, not dates the commits were made public (which is today, April 17th 2013)

What's New?

After weeding out the changes from the commit logs, it looks like all of them are, as expected, very minor.

02
Feb
image

Earlier this week, we got wind of a new OTA build JOP40G possibly hitting the Nexus 4 soon. I thought this update would finally be the elusive Android 4.2.2 that we've been hearing about, but it looks like that's not the case.

Yesterday, Google pushed some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.1_r1.1 and android-4.2.1_r1.2. The build number corresponding to the 4.2.1_r1.2 release is - you guessed it - JOP40G (with mentions of JOP40F and JOP40E along the way too) - the same one we thought would be 4.2.2.

27
Nov
lights2
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.

13
Nov
http://cdn.androidpolice.com/wp-content/uploads/2012/07/AOSP_Bugless_Beast_thumb.png
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.

22
Oct
nexus

The Galaxy Nexus variant on Sprint might actually have a chance of being officially supported by Google in AOSP after all, which would be a big step in the right direction for carrier-branded Nexus devices.

If you remember, neither Verizon's nor Sprint's Galaxy Nexus was supported by the Android Open Source Project at launch, with the Verizon's version joining the program over half a year after its release. Even though the Nexus S 4G is fully supported, Sprint's GNex variant remained absent from the Nexus Binaries page and was therefore completely unsupported by the Android team.

09
Oct
android-logo-font
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.

10
Jul
image
Last Updated: October 22nd, 2012

image

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.

09
Jul
vzw-galaxy-nexus

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.

28
Mar
image

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.