Use two-factor authentication? If not, you should, because it's more secure than if you don't use it. If you already use it, then you probably remember a time when the Android setup process was obnoxious because you not only had to put in your password twice, but also had to deal with an annoying web prompt to enter the passcode. It's a hard knock life.
Are you super-anxious to get your hands on Android L, now that it's been officially revealed as version 5.0 with the Lollipop name? Well tough noogies - it looks like we'll have to wait for the releases of the new Nexus 6 phone and Nexus 9 tablet before the older Nexus and Google Play Edition devices get their updates. But if you have a Nexus 5 or a Wi-Fi Nexus 7, you've already got the Android L Developer Preview builds as an option.
Rumor has it tomorrow is a big day for the Android world. Of course officially, Google hasn't made a peep about potential new devices, their announcement date, or Android's upcoming L incarnation, but we've heard plenty about the Nexus 6, Nexus 9 (and its accessories), and L itself.
Sundar Pichai, however, has shared a video clearly meant to tease the Android community (already stirred to a fever pitch) at least one more time, following the story of the L casting call, where various desserts audition for the role of L's official mascot.
When a new version of Android is announced, one of the first questions on everyone's mind is "when will my device be getting updated?" Fortunately, Motorola has moved towards complete transparency and providing timely updates over the past couple of years, and with the announcement of Lollipop it is giving details on what Moto owners can expect in the coming weeks.
Once Android 5.0 L is officially released, we intend to bring this latest upgrade to many of our other Motorola devices, as well.
We've been speculating and making wild guesses for months about what the new version of Android would be called, but now we know. It's Android 5.0 Lollipop. There was a time when many thought 5.0 was going to be Key Lime Pie, but that certainly didn't happen. How far we've come.
It feels like Android L and the Nexus 6 are set to drop at any moment—you can almost sense the #NexusWarriors gathering at the fringes of the internet, ready to storm all the comment sections everywhere and tell you how great the Nexus 6 is. And maybe it will be, but for now all we have is a taste of what's to come with a leaked copy of Google's new Android ads with the slogan "Be Together, Not The Same." It includes a cameo by what appears to be the Nexus 6 running Android L.
Back in June, Google announced Android was destined to gain 64-bit support in the coming L release. A few weeks later, Revision 10 of the Native Development Kit (NDK) was posted with support for the three 64-bit architectures that would be able to run the new version of Android: arm64-v8a, x86_64, and mips64. As we close in on the official release of Android L, Google has updated the NDK to revision 10b and added an emulator image developers can use to prepare their apps to run on devices built with Intel's 64-bit chips.
Google has been wrestling with a series of strange and not too uncommon bugs with a part of the camera subsystem on the Nexus 5 called mm-qcamera-daemon. Without this component, the camera on this device won't function, but sometimes it goes wonky and drains the battery. A Googler has just marked this issue as "future release" in the AOSP issue tracker, meaning it should be fixed when Android L rolls out.
Android L is probably just a few weeks away, but Google's partners already have the code to begin designing updates. That's why SamMobile was able to get a hold of a nearly complete build of Android L on the Galaxy S5. It looks pretty much like you'd expect a Samsung ROM to look, but there's definitely some L influence.
Just a couple of days ago, we posted a quick look at what the next Nexus phone would look like (along with some spec confirmations), based on new information and materials we had seen. That image however, as stated before, was just a reproduction of what we'd seen (redrawn to protect our source and eliminate any possible identifiers). Today, though, we have what looks like a photo of the device.