Last week, after Google Maps received a public transit-minded update, it became apparent that the app wasn't playing nice with the HTC Rezound. Befuddled user reports spilled in, relaying tales of inexplicable reboots and crashes. As always, the community found a solution but, unfortunately, the only solution ended up being the "uninstall updates" button.
T-Mobile today acknowledged the Maps update's issues with certain handsets, posting a support document related to the HTC Sensation 4G's problems with the app.
It looks like owners of AT&T's Inspire 4G should be expecting an OTA update any time now – HTC posted a notice to their support site earlier indicating that an update carrying software build 3.20.502.2 would begin rolling out July 31, 2012 (today).
The update, which AT&T recommends setting aside about 20 minutes for, brings just a few new features and a small handful of fixes/enhancements. New features include HTC Sense 3.0, "Task Manager," and AT&T Address Book.
Ding-ding-ding! EVO 4G LTE owners, the update you've been waiting for is ready. v1.22.651.3 of the software is rolling out starting today, July 11th, and according to Sprint fixes a whole array of bugs. The most important aspect of the update has to do with Google Wallet which has been broken since pretty much day one of the release. Other changes include improvements to Wi-Fi connectivity, playback of sideloaded videos, the crashing gallery app, calendar reminders, random power cycling, and more.
The HTC One X is a damn good phone. Unfortunately, the One X's overall quality seems not to have been incorporated into HTC's quality control - already there have been reports of bothersome game lag, and now XDA user bigoliver has shed light on an even more grave concern: the WiFi antenna has been acting up on many devices.
XDA also lists countless other videos to prove the point
As demonstrated in the video, finding out whether your One X is affected is simple:
Gently squeeze the side back of your phone, between the camera lens and the volume buttons, if your WIFI signal strength improves only to drop back down when you stop squeezing then you have this seemingly common fault.
Remember that problem Galaxy Nexus devices were having on Sprint where owners couldn't get any connection to any data network at all? Well, if you happened to be one of those owners, how could you forget? Worry not, though! Sprint just announced it will be rolling out a fix over "a 1-2 day period."
You'll need to be connected to a WiFi network to do anything (though this shouldn't be new to you if you're affected by this problem).
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. It doesn't matter if I'm in an area with 2bars or 5 bars, same results. I've tried toggling all of the differnt options under Mobile Networks.
The ASUS Transformer Prime is the hottest Android tablet on store shelves right now, and for good reason; it's thin, fast, powerful, and well-featured. But there's one shortcoming that ruffled a lot of feathers: very poor GPS performance.
The Transformer Prime is a nice tablet. The GPS problems it suffers due to its all-aluminum case, however, are not. We've heard that ASUS is planning on alleviating these problems with a GPS dongle, and now we're finally getting a look at it. It's uh...well, it sure is a dongle
According to Land of Droid, this giant, we'll say, wand-looking thing, is the GPS dongle that's going to "fix" the Transformer Prime's GPS issues.
Google announced today on its Chrome Releases blog that Chrome for Android Beta has been updated to version 0.16.4301.233 (that's Chrome 16.0.912.77 for anyone counting).
The update primarily brings bug fixes, specifically addressing "issues in the compatibility check which prevented Chrome from starting up on some versions of Android 4.0, Ice Cream Sandwich." In other words, whatever it is that broke compatibility with custom ROMs in Chrome's previous update seems to have been eliminated this time around.
We are no longer supporting the Vibrant due to the inability to dial 911. We consider the issues related to this unresolvable without source code from Samsung related to the Radio interface layer and its interactions with the Audio layers and have taken the decision to no longer support this.