We all use our smartphones differently. Some people rely on them for web browsing and apps, some for texting, and many of us still resort to making calls, you know, when we have to. Even within those categories, several patterns emerge and certain habits and practices have been developed. Many of us have long since abandoned using wired headsets for calling, but a lot of people still prefer them to keeping Bluetooth headsets charged or holding a 5-inch phone against an ear.
We've all heard the story before. A brand new, very popular device rolls out to the public and everybody hurries to get their hands on it. Shortly thereafter, people start to notice some of the more serious issues that degrade the experience or even make the gadget unusable. When that device is a phone and one of those issues is audio quality during calls and recordings, people can become justifiably angry.
In the haze of excitement over getting the latest and greatest from Android, sometimes we forget that some people actually depend on their phones and tablets for work. Within the professional world, mobile access to email tends to be vital. For better or worse, an overwhelming number of businesses and organizations rely on servers running Microsoft Exchange (or other software implementing the protocol) to handle their email and calendar needs. Unfortunately, a minefield of bugs in KitKat's Exchange support are leaving many stranded without access to their employer's servers.
Sometimes relatively insignificant software bugs come together in what can only be described as a perfect storm, wreaking havoc and leaving the victims without recourse. Only a few days after the KitKat announcement, complaints of some rather odd behavior on Nexus devices (mostly Nexus 4s) running Android 4.3 started popping up around XDA, the Google Product Forum, and the AOSP Issue Tracker. People were waking up to find alarms failing to go off and most of their apps crashing instantly.
Google Now is pretty amazing, and it just keeps getting better as Google finds new ways to expose knowledge from its massive data repository. It's hard not to become addicted to everything that Now can offer. But what if you just got your hands on Google's latest flagship phone, went through the setup process, and then discovered Google Now doesn't work? Not only have some Nexus 5 owners had this experience, a few of them have even seen Google Now stop working across all of their other devices.
There seems to be a peculiar bug in the Play Store app that causes it to freeze when you try to install apps with a large number of in-app purchases. Perhaps you would prefer to take this as a sign from the sages at Google that in-app purchases are a bad thing. However, there are plenty of valid reasons to have them. It takes a lot of IAPs to trigger this, but we've confirmed it happens on multiple devices.
Every version of Android has launched with at least one headlining feature. As any true fan would know, the 4.2 camera brought with it a very cool new mode called Photospheres. While the initial hype has dropped off, the popularity of photospheres still continues to grow, thanks in part to improvements in image quality and the addition of a Maps-based community designated for sharing the immersive images. We don't always want a location attached to our regular pictures, but it's pretty rare when we don't want our photospheres to be geotagged.
It has only been a couple of weeks since I wrote about the troubles with multi-touch (well, touch in general) on the 2013 Nexus 7. At the time, Paul Wilcox of Google's Product Support forum stated that the issue was being examined, and about a week later he confirmed that the JSS15Q update addressed the problem. While many people are reporting that the OTA has completely cleared up any touchscreen glitches that had been present, some people haven't seen any improvements, and still others are complaining that the problem has grown significantly worse.