Though there are a plethora of options for backing up your apps and data if you have root access to your device, for those without Superuser privileges, you basically have one option - the Android backup service. Even the backup apps like Helium that don't technically require root are simply front-ends for the backup service. The problems with this part of Android are well-known, extensive and, quite honestly, embarrassing. As if there aren't enough things to complain about with it already, it appears that some folks are having problems restoring encrypted (i.e.
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.
Have you noticed that your devices get slow sometimes? Is your memory usage out of control? One user was having these problems, decided to take matters into his own hands, file a bug report, and get this problem FIXED! User "Amit", clearly frustrated by the fact that his phone runs slower than cold molasses, took to Google's AOSP issue tracker for some help downloading more G-Bs.
Certainly, the addition of NFC functionality into Android has been behind a plethora of useful features in recent years, from mobile payments to beaming files between devices. Unfortunately, for some users who updated their Nexus devices to KitKat, the NFC service which powers all these cool features dies repeatedly, and renders any functions tied to it useless. The good news is, Google has apparently found the root cause of the problem and has marked it to be fixed in a future release.
One of the fundamental differences between Android and every other mobile operating system is the practically unrestricted capability to run services. Without this freedom we could not enjoy something as powerful as a homescreen widget or as straight-forward as a Twitter client with background updates. Aside from games and very simple utilities, it’s becoming increasingly rare to find an app that doesn’t run a service, at least for a short span of time.
When it comes right down to it, there’s a pretty short list of things everybody simply expects a cell phone to be able to do well: making and receiving calls and text messages. We must be able to trust that our phones aren’t failing at the most basic types of communication. Unfortunately, some people have found that the Nexus 5 can’t always be trusted to let them know when somebody is calling or texting them.
If you're idly cruising the Play Store on the web, checking out the most downloaded apps ever, you might stumble onto a little glitch when an install count crosses 1 billion. That's right, billion... We're talking 9 zeros, folks! Hitting this illustrious mark will result in an install range that reads 1,000,000,000 - 705,032,704. Not only does tradition tell us that the larger number should come second, but that is an exceptionally specific amount.
The Google Cast SDK is only just escaping its confines as a developer preview, so it’s not surprising to see a few bugs turning up in some odd places. A couple of simple, but potentially telling glitches started appearing after Google Play Services 4.2 began rolling out a few days ago. This latest update is causing the list of Cast targets to fill with incompatible DLNA-enabled devices and duplicate Chromecasts.