Recently there's been a rumor that Sony is planning on releasing stock AOSP ROMs (clean, Nexus-style builds of Android) for some of its high-end phones and tablets. It's easy to understand why Sony in particular might attract that kind of attention: the company has better support for aftermarket development than most, promptly releasing binaries and source code on the company's own GitHub and even some developer-grade AOSP builds. But as for consumer-ready, finished and fully supported AOSP ROMs? Yeah, that's not happening.
At least not yet. While this blog post says that some of the members of Sony's development team love the community that's grown up around its open source Android releases, there are no current plans to support retail Sony Xperia hardware with full AOSP ROMs. Read More
If you've been dying to start poking around the Android Wear source code, now is the time! Google just posted 4.4W to AOSP. The active development branches are distributed throughout each project repository as kitkat-wear. This is the location where further patches and minor updates will appear. There is are also tags for android-4.4w_r1 (build KTU84Q), which represent the first official release of the platform.
There aren't any repositories for either Dory (LG G Watch) or Sprat (Samsung Gear Live), but we can't be certain if they will appear in AOSP or if the distribution of device specific source code will be left up to the manufacturers.
A couple of days ago, AOSP was graced with a series of freshly created "l-preview" branches and a massive push of brand new code. As we know now, quite a bit of that code push wasn't truly representative of the L developer preview. (Very sneaky, Google.) Most of the truly new updates belonged to GPL-licensed projects, which Google is obligated to release in a timely fashion. The remaining projects with "l-preview" branches were filled with a recent snapshot from the Master branch.
While we didn't get enough code to build our own versions of L, there is still an obscene amount to look at. Read More
It looks like Google is serious about getting the "L" preview out to developers in all of its forms, even as code. That's right, some of the source code is already live on AOSP!
It looks like all of the recent Nexus devices are covered - everything from the 2012 Nexus 7 up through to the Nexus 5. Of course, just because branches have been published for these devices, it is not absolute confirmation that this entire list of devices will receive an official L release. Nothing is certain until Google releases OTAs and/or factory images.
Note: there still aren't any binary packages or kernel sources for the Nexus devices, but these are probably coming fairly soon. Read More
At the Google I/O 2014 keynote, Google SVP Sundar Pichai announced that Android is now being used by more than a billion people every day. But in order to gain customers in the emerging market, Google has a new initiative: Android One. This program will be centered around affordable hardware with essential features, but it will also have an exciting software component.
In short, Android One is Nexus for emerging markets. The reference designs allow for incredibly cheap hardware with software that's semi-standardized. And that's important, because the updates will be coming straight from Google, in the same way that the company currently delivers new versions of Android for Nexus and Google Play Edition devices. Read More
An unexpected treat came zooming out of Google HQ today as Android 4.4.4 OTAs and factory images have started rolling out for Nexus devices. The updates have already been posted to AOSP and Al Sutton quickly followed up with a list of the changes. Since 4.4.3 is only 2 weeks old, and I/O is merely a week away, we had a feeling this was just a security update, and it looks like that's all it is.
Most of the significant changes are centered around fixing a recently discovered vulnerability in OpenSSL. The side effect is a few tweaks to the OpenSSL, WebView, and Chromium projects. Read More
It looks like Google is putting the last nail in Dalvik's coffin, and the new Android Runtime (ART) is about to take the throne. A pair of commits turned up last night in the master branch of the Android Open Source Project (AOSP) repository that spell certain doom for the Android runtime we've known Read More
and loved for all these years. The first of the two changes completely wipes the /libdvm (Dalvik Virtual Machine) folder from AOSP, and the second takes care of changing all of the relevant configuration files and startup scripts to call on the ART runtime. Yup, this is the end for Dalvik.
Most people familiar with the Nexus program know that each new Android update usually brings with it a new set of driver "blobs" for each supported phone and tablet in the product line. Even though these proprietary binaries are usually the latest versions when they come out, Google still occasionally receives updates to the drivers even when it's not a good time to issue an OTA. As we've just witnessed from the long lead time on the 4.4.3 release, it can take quite a while before an update is rolled out. However, it looks like Google is moving to combat this issue by adding a public channel for "Preview" versions of those binaries. Read More
Unless you blacked out all of the news from yesterday to avoid a deluge of stories about what has been happening in Cupertino, you probably caught wind that there's a brand new update to Android. Whether you're manually installing the latest OTA or going all out with the factory images, you might be interested to know what is actually different. Thanks to Al Sutton, we've got a brand new changelog compiled from the list of code commits submitted to the Android Open Source Project (AOSP). It covers just the bug fixes, tweaks, and adjustments from 4.4.2 (KOT49H) through to 4.4.3 (KTU84L).
Following the release of full factory images for all supported Nexus devices, Google has begun pushing Android 4.4.3 to the Android Open Source Project (AOSP). The push is ongoing and should be complete within an hour or two.
The build numbers are KTU84M for the Nexus 5 and KTU84L for the rest of the Nexus devices. The AOSP branch is kitkat-mr2-release, with the tag most likely named android-4.4.3_r1 expected to arrive shortly.
Here are several links pointing to the newly released code to get you started:
Update #1: The tag, indeed named android-4.4.3_r1 (KTU84L), has just popped up as well:
Update #2: Another tag android-4.4.3_r1.1 (KTU84M) just appeared:
Of course, you might be wondering what the source code availability means to you. Read More