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:
If you have already upgraded to 2.2 for Droid X, you have found some new capabilities. Unfortunately, some owners also found new issues. Here are some of the known issues raised by forums members, with some information about each. It is not intended to be a complete list at this time -- there are many more fixes and improvements in the works. I’ll update this list as information becomes available.
- Stuck on Moto logo after reboot – this was tough on a few owners. Very sorry about that. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release. If you are still experiencing this issue, click here.
- Random rebooting – while there always seem to be new conditions that can cause an electronic device to panic, we do have improvements coming that address and eliminate identified panic states. They will be distributed in a future software release.
- WiFi connection and stability – improvements in WiFi have been developed, to address several problem areas. They will be distributed in a future software release.
- Battery Manager “force close” errors – under some circumstances, pressing the battery icon under Menu > Settings > Battery Manager results in a forced close error. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release.
- Media won’t play – includes “sorry the player does not support this type of audio file," custom ringtone stop working, video won’t play, etc., until after a reboot. We believe we have identified the cause of these errors. A fix has been developed for this and should eliminate the problem. It will be distributed in a future software release.
- Music files cutting off the final four seconds or so – a solution has been developed. It will be distributed in a future software release.
At this time I don't have information about when the next software update will be available -- when I have it, I'll share it here.
This seems to confirm many of the issues our commenters pointed out.
It's good to see Motorola responding to the issues of users directly, but this is why I would advocate for device manufacturers to use bigger test groups when releasing major updates: you simply get more user feedback. The nice thing about beta testing is that the people you give the software to are inherently aware it may cause their phone to go berserk. The problem with small test groups is that you simply don't get a big enough slice of the user ecosystem to ensure that all issues have been addressed, and things like this happen.
As we know, Motorola isn't too happy when their test builds get leaked, but I think a few hundred geeks downloading an unfinished update isn't something Motorola should really worry about. At least not more than an officially pushed OTA update bricking a customer's phone.