As Google typically does upon the release of a new product, it has updated its support documentation with a series of common questions and issues users may find themselves facing when using Wear devices. Some are pretty handy. For example, if your phone is too far from your watch to maintain the pairing connection, you lose voice action controls. You can still set alarms, check your calendar, step count, heart rate, and a few other basic features, though.
We've already started receiving a ton of emails from concerned readers about L's app compatibility issues, broken functionality, and the like. Of course, we understand how frustrating this can be, but that's actually the point of the developer release.
One of the primary purposes behind Google releasing L for the Nexus 5 and 7 is so developers can get their apps updated before the stable version rolls out, as the switch from Dalvik to ART requires apps to be updated to add support for the latter.
The new Google keyboard in Android L brings the Material Design aesthetic to text input, but the APK pulled from L doesn't work quite right on other Android builds. It actually breaks the keyboard for most devices. No worries, though. An XDA user has tweaked it to work correctly on (probably) all Android 4.0 and higher devices. There is one method that requires root (it's actually a ZIP file) and one that might not work on all devices that's an APK.
Among Android L's many, many features is one that will set game developers' hearts aflutter – support for the recently announced OpenGL ES 3.1. This is the cross-platform rendering API used in many games, both mobile and desktop. Android L's support for v3.1 of the standard brings a ton of new capabilities.
You know the scenario: friends come over, want to use your Wi-Fi, and expect you to just hand over the password. I don't know about you guys, but I'm pretty weird about just giving my password to everyone who walks through the door, regardless of how well I know them. Most of time I opt to type my password in for them, but there is an easier way: store your Wi-Fi info on an NFC tag.
Compared to the popular third-party alternatives, Android's stock recovery has always been pretty...weak. Makes sense, because it's not really meant to do all the stuff that ROM flashers tend to use recovery for, but rather a failsafe of sorts in case something goes awry.
With L's Android release, the recovery is getting a little bit more useful with two new options: reboot to bootloader and power down. Nothing groundbreaking here, but still incredibly useful (especially "reboot to bootloader") for those times when stock recovery is the only option.
Earlier this year, both Evan 'Evleaks' Blass and The Information's Amir Efrati claimed that the upcoming Android Silver program would replace the Nexus line of developer phones. Blass went so far as to say, "There is no Nexus 6. Farewell, Nexus." Both of those reports would seem to be contradicted by our own exclusive reveal of the HTC Volantis, a new Nexus tablet. Now we've got even more claims that the Nexus hardware line isn't going anywhere soon, this time right from the proverbial horse's mouth.
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.