Sony's relationship with "pure" Android is an interesting one. As a company they generally make it easy to root or otherwise modify their phones or tablets, with a few notable qualifiers. The AOSP for Xperia project, which provides the basic tools for building standard Android ROMs on popular devices, is also one way that Sony stays relevant for those who buy phones with the intent to add aftermarket software. Today it gets two new flagship options, the older Xperia Z1 and Z2. Read More
Google has been wrestling with a series of strange and not too uncommon bugs with a part of the camera subsystem on the Nexus 5 called mm-qcamera-daemon. Without this component, the camera on this device won't function, but sometimes it goes wonky and drains the battery. A Googler has just marked this issue as "future release" in the AOSP issue tracker, meaning it should be fixed when Android L rolls out. Read More
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? 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. 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. 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. 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. 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.