Basically all of Blu's phones as of the last year or so have been released with Android 4.2.2, leaving users waiting for any sign of an update to put them past Jelly Bean. We've known that the company planned on pushing KitKat to a number of devices towards the end of June, and it has now released the initial devices that will be the first to get 4.4, along with a statement on Facebook.
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.
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.