A growing thread on the Android issue tracker is home to more and more reports of in-vehicle Bluetooth problems with the Nexus 5, 6, 5X, and 6P. The N5 and N6 allegedly only became affected when their Marshmallow updates rolled out, while the 5X and 6P, which run Marshmallow out of the box, have allegedly had problems from day one. Notably, the Bluetooth issue being cited supposedly was not present in the "M" developer preview releases for the Nexus 5 or 6, suggesting something changed recently to cause it.
The rather irksome bug manifests most commonly as follows. When attempting to dial out to a phone number when your phone is connected to your car via Bluetooth, the call will fail and the car's radio will resume playing whatever audio was on previously. Read More
If you're looking for a nearby place to eat and want directions on how to get there, open Google Maps first. If you try using the Google Search app or the web, you probably won't get the results you want.
You see, Search is currently having a hard time giving out directions. If you tap the icon underneath a restaurant, it will open up Google Maps, but after that... nothing.
Yup, as you can see, I'm somewhere in Virginia. As for the nearest pizza place, it's presumably somewhere along the East Coast.
This bug is pretty easy to replicate. Search for something nearby in the Google Search app or the web. Read More
Android is a complex, multifaceted beast with a lot of moving parts that can break. In the grand scheme of things, this bug isn't a huge deal. It doesn't affect functionality, but it sure is annoying. Here's the deal: get an expanded notification with more than 7 elements on Android 5.1, and you'll probably see a line at the bottom that says, "@17041057."
For most of us, making and receiving phone calls with our devices is something we simply take for granted. Unfortunately, Nexus 6 owners who use Sprint as their carrier are finding that it's not quite that simple.
The Nexus 6 works on all five major US carriers with the simple swap of a SIM card, but that doesn't mean that all problems with the device are universal to all carriers. In this case, a lot of people who have a Nexus 6 on Sprint are reporting that their devices are not receiving phone calls. The problem seems very random and there isn't much of a pattern to it. Read More
Emoji are a staple in conversations for many, many people. They offer a colorful, language-agnostic way to convey thoughts and intent that can’t always come across in a wall of text. Instant messaging is the most common home to these little pictograms, but it's not unheard of for them to appear elsewhere, particularly within contact names. Unfortunately, when Emoji are used to decorate contacts in Gmail, it can interfere with the syncing service and prevent those contacts from crossing between devices.
You’re not going to see any overt warning messages or obvious signs that something has gone wrong, but there are a couple of things to look for. Read More
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. Tuesday night, Google responded to developers with an apology and a set of steps to reconfigure development projects to circumvent the installation issue.
To implement Google's proposed workaround, developers will have to make some simple one-time changes to the configuration of their projects and then endure a couple extra steps to manually package final versions for release. Read More
Remember a few months ago when fellow Android enthusiast Amit was sick and tired of his phone's performance being subpar? Google took notice by marking his issue as "FutureRelease," thus ensuring that one day, the Performance Boosting Thing™ that he so desperately desired would see the light of day. Well, folks, that day has now arrived. The bug has been marked as "Released" and Amit's problem is now officially fixed.
Considering that Google just released Android 4.4.4, it would seem logical to conclude that PBT™ was included in that release. If you don't have a Nexus or another device that stays on the bleeding edge of Android OS releases, just hang tight. Read More
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. Once a device has been within range of enough BLE devices, the entire Bluetooth service will begin crashing.
There is only one truly obvious symptom, but it's incredibly unhelpful for diagnosing the issue. Read More
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. password-protected) backups made using this
feature last-resort functionality.
The symptoms of this bug are pretty cut and dry. Read More
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. Essentially, what happens is that you enable fast scrolling in your ListView either via XML or in code using the setFastScrollEnabled() method of the AbsListView class. Read More