Someone posted a note on Twitter about the Sidekick fiasco. Apparently the servers that lost data weren't Microsoft servers. They were actually Oracle, Sun, and Linux servers that were at a Verizon data center. Microsoft bought Danger last year, and when they had issues, they spent time and resources to recover the data. And T-mobile, and possibly Microsoft, is giving customers some credit for the hassles.

I had a Sidekick for awhile, and my son has one as well. I thought it was a great device when I had it, with an easy to use keyboard, and some nice features. I'm not sure how they've changed since the Sidekick III, but now that I've had an Android phone, and an iPhone, I think it's way behind the features in those devices.

I suppose some people will spin this as Microsoft not necessarily having the expertise to run these servers, but that's silly. Microsoft bought Danger, who presumably had the talent to administer these. They were at the data center they've been hosted at for some time, which also likely has talent there to help out.

What was amazing is that Microsoft didn't try to spin the PR on this and say this was an Oracle or Sun issue. They left it alone, letting plenty of people blame MS software and use this as an example of why Microsoft software is poorly written.

But was it MS software?

This report says that Microsoft may have been attempting to move the service, and that's certainly possible. Maybe they were to blame and didn't want to raise that issue.

I don't know that a root cause will ever be reached, but I can definitely see T-Mobile moving the Sidekick brand to an Android phone. It's a better OS, it saves them $$, and they consolidate some of their own support.

This does show that the cloud is an issue. I have my devices sync with Google on the cloud for various things, but it keeps copies locally. Something everyone needs to do with cloud services.

I still love my G1, and I got a pleasant surprise recently. I was out at dinner with my wife, and we needed to look something up. So we decided to race, her with her Blackberry Curve (and Verizon), me with my Tmobile G1. The kids were excited, and so I turned it on and saw a note about an update. I clicked "OK", not really thinking about it since I get these messages all the time from apps I have installed on there. Just as my finger was pressing the screen, I read "Android" in the message and couldn't stop myself.

Noooooooooooooooooooooooooooooooooooo

I hate OS updates, especially when I'm trying to do something else. So I sat there, waiting about 10 minutes while it downloaded the update and then restarted my phone. It applied the update as well, so the restart was about 5 minutes more. There were some cool images on the phone as it applied the updates, so at least there was something to look at.

The update finished, I popped a browser, looked up my item (losing horribly in the race) and went on with my evening. The next day, I was riding in the car with Kendall next to me, and I got a message from someone. Normally when I respond, I pop open the keyboard and type my response. This time, I clicked the screen to highlight the text box and was about to open the keyboard when a virtual keyboard popped on screen.

That was cool. I'd never seen it, and with Kendall leaning on my arm, I didn't have to move. I one thumbed a message out, making a few mistakes, but not many, and sent it. All without opening the phone. Since then there are a few times when I've used the virtual keyboard, since it's easy to do, works well, and provides feedback about which item you've pressed. It's not quit as quick as the physical keyboard, but it works well one handed and I don't have to open the screen.

The other interesting thing I noticed was during a phone call. Where I live the voice mail system never connects automatically. When I call, it assumes I need to leave a message and I have to his ***, then enter my phone number and password. However the interaction between the ***, the message to enter a phone number, and then the message for the password, is slow. You can't jump the gun and you have to wait. However when I wait, my phone always goes dark and I have to hit the menu button to bring the virtual dialpad back up to make the entries (or open the device).

This time, I hit *** and then listened for the system. When it responded I was set to hit "Menu", but all of a sudden noticed a padlock icon on the screen with a "double tap to unlock" message on it. A quick double tap and I was entering info again. It doesn't sound like much, but it's a much easier, and simpler way to handle this, and it really made me appreciate the OS.

Little things like that are why I really like Android and this phone. I'm not sure I'd always want to be stuck with the virtual keyboard, but it's nice to have that option.