Some bugs only cause problems for a select few users, but that was not the case when Google bungled the reminders voice command in a recent update to its back end. A lot of people noticed. Instead of setting a reminder when you asked for one, Google Search would set an alarm, which isn't really as useful. Now that appears to be fixed.
The makers of SiriusXM's Android client, an Internet version of the notable satellite radio streams, seem to take positive delight in ignoring Android design guidelines. Before today, the app looked like a lazy port of the iOS version... and the iOS version wasn't exactly a looker to start with.
SiriusXM for Android, circa 2014. Or possibly RealPlayer for Windows Mobile, circa 2004. It's hard to tell.
The updated version of the app doesn't exactly look like Material Design, or even Holo (apparently said app developers aren't Android Police readers), but at least it looks like something designed this decade.
Google is cancelling the upcoming iteration of Pwnium, the competition they have sponsored regularly over the past several years. Pwnium has been very useful for Google in protecting Chrome and Chrome OS, because the entire event is about finding holes in the Chromium project. Why did they cancel it, then? For the sake of security!
The trusted face component of Lollipop's Smart Lock system is really neat, but it's a little buggy on the Nexus 6. Shortly after launch, users noticed that the front-facing camera wasn't very good at recognizing them. According to the Google Groups thread, Google has fixed the problem in the Android code and an update is on the way.
Being on the bleeding edge is great and all, but there are drawbacks. For example, many users of Android 5.0 devices are reporting that apps seem to be restarting an awful lot in the background. There are also performance issues that seem to crop up more the longer a device runs without being restarted.
The longer Android 5.0 is in the wild, the more we come across annoying little bugs. It sounds like Google might have broken something in the wireless framework in 5.0 because a sizeable number of users are reporting issues with connecting to their corporate networks after the 5.0 update.
It's not Google's job to account for all the quirks of custom ROMs, but there's been one pervasive bug that has driven some users up a wall in recent weeks. Chrome would render in a bizarre little floating window on ROMs like Paranoid Android. The latest Chrome Beta release fixes that, and you can grab it below.
There's a lot of new stuff in Lollipop, so there are bound to be some bugs. One particularly weird bug can be found in the recent app list. Pull up the app switcher and swipe away all your cards. Go back, and there's another random app card. What gives?
Now that Lollipop is out in the wild to be abused in every which way, we're starting to see the bugs pop up. The latest one has to do with that new flashlight toggle in quick settings. If you turn it on and leave it like that until it times out and shuts off, the camera and flashlight will stop working until you reboot. This is confirmed at least on the Nexus 5.
If you follow Artem on Google+ or check Reddit, you probably saw him discussing the likelihood that Google has delayed updating Nexus devices to Android 5.0. This was originally slated to begin November 3rd, but now the date we're hearing is November 12th. There's no official word, but it looks like a particularly troublesome WiFi bug in the developer preview might be to blame.