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.
The Moto G has been a big seller for Motorola, and the device has seen pretty much universal praise from owners. However, the international version of the device (as well as the Moto X and Moto E) has an odd interface quirk that's driving some users up a wall. The carrier name sits on the left side of the status bar all the time, essentially making the notification area useless for anyone whose carrier has a name longer than a few characters.
Sprint got on the Google Voice train early – about when Google got bored and started ignoring the product. At any rate, things have been fine for users on Sprint, who get tight integration with Google Voice on their Sprint number. Well, except this last weekend. There's a pretty big thread going over at the Google Product Forums of Sprint users reporting strange behavior with GV.
When writing an Android app, one useful feature that developers use when dealing with a potentially long list of options is fast scrolling. First introduced in Android 1.5/Cupcake, this functionality allows a user to grab the scrollbar and drag it down to scroll section-by-section, rather than item-by-item. It appears, however, that the KitKat implementation of this classic Android feature has introduced a bug which is driving some developers crazy.
This bug is certainly one that affects developers more than end users.
Virtual Private Networks (VPNs) aren’t the sexiest topic out there, but they are a pretty vital part of daily operations for almost every major company and many small businesses. VPNs are used to securely connect a computer, tablet, or phone to a company's private network over the Internet, thus allowing people to work remotely while ensuring strict authentication and enforcing administrative policies. Even some power users are apt to set up a VPN if they want to make their home networks accessible while they're on the road.
Certainly, third party keyboards are a real testament to how customizable Android can be out of the box. Since KitKat's rollout, however, people have noticed that the default input method reverts to the default keyboard when updating a paid keyboard app. Worse still, the keyboard you updated actually ends up disabled.
What's interesting about this bug is that it seems to only affect the paid flavor of these apps. Free versions should go unaffected.
No, you're not the only one seeing something odd in the web Play Store – the reviews are all missing the Google+ profile data usually associated with them. Everything says "A Google User" instead. You can still leave reviews, but they won't show up with your name online.
This appears to be universal on the web interface, but hasn't affected the Android app. Note, that includes all content, not just apps and games.
It seems that Google introduced an annoying little bug in the most recent version of Chrome Beta, which just rolled out yesterday. After installing the update and launching Chrome Beta, hotword detection no longer works in the Google Experience Launcher or in Google Now through a different launcher.
If you're an audio perfectionist, you've surely stumbled onto flac, an audio compression format designed to deliver lossless recordings. The file sizes are considerably larger than your average MP3, but the sound quality is unparalleled by lossy compression algorithms. It's not hard to see why audiophiles drift towards flac as their preferred storage medium. Now imagine the latest version of Android is causing stuttering, cracks, pops, and static in the otherwise perfect playback of flac.
As soon as the first orders for the Sony Z Ultra Google Play Edition began arriving at users' doors, the bug reports started rolling in. While this always happen with a new handset, two of the issues quickly emerged as critical. To be more specific: