See? What did we tell you ... We quickly saw the boot animation stripped off the Nexus One along with the wallpaper and ringtones, and now its Android 2.1 operating system has been ported over to the Motorola Droid. Again, no great surprise there. Of course, being on the bleeding edge comes with its downsides, which often read like pharmaceutical side-effects.

Flan on the Motorola DroidCase in point:

1) Keyboard backlight is no longer functioning properly. The only way to get the keyboard to turn back on is to use the Power widget and toggle the brightness. This is a one-time fix and needs to be done repeatedly.

2) Superuser and the su binary for local root and escalated privileges no longer works (even if pushed to the device). If you drop to a terminal and execute “su” it seems like it wants to do something and then ultimately gives a “permission denied.”

3) Landscape mode app drawer acts weird. The little “home” icon on the screen is off-centered and when pressed launches the Camera application.

4) The Messaging app still notifies you of Messages even when it’s set not to.

5) The carrier shows up as T-CDMA 64

6) General, non-repeatable inconsistencies with the home screens. Issues like no longer being able to swipe to change home screens, or not being able to launch apps from the home screen.

Yikes. That's quite the list. But, obviously, if you take the time to hack one OS onto another phone, this comes with the territory. They're used to it. We're used to it. But at the end of the day, when you're the only kid on your block rocking Android 2.1, these things can seem a bit trivial. [; image via Engadget]