The Dell Venue 8 7840 was released in early 2015, and it was a pretty good tablet. It's certainly the best Android slate Dell has ever made. It was slightly annoying to have the device launch with KitKat back then, but it still doesn't have Lollipop all these months later. That hasn't stopped Dell from updating its product page to claim the Venue 8 does in fact run Lollipop. Here's everything we've learned from Dell about this mess.
I'm sure everybody can agree, it makes almost no sense that the Nexus 9 is only now receiving a tiny maintenance update to 5.0.2 a couple of months after 5.1 came out. Nevertheless, that's how events are playing out, so we should at least know what's so special about this update. We've generated a changelog from AOSP, and honestly, there's not much to see.
Be aware, the Nexus 9 update goes from 5.0.1_r1 to 5.0.2_r3.
Google has updated the Nexus developer page with links to factory images for the latest Nexus 9 Lollipop build. Don't get too excited, though. This is the 5.0.2 build that started going out as an OTA earlier today. Google, you monster.
You know how the Nexus 9 is still waiting to get the Android 5.1 update? Well, there's an OTA update rolling out right now that isn't Android 5.1. When next you see that glorious system update icon, it'll probably be for a build of Android 5.0.2, which is rolling out right now. Oh, Google.
Android Wear 5.1 is surprisingly full of new features, and the lock screen may be one of the more exciting ones. Until now, there was no OS-level way to secure your Wear device from unauthorized use. With Wear 5.1, a pattern lockscreen has been introduced, and it should pop up any time Wear detects your device is no longer on your wrist. For a quick walkthrough of the feature, see the video below.
Setting up a lock screen is dead simple, just go into settings, find the lock screen option, and enter the 4-point-or-greater pattern you want to use (twice). At this point, your watch is set up to lock its screen whenever it no longer detects it's on your wrist.
Google's monthly platform distribution numbers are in, and there's finally a respectable showing for Lollipop. Meanwhile, the remainder of the versions ticked downward as the Android device ecosystem marches slowly into the future.
App discovery on Android Wear isn't outstanding to start with, but one thing that always rubbed me the wrong way was just how blissfully unaware you could be that an app you had installed on your Android smartphone also installed a Wear mini-app on your watch. With Android Wear 5.1, you'll live in ignorance no longer: every time a new Wear app is installed on your watch, it'll serve up a notification letting you know, just like the one above (this is also true for watch faces).
Is it a small feature? Absolutely. But it's one of those things you're happy to have when you do, and might not even know you miss when you don't.
One thing that I've always found annoying about notification management on Android Wear is that dismissal is generally handled in bulk. If an app is serving you multiple notifications, like Inbox, for example, you can't go through each of those messages and dismiss them individually. Nope, you can either dismiss all of them or none of them (unless you use a specific action that subsequently dismisses the card, eg, "Done").
Android Wear 5.1 appears to have addressed this in some apps, with the Inbox, Hangouts, and Calendar apps on Wear now allowing you to dismiss single cards from a larger stack, instead of having to swipe them away en masse.
Wi-Fi connectivity has been one of the real headline features for Android Wear 5.1, and rightly so: this new functionality will allow your Android Wear device to stay connected to the internet even when your phone is nowhere to be found (so long as you have a saved Wi-Fi network nearby). Here's what we've learned about the feature in using it so far, including a video primer of how to get it set up.
First things first: this feature will not allow you to use a Wear device without ever connecting it to a smartphone. An Android smartphone is still required, because things like entering the Wi-Fi network password take place on the paired phone rather than the watch itself.