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.
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.
Releasing the L preview was an important leap forward for Android as an ecosystem, but, outside of a single almost meaningless update, we're probably not going to see any new builds up until the final L release. I can sort of see why the Android team doesn't want to put out builds with incremental fixes, saving all the improvements for a grand finale unveiling, so in the meantime, any glimpse at their progress is very interesting to us as well as developers working on porting their apps to adhere to the new Material Design guidelines.
Today, we have a photo showing a Nexus 5 running build LRW66E, posted to the Chrome bug tracker a few days ago and subsequently set to private.
With most versions of Android, we're not used to seeing a changelog until a few hours after the AOSP code has been fully uploaded and somebody has had time to generate a comprehensive list. Imagine our surprise when such a list for KitKat 4.4.3 was discovered simply lying around on Google's servers. The file, named KK-MR2_changelist.txt, is located amidst Android's platform documentation. This is something of a first, since we'll actually learn about what's to come before the code is even available.
The changelog was first added 3 weeks ago, but it may not have been uploaded to AOSP until more recently.
Over the past few days, ASUS has begun rolling out a treat to MeMO Pad Smart 10 owners, distributing Android 4.2.1 in an update to build number V10.6.1.15. The update, which rings in at about 500MB, brings the MeMO to 4.2.1 from 4.1, delivering on ASUS' "Q2 2013" promises noted in our review.
Of course, the headlining feature with this update is 4.2's multi-user support, which we already saw on an ASUS slate back when the manufacturer brought 4.2 to the TF300T in the US, beating other OEMs to the update punch. Otherwise, users can likely expect the same performance and stability enhancements found in the TF300T's 4.2.1 build.
Earlier today, Google started pushing some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.2_r1.1 and android-4.2.2_r1.2. The build number corresponding to the 4.2.2_r1.2 release is JDQ39E.
The dates you see here are commit dates, not dates the commits were made public (which is today, April 17th 2013)
After weeding out the changes from the commit logs, it looks like all of them are, as expected, very minor. We've seen these _r1.X releases before, and the last one didn't fix much at all.
Here are the aforementioned changes between 4.2.2's tags 4.2.2_r1 (JDQ39) and 4.2.2_r1.2 (JDQ39E).
The Xperia E, Sony's low-end Jelly Bean-powered smartphone which was announced back in December may have another trick up its sleeve yet. The manufacturer is offering owners of the device the chance to test out Mozilla's fledgling Firefox OS on the device via a downloadable ROM. Meant for "advanced developers," the ROM comes with a few warnings from Sony, chiefly that you should know what you're doing before you get started.
The ROM is thus far labeled "experimental," and comes with its own set of limitations: for starters, there's no radio connectivity. This means no cellular, Wi-Fi, or Bluetooth capability. Additionally, the SD card "might be unstable" and touch screen sensitivity is not fully calibrated.
Yesterday, Google pushed some new open source code to AOSP (Android Open Source Project) marked with 2 new tags: android-4.2.1_r1.1 and android-4.2.1_r1.2. The build number corresponding to the 4.2.1_r1.2 release is - you guessed it - JOP40G (with mentions of JOP40F and JOP40E along the way too) - the same one we thought would be 4.2.2.
The dates you see here are commit dates, not dates the commits were made public (which was Feb 1st 2013)