While manually syncing your phone's linked accounts isn't something most of us are in the practice of doing these days, there are situations where it can be prudent to disable syncing certain items, such as those you don't find yourself using very often. Previously, when you did want to sync these un-synced items on your phone, you went into the accounts UI in settings and tapped "sync now" to force all the items on an account to sync immediately.
Being on the bleeding edge is great and all, but there are drawbacks. For example, many users of Android 5.0 devices are reporting that apps seem to be restarting an awful lot in the background. There are also performance issues that seem to crop up more the longer a device runs without being restarted.
Many Nexus 9 owners appear to be experiencing a bug that causes OK Google Everywhere voice recognition to simply not work, unless you're on the homescreen. Toggling the options or rebooting the tablet doesn't seem to fix it, and not everyone is affected.
We initially thought this might have been caused by the recent update to LRX21Q (the earliest orders from Google Play shipped with LRX21L), but that's apparently not the case, either.
Now that Lollipop is out in the wild to be abused in every which way, we're starting to see the bugs pop up. The latest one has to do with that new flashlight toggle in quick settings. If you turn it on and leave it like that until it times out and shuts off, the camera and flashlight will stop working until you reboot. This is confirmed at least on the Nexus 5.
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.
Google's hot new item, Android Wear, is barely out of the box, but there's already a pretty big issue deserving of a place in our Bug Watch series. The initial rush of native Android Wear apps is starting to roll into the Play Store as developers get their hands dirty with the freshly released SDK. So far, most of these apps have been given away at no cost, but the few that have attempted to charge a fee have run into a wall.
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.
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.