Battery life on Android has been a bit of a sore spot for many users, mostly because it's simply not good enough. Most devices can make it a day on moderate use, and a few can even do so comfortably, very few phones can hit two days without some time on the charger. The Android "L" release is making several improvements to power efficiency via Project Volta, but there are also ways to improve 3rd-party apps, and that's where the new Job Scheduler comes in.
If it's not already completely obvious, the L Developer Preview is shaping up to be an absolutely massive sea change for Android. While we've been treated to an entirely new design language called Material, a redesigned Recents screen, huge performance improvements, and over 5000 other new APIs and features for developers, it's easy to overlook plenty of exciting improvements that aren't quite as flashy. One such change was briefly mentioned by Dan Sandler during the "What's new in Android" session: Multi-Networking, the capability to maintain multiple network connections simultaneously.
Last year, at Google I/O 2013, some major new features and improvements were announced for Google Cloud Messaging (GCM) -the replacement for Cloud to Device Messaging (C2DM). A couple of the new bits were even featured during the keynote, particularly notification syncing, which the audience loved. The one thing most people don't know is that most of the coolest things announced that year were marked as beta and locked behind an application process.
If we're being honest, it's hard to deny that one of Android's most obnoxious flaws comes in the category of audio performance. Playing some music is generally fine, but the issues start to become obvious after introducing very high quality audio or trying to achieve precise timing or real-time processing. With the L Developer Preview, it appears that Google is driving to improve upon these weaknesses and give audio performance the shot of adrenaline it needs.
Android Studio was first introduced to the world a little over a year ago at Google I/O 2013. At the time, it was coined a "Developer Preview" to indicate that it wasn't ready for major development projects, but people were welcome to experiment with it. In the following months, Android Studio has progressively improved, swatting many of the bugs and adding truly valuable features for developers and interface designers. After a long, and sometimes frustrating road, the upstart IDE is finally trading in its 'Developer Preview' moniker in favor of a shiny new 'Beta' tag.
The Android team has been hard at work replacing old code that hasn't scaled well with newer and more powerful hardware. We've long known that the camera API was destined to see a massive update, but we were missing details like a release date or exactly what was coming. Thanks to the L release, we can finally see what has been in the works for all these many months.
One of the most important aspects of the new Camera 2 API is a dramatic increase in performance over the previous interface.
Android 4.4 contained a number of interesting and very powerful features for developers, many of which went unused or misunderstood for quite a long time. Since it was introduced in KitKat, The Storage Access Framework (SAF) may be one of the best examples of an API that has been underutilized, despite offering a great method to provide cleaner and more informative interfaces. I even theorized that it may ultimately take the place of file system access.
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 changes have already been posted to AOSP and Al Sutton quickly followed up with a list of the changes that make up the latest update. 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.
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
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.
Jeff Bezos took to the stage earlier today to announce Amazon's first entrant into the highly competitive smartphone industry, the Fire Phone. Not only was the presentation loaded with some of the shiny new features of the handset and Fire OS, all meant for the press to disseminate to potential buyers, but there were also a few unusually blunt efforts to attract developers. In the midst of demonstrating Firefly and Dynamic Perspective, portions of the presentation were focused on explaining that developers would be able to extend these platform features in their own apps.