Galaxy Nexus Seeing First Batch of Android 4.2 Custom ROM’s From AOSP

As a Galaxy Nexus owner, you expect nothing but the latest and greatest software to be running on your device. Unfortunately, Verizon is currently not the fastest carrier to deliver such things. But don’t worry, this is Android! Once Android 4.2 hit AOSP, along with the Verizon binaries, the developers got straight to work.

As of right now, we have a few custom ROM’s that feature pure Android 4.2 AOSP code to share with you. Below, we will provide links to their respective forum pages and will continue to share more ROM’s as they emerge. If you have a favorite custom ROM that you would like us to personally flash and share with the community, go ahead and let us know down below in the comments section.  (more…)

Android 4.2 Headed to AOSP Right Now!

With the Nexus 4 and Nexus 10 launching on Google Play, and running Android 4.2, it only makes sense that this new version of Jelly Bean would makes its way to the Android Open Source Project (AOSP). Sure enough, that is happening now.

What does this mean for all of you? Well, it means that your favorite custom ROM developer has some work to do. Once that work is done, it then means that you will have a brand spankin’ new ROM to dive into that includes Photosphere, the quick settings pull-down, a better keyboard, and more.

Once we start hearing from the top devs with ROMs, we’ll start gathering them up for a mega-post.

Via:  Google Groups

Understanding the Difference Between AOSP and the Open Handset Alliance [Opinion]

Over the past few years there has been grumbling among some that Google needs to stop calling Android open source. The argument is a simple one: Google can call Android open source as long as it doesn’t place any requirements on its OEMs to use Android. This article will unpack some of the misconceptions about what it means to say that Android is open source and deal with the two major instances where Google has been accused of violating its own principles concerning Android.  (more…)

Google Experimenting with Bringing AOSP to the Sony Xperia S

For years there has been a battle between AOSP fans and manufacturers to hack vanilla Android (or something close to it like CyanogenMod) onto devices instead of the manufacturer’s version of Android. The difficulty with this battle is that it takes a tremendous amount of work to get another ROM working on a device. A developer cannot simply take AOSP Android and load it onto a device because stock Android is actually designed to run on a specific device (currently the Nexus S, Galaxy Nexus, or Nexus 7).

Jean-Baptiste Queru, the technical head of the Android Open Source Project, wants to experiment with how AOSP works. Starting with the Xperia S, Queru has invited the community to experiment with porting AOSP to the device. “In theory, AOSP is designed such that it should be possible to plug in the files related to additional hardware targets,” said Queru in a Google Groups post. “In practice, that has never happened.”  (more…)

Yessir, the LTE Galaxy Nexus is Technically “Supported” in AOSP by Google Again

If you follow us on Twitter, then you probably saw us break this news yesterday afternoon. For those who don’t, feel free to be proud of your LTE Galaxy Nexus again because it technically falls under the “supported” tag by Google in AOSP.

As you may recall from back in February, we threw a bit of a fit when we found out that CDMA devices were no longer officially supported. Most of us had no idea what this meant until we raised that stink. Eventually, an Android engineer clarified that it really just meant that they were not allowed to make some CDMA binaries available, hence the reasoning for removing official AOSP support.

When Android 4.1 hit AOSP yesterday though, one of our readers noticed that the CDMA/LTE and orientation sensor binaries were now showing as available for the LTE G-Nex, essentially making it official again. Master of AOSP, Jean-Baptise Queru, said that it is supported in an “experimental” fashion.

So, there you have it. Throw a mini-party. This doesn’t mean that you will see updates any faster. It also doesn’t mean the ROM game will change all that much. After all, it wasn’t officially supported for months and things hummed along fine.

Cheers Nick!

First Batch of 4.0.4 ROMs Arrive for the LTE Galaxy Nexus

With the release of Android 4.0.4 to the Open Source Project, custom ROM developers have begun the scramble in working all of the newest features into their current work. One of the more well-known developers, Roman and his team from the Android Open Kang Project, have released Build 29 for the Galaxy Nexus and there are also builds floating around from other mentionable developers, inlcuding a stock 4.0.4 build from Birdman.

AOKP Build 29 | Stock 4.0.4

For downloads and flashing instructions, just click the thread link you wish to read up on and go from there. But do note, that when flashing a newer version of Android, you must wipe data/cache in order to have a clean install. We don’t want anyone bootlooping when trying to perform these tasks.

Cheers K!

Android 4.0.4 Build IMM76D Hitting AOSP Right Now


The Android Dev team just announced that Android 4.0.4 Build IMM76D is being pushed into AOSP this very minute. This would be the same (or very similar) build to what was released to the Motorola XOOM WiFi this morning. This doesn’t necessarily mean that the Galaxy Nexus will see it any minute, but it is certainly a hell of a sign. If anything, it means that a new round of your favorite ROMs will be built within a few hours.

We should point out that this new build is already becoming available for the T-Mobile Nexus S.

Update:  I could not help but point out a couple of specific notes that Jean-Baptiste Queru mentioned in his post:

The matching proprietary files will be available at by the end of day (PDT). You should note that files related to CDMA devices (Nexus S 4G, CDMA/LTE Xoom, CDMA/LTE Galaxy Nexus) have not been tested in the context of AOSP. Of course, consumer support for those devices continues unchanged.

I do not know the schedule for deployment to consumer devices, especially in situations that involve additional per-operator customizations done by the device manufacturers and/or in situations that require operator approval prior to deployment.

Grrrrr” is all I have to say to that.


Via:  Android Building