T-Mobile began rolling out security-centric updates to Nexus devices yesterday. As we already know, there aren't any big changes due out in this release, but Google has pushed the latest code up to the Android Open Source Project (AOSP) for the world to see. As usual, we've put together a changelog for easy reading.
Updates for T-Mobile devices are built from a dedicated branch in AOSP with custom code to support the Wi-Fi calling feature. As it turns out, the list of changes for this update to LMY48M closely resembles the r6 to r9 update from last month, otherwise known as the update that (mostly) fixed Stagefright. Read More
The Android public issue tracker is a place for users to report possible bugs to Google's engineers, but just because something is reported doesn't mean it'll get fixed right away. Many users have been experiencing a battery draining bug in Lollipop caused by the device's radio remaining active for too long, but only now is Google doing something about it. The fix is expected to roll out in Android 6.0. Read More
Sony is ahead of most other OEMs when it comes to its support of open source. It contributes significantly to AOSP and even releases binaries for many of its devices so developers can build AOSP ROMs for them. Today, Sony is announcing support for the first three 64-bit devices in the Open Device project. Read More
Earlier today, Google released updated factory images for all of its supported Nexus devices to patch up some reasonably serious vulnerabilities in a core Android library called Stagefright. While we await the stream of OTAs that are sure to follow, there's a fresh code drop to the Android Open Source Project containing security-related patches. Don't expect to see any new features or user-facing changes, this one is all about closing loopholes. Nevertheless, there are some interesting things to peek at.
A quick look at the changelog shows the highest concentration of fixes were made to frameworks/av (audio/visual), which is used extensively in the Stagefright library. Read More
It seems like the only thing anybody can talk about is Android M, but we should remember that we've got about 4 more months with Lollipop v5.1.1 as the current version until Mango Mojito (probably not) is officially released in October. This is no more apparent than when an update appears on AOSP and brings with it thousands of changes. In fact, this update is large enough it probably deserved more than a barely noticeable revision bump.
The code drop for LYZ28E comes a bit later than expected, since the build number was first seen in a Nexus 6 update that began rolling out a month ago. Read More
The Android M Developer Preview was released just yesterday and we're all very closely examining the changes. While there's still quite a bit to dig through, it looks like Google is getting some of the source code up right away. Before anybody gets too excited, it's likely that this code dump occurred to ensure GPL compliance. However, there are quite a few projects in the changelog that wouldn't normally require updates due to licensing, so there may be quite a bit more going live on this release.
The entire changelog totals about 29,000 commits and weighs in at about 4.7 MB. It's not entirely clear where the official starting point would be, but we generated the changelog from 5.1.1_r4, which is currently the latest release available. Read More
Google will be unveiling the successor to Lollipop at Google I/O in just a few days, but we won't get a real name. It will likely just be called Android M until it's released, but Google has an internal code name just as it did for L and K. It's called Macadamia Nut Cookie (MNC), a name which is already being referenced in AOSP. Read More
Changelogs come in all shapes and sizes. Well, maybe there is just the one shape, but many different sizes. A new tag for 5.1.1_r3 turned up a few hours ago in AOSP and we've generated a list of changes the change for those who would like to know what's going on. As it turns out, this update sets a record for the smallest changelog ever, at just one lonely commit. On top of that, it's specifically for the Nexus 6 (Shamu).
The lone commit in this release appears to be a bug fix for devices with encryption enabled. The adspd process has been set up to run with the encryption lock screen instead of after. Read More