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. Read More
Back in December of 2011, the T-Mobile Samsung Vibrant was canned by the CyanogenMod team due to a 911 emergency dialing bug that was considered crucial and unfixable:
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.
Yesterday, a security firm called zvelo demonstrated a vulnerability within Google Wallet, cracking its PIN verification system using brute force, giving Wallet access to anyone who had the exploit. It was also revealed that the hack only worked on rooted devices, and Google swiftly reported that a fix for the bug was already being worked on.
Adding to Google Wallet's security worries, a new hack was posted online today, claiming to give access to Google Wallet (sans PIN) on non-rooted devices, requiring just a few steps to gain user information (and funds). Read More
Since launch, the ASUS Transformer Prime's GPS issues have hampered an otherwise stellar tablet. To make matters worse, ASUS confirmed that the problem was due to the Prime's all-aluminium construction, indicating that a software fix was unlikely. Indeed ASUS was forced to release a new version of the Prime (TF700T), with an updated back panel to improve the GPS functionality. However, ASUS has not given up all hope on the original Prime as a new OTA update (V18.104.22.168) is rolling out, which could fix the GPS drivers. Read More
There's been quite a stir caused in the past few days about a mysterious volume bug which surfaced on the Galaxy Nexus. The bug began drawing attention over at XDA's forums, where several users reported ostensibly random muting, and erratic response from the Nexus' volume rocker.
It was quickly discovered that the issue seemed to have something to do with the use of 2G signal, specifically the use of a 900 MHz frequency used by many European carriers. Read More
The intrepid folks over at XDA are always tinkering away to try and make using your Android device a better experience. And a few weeks ago, one of them (namely, temasek) found that the Android Market has some issues trying to resolve DNS servers when your device is connected over Wi-Fi. This can cause the Market to load slowly, and it's definitely something I've experienced on my own phone.
The solution? Read More
It looks like the touchscreen isn't the only piece of hardware on the Sensation that works when it wants to. Posted today on XDA-Developers, Sensation owner zmfl recounted his experience with the audio signal coming and going on his phone, and having received confirmation of the issue from other members there, enterprisingly figured out the cause of the problem and its solution.
Put simply, the paint around the Sensation's 3.5 mm headphone jack tends to wear away or chip with use. Read More
If you've downloaded or had the Android 2.3.6 update pushed to your AT&T, T-Mobile, or unlocked Nexus S recently without issue, consider yourself lucky. None of this applies to the Nexus S 4G on the Sprint network.
While we reported that the update was breaking Wi-Fi and USB tethering initially, it seems something much, much worse is happening to some users who have received 2.3.6 OTA.
If you check out this Google thread, you'll see a number of poor souls have had all cellular connectivity stripped from their devices after updating. Read More
A few weeks ago, a GSM Nexus S update 2.3.6 (GRK39C) with voice search fixes started rolling out, but it was immediately discovered to break Wi-Fi and USB tethering. After many complaints, Google pulled the OTA, and it seems like they've spent the last couple of weeks making sure everything works as expected.
A new update surfaced tonight, also numbered 2.3.6, but this time bearing build GRK39F. While there is no official changelog, based on the fact that an update with the same exact build hit the Nexus One a few days ago and didn't break tethering, I think it's safe to say it fixes at least that issue (Update: thanks to our buddy Omar for an additional confirmation of working tethering). Read More
On September 14, Sprint revealed that an update to Android 2.3 (Gingerbread) was rolling out for the LG Optimus S. Seems like a good thing, right? Not so fast, actually - it turns out there are some fairly substantial bugs that weren't worked out before rolling out the update. Sprint is aware of the keyboard issue but has yet to acknowledge the other problems users seem to be experiencing, such as issues charging and using USB storage. Read More