Nexus S owners, listen up. If you own Samsung's flagship "Google Experience" device, it's likely you've experienced a random reboot bug that we reported on over 2 weeks ago. The Google bug tracker thread for this issue has been a roller coaster of emotion - after getting filled with a large number of comments, it was declined by a Google employee, only to be reopened shortly after due to a public outcry.
The Honeycomb SDK preview, allowing everyone to take a peek and play around with Honeycomb using the Android emulator, was launched yesterday, but after we got past the initial excitement, we found that the emulator itself was dog slow and pretty much unusable. In fact, it was so frustrating to use it that I wanted to punch walls and rip out my hair after 5 minutes with it. And I'm not even going to talk about orientation problems - how the Android team managed to ship the SDK with orientation broken by default (there is a fix for it in the Settings > Display) is beyond me and beyond the scope of this article.
This morning, I noticed an interesting thread in the EVO subsection of the XDA forums that claimed to be able to fix music streaming (which was broken in some apps after the latest OTA), while boosting 3G speeds by .2 to .6 Mbps. As the process is very simple and easily reversible, I gave it a go - but decided that I was going to use SpeedTest to benchmark the changes.
As disappointing as it may be to see the Nexus One - Google's first officially anointed developer phone - still getting Froyo-based updates, that's exactly what just happened. According to several Android Central forums members, a 558kb update to Android 2.2.2 (or build number FRG83G) is currently rolling out over the air to the N1, bringing "important bug fixes" with it.
In related news, the Samsung-built Nexus S - Google's second developer phone - also received an update today, though this one is Gingerbread-based.
About a week ago, Engadget ran an article covering two bugs in Android's Messaging app:
- The first involves an issue where users are directed to a different thread than the one they selected from the notifications bar or the main screen of the SMS app
- The second occurs when users are directed to the right thread but end up having their messages sent to a different person than the one involved in the thread
Shortly after, Google changed the bug's priority from "medium" to "critical" on the bugs Google Code page to show that the company cares.
With Android 2.3, users will have not only a slew of new features (I can't wait!), but also a fix to a security issue present in the previous versions of Android: TapJacking. TapJacking occurs when a malicious application displays a fake user interface that you can interact with, but actually secretly passes interaction events, such as finger taps, to a hidden user interface behind it. Using this technique, a devious developer could potentially trick a user into making purchases, clicking on ads, installing applications, or even wiping all of the data from the phone.
Update: This Gmail client update is only for devices with Android 2.2 or higher.
Gmail for Android received a substantial update from Google this afternoon - and the AndroidPolice team has agreed: some of the improvements are long overdue, while some of them are just plain cool.
The change blurb that you'll find on the Market page lists some of the biggies, but a major one (for us, at least) has been excluded: quick folder switching.
The Galaxy S phones are, without a doubt, among the best Android phones out there, but for some time now, the handsets have been plagued by one potential showstopper - malfunctioning GPS capabilities. Worry not, though - in addition to an update that rolled out a few months ago, Samsung has developed an app called GPSSamsungRestore which is now available from the Android Market for all users of AT&T's Captivate and T-Mobile's Vibrant.
Dropbox users, listen up. Today, the company released an off-Market beta version of the Android app that finally fixes a runaway always-on background service, adds Apps2SD support, and fixes a bunch of other bugs. As far as I can tell, the background service was introduced to allow uploading of files even if the app is closed, except a buggy implementation never shut the service down. In the new release, files are properly uploaded in the background, after which the service correctly shuts down.
Motorola has acknowledged the complaints of a number of DROID X owners who have upgraded to Android 2.2 and are experiencing "issues" related to the update. Some of the issues are minor, but a couple (failure to boot, kernel panic) are definitely not. Motorola is saying the bugs have been squashed, but the fixes will be incorporated into a yet-to-be-announced "future software release." Here's what a Moto employee on the DROID X support forum had to say: