The new Pixel Buds have plenty going for them: they're modern and sleek, they sound nice, and their Android integration is top-notch. But a quick glance at the Pixel Buds support forums shows tons of reports of connectivity problems. The good news is that Google is aware of these issues and a fix is on the way — eventually.
If you keep an eye on Android news, and particularly if you have any interest in Google's latest hardware, it won't be news to you that there's some controversy surrounding the screen on the Pixel 2 XL. While almost every other aspect of the phone has received universal praise, the LG-made POLED display panel has seen plenty of criticism.
Several different complaints have been reported, ranging from a blue tint when viewing the screen at an angle, screen burn-in or image retention, lines of dead or colored pixels, low light graininess, dull (if accurate) color profile, light bleed, and even a strange shadow arc.
Not all app updates are created equal and while most usually fix bugs, add features, and make things better, faster, smoother, more stable, and more enjoyable, it is not the case of the latest Android Wear app update. Google giveth and Google taketh away.
Version 1.4, which was released about 10 days ago, did some UI cleaning, but it dumped a couple of features: the battery stats (for everyone) and the disconnect toggle (for some users). Battery stats weren't the most useful feature all the time, but I liked peeking at them every now and then to check the stamina of my watch.
If you're on the Sprint network, and you're thinking about upgrading to the Galaxy Nexus, you might want to hold off for a bit. Some users in Sprint's forums are reporting that they are unable to connect to Sprint's 3G data network, instead only able to get data via WiFi. Ouch.
Said one user, who attached the above screenshot:
I've attached a screen shot from RF Signal Tracker.
It shows EVDO-A is available and a "Network State" of "CONNECTING"
Every now and then it will get a data connection and the network state changes to CONNECTED, but that will only last for a few seconds.
After a rollercoaster of emotions and months of waiting, the back-from-mythical Galaxy Nexus was finally released on Verizon yesterday, but were the main reasons for the delays, in fact, related to unstable and poor connectivity? I've had endless problems with connectivity on the Thunderbolt (even with the latest firmware), and plenty of you had similar issues with pretty much all other LTE devices.
Can the Galaxy Nexus be no different? I assumed loss of data (even 3G, I'm not even talking about 4G here) and voice was a thing of the past with the Nexus, but having run into this Reddit post with multiple confirmations, I decided to do a quick poll using our social media accounts.
The Nexus S 4G is, without a doubt, a great phone - but as of now, many units ship with a major flaw: they often have trouble connecting to 4G or even WiFi. The issue doesn't affect all Nexus S 4Gs, as shown by Android Central's poll on the subject, but those suffering from it are understandably unhappy with their devices.
And though it may have seemed that Sprint was turning a blind eye to these users' woes, it turns out they've actually been working on an update that will address this issue.
Bearing the build GRJ90, the update will start its four-day rollout on the 11th.
Uhoh, he's at it again. No, I'm not going to make this a rant that is hugely controversial or upsetting. Seemingly contrary to what I write sometimes, I love Android. And anyone who loves Android can agree: the Android Market kinda-sorta sucks sometimes.
Whoa there, let me qualify that - some aspects of the Market are less than fantastic, and I think every Android user has come to realize this. In fact, I doubt it's a stretch to say that the Market's shortcomings are the single biggest reason Android hasn't eaten the iPhone for breakfast in terms of critical acclaim.
Update: Shortly after the update botch was noticed by Notion Ink, they halted distribution of the update in question because it was not downloading completely. If you have a bricked Adam, here is the fix as e-mailed to Notion Ink Fan:
No one here at Android Police has a device to test this fix on - so be careful, and read the warning.
How to flash your Adam and get it working again
WARNING This fix is recommended only if your Adam has stopped booting up after installing the over-the air system update on 24 January. Please don't use the method indicated to flash your Adam with any ROM not from Notion Ink, as it would probably damage your Adam irreparably.