Google has released the Android 4.2.2 “JDQ39″ binaries and will now begin pushing the code to the Android Open Source Project. These files, available for the full range of Nexus devices, will greatly benefit anyone looking to make their own ROM’s and or anyone hoping to see new ROM’s completed for any number of devices should be excited by this news.
If you dev, go grab it now.
Via: Google Developers
Mr. AOSP, Jean-Baptiste Queru, notified the Android Building group a few moments ago that Android 4.2.1 is being pushed to AOSP. After an update for 4.2.1 started rolling out to the Nexus 4 and Nexus 10 this morning, this move is exactly what you would expect to see. JQB called this a “minor update on top of 4.2.” We would agree, since the update to 4.2.1 is only a little over 1MB in size. The build number is JOP40D.
Full factory images will follow in the coming days.
Via: Android Building
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…)
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
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…)
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…)
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.
Here comes Android 4.1 (Jelly Bean) to AOSP. JBQ announced within the hour that today is the day.
Go build those ROMs, boys.
Via: Google Groups