Google's recently launched Android Wear platform had a bit of a rough weekend when it ran into an unexpected snag regarding paid apps – it couldn't install them. It turns out that the behavior could be traced to a Play Store security feature that was responsible for encrypting paid apps to make them more difficult to pirate; but in doing so, it had also made it impossible to extract and install any micro-apps contained within the apk.
A particularly aggravating issue happens to be plaguing a number of Gmail users on Android as of late. Affected people report a complete loss of the ability to sync their accounts, both manually and automatically. The cause is still unknown, but users report experiencing it following the 4.8 update. Yet clearing updates and returning back to a previous version doesn't fix the problem, suggesting some other source is to blame.
For the last several days, an unknown number of Android users have been getting inconsistent results when using the built-in Google Search app on their phones and tablets. And by "inconsistent," I mean that they aren't getting any at all, instead being greeted by the enigmatic message "can't load search results" whenever they try to use it. While none of the Android Police staff have experienced this, threads on Google Code, Google Groups, and Reddit continue to receive replies.
Ask anybody that spends time in the security circles and they'll tell you that every large software project is bound to have a few long-standing vulnerabilities in the code. Fortunately, there are usually a few people who are paid to close up those holes so you, the customer, don't find yourself the victim of nefarious evildoers someday. Like so many before it, the latest update to Android came with a boatload of changes, at least one of which fixes a potentially dangerous vulnerability that can be used for numerous attacks, including a way to acquire root.
Thursday we reported that T-Mobile's version of the Samsung Galaxy S5 was getting a minor bug fix in the form of a 131 megabyte update. It looks like the cure was worse than the malady, because T-Mobile has abruptly halted the G900TUVU1ANE5 update, putting up a short message on the support page by way of an explanation.
It's no secret that Bluetooth has been a problem child for Android, plagued with poor audio quality and connectivity issues. I've already covered a handful of common problems in a previous post, but another issue has been emerging in the last few months that threatens to virtually kill all Bluetooth operation on a device in the right conditions. The culprit is a nasty little oversight in the Bluetooth Low-Energy code added with Android 4.3 Jelly Bean.
It was just last week that the Google Glass team started pushing out eagerly awaited update to XE16. It was followed less than 24 hours later by a silent hotfix dubbed XRE15C. Unfortunately, these updates left many Glass owners with complaints about stability and an even shorter battery life than the device was already known for. Yesterday, in a bid to resolve some of these issues, the team began rolling out a new update to XE16.1.
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.
The Internet has been abuzz over the recently discovered Heartbleed bug. If you're not already familiar, Heartbleed is a vulnerability in the OpenSSL software library that allows an attacker to steal data directly from the memory space of an application and learn the private keys used to keep data securely encrypted as it travels over the Internet. The implications of this kind of leak are certainly severe, and it has everybody rushing to either install updates that fix the bug or implement workarounds to disable it.
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.