Nexus One Headed to Verizon, AT&T, Sprint?


The Google Nexus One is easily the best Android phone on the market today — at least I have been impressed with the brief play time I’ve had. I know Kevin is still enjoying his Nexus One, based on conversations with him about it. While Google’s business model for the Nexus One is unique, in that they sell the phone themselves to be used on the T-Mobile network, it starts to make more sense if new information that is surfacing holds true.

FCC filings show a Nexus One model that is equipped with the radios needed to work on the AT&T network in the U.S. This would also work in Europe. The original Nexus One will only work on the T-Mobile 3G network, so this new model would enable Google to have handsets that work on both carrier’s networks.

Having a phone that can work on both the T-Mobile and AT&T networks would open up a bigger market for the Google phone, but that might not be enough for Google. Evidence is mounting that the Google phone may soon be appearing on the Sprint CDMA network.

A customer’s interaction with Sprint leads us to believe we may see a Nexus One on that network, too. A Sprint customer asked if the carrier would be carrying the Nexus One, and got this reply:

“Thank you for contacting Sprint regarding the nexus one. Unfortunately, this handset model is not on offer as of now.

Once it is launched, you will see promotional campaigns related to the launch date, cost and the features of the handset on our Web site and other promotional media.”

While this is by no means conclusive, it sure looks like the Nexus One may be coming to Sprint. I guess we’ll have to keep an eye on the FCC for evidence that a Sprint version is indeed forthcoming. A Verizon model already shows as “coming soon” on the Nexus One product page, and this all fits together;  the Sprint and Verizon networks both use the same CDMA technology. That would have Google selling a phone that can work on all major U.S. carriers.

You're subscribed! If you like, you can update your settings


Comments have been disabled for this post