droidStory

As previously posted, Google is discontinuing the Nexus One. Well, it only took a couple of days before the remaining stock was depleted. Incidentally, I just sold my N1 on eBay, since I have now moved on to the Motorola DroidX. The Nexus One was/is a great phone and surely helped pave the way for the rapid growth of Android.

Google quietly announced that it will discontinue the direct sale of its Nexus One phone.

This week we received our last shipment of Nexus One phones. Once we sell these devices, the Nexus One will no longer be available online from Google. Customer support will still be available for current Nexus One customers. And Nexus One will continue to be sold by partners including Vodafone in Europe, KT in Korea, and possibly others based on local market conditions.

To ensure our developers have access to a phone with the latest Android OS, Google will be offering the Nexus One through a partner for sale to registered developers. Visit the Android Market Publisher site and log into your developer account to purchase a Nexus One.

This officially marks the end of the N1 experiment.  There are many opinions why this experiment failed. Google has certainly learned a lot about the complexity of the US wireless market and retail operations in general. The N1 offered a glimpse at carrier independence, with unrestricted software access and real-time Android updates. The 3G reception problems and the resulting finger-pointing between HTC, T-Mobile and Google highlighted the inherent problems with this direct sales model.

I believe, that the US wireless market with its carrier specific 3G data frequencies and incompatible wireless network technologies is a key reason for the failure of the N1, and Google’s direct sales model. Why buy an expensive phone without contract subsidy, if you can’t switch wireless providers because the phone wont work on another carriers network?

The DroidX went on sale today. The Verizon online store listing went live around 2AM EDT, and I woke up to an email from Verizon telling me that the DroidX was ready.
Unfortunately it seemed their website was not quite ready for the onslaught of interested buyers, showing some serious overload problems between 7-9AM.  I kept hitting refresh but no luck in getting through to the actual site.
Oh well, off I went to the nearest Verizon store.  It was now a little after 9AM and the store was already filled with over 30 people waiting in line. There was a sign-up kiosk, but only the names of the next 15 or so customers were displayed on the overhead screens. I had no idea how many others were in front of me or how many phones the store actually had on hand. The store manager refused to provide any insight into how many phones they had received and if waiting in line would get me a phone today. I suddenly felt more like being at the DMV than a retail store. Verizon can certainly learn a bit from Apple and how they handle their retail launch events. Still, there sales staff was friendly and worked very fast. An hour later my number was up and I got my DroidX- YES! The sales rep told me that only 18 phones were left. Not everyone left waiting was going to get one today. I wonder when they were told…

My first impression. This phone is awesome indeed. Its giant screen makes my Nexus One look puny next to it.

Setup was a breeze using AppBrain to get all my current apps loaded. But the most notable and very pleasant surprise so far is the battery life, which was a big concern given the fast CPU and large screen. I had charged both the N1 and the DroidX to 100%, and 8 hours later the Nexus One is down to 29%, while the DroidX still has 50% charge remaining. This is amazing, given that I mostly used the DroidX today.

More to follow…

As it turns out FRF83 still wasn’t the final release build of Android 2.2 (Froyo).  Google has now announced the official availability of Android 2.2 on the NexusOne blog.

Starting today, Nexus One users will begin to receive the Android 2.2 (codenamed Froyo) over-the-air software update on their phones. This update provides some great new features including support for making your handset a portable hotspot and support for Adobe Flash within the browser.

If you can’t wait for the OTA update, you can get the latest FRF85B build directly from Google FRF91 build directly from Google and use the upgrade instructions found in some of the previous posts.

Some Nexus One users are reporting that they’ve received the OTA Update of Android 2.2 Build FRF83. I’m a bit skeptical about the OTA, but you can download the latest build, which is rumored to should be the official 2.2 release here:

FRF72 –> FRF83
http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF72.684bd56a.zip

FRF50 –> FRF83
http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF50.38d66b26.zip

You know the drill, or check this post on how to perform the update.

I didn’t see any noticeable differences to the prior build, but had to reinstall Swype to get it working after the update.

This blog and many others have covered the prevailing 3G problems with the Nexus One. Just to recap, the Nexus One is having trouble holding onto a 3G signal reliably, unless the signal is really strong (>-70dBm). The problem is exacerbated by holding the phone, well – like a regular cell phone, with the back resting in the palm of your hand while surfing the web or making a call.

There have been endless threads on the Google support forums, numerous YouTube videos, and even the big gadget blogs picked up on the issue. Personally, I always attributed the problem to poor hardware design that is un-fixable without a redesign and recall of the existing handsets. Others put much hope into a software update. The first OTA update however didn’t do much good other than moving the signal threshold to delay the 3G – Edge flip-flopping.

In recent days the rumor mill on the web spun-up again with news about another imminent update. After months of deafening silence from Google on this issue, finally “Ry Guy” from Google chimes in to crush any speculation. According to Google this is a non-issue: