News

February 2, 2010

AT&T and Sprint may support 3G Nexus One soon

More articles by »
Written by: Chad Dreier
Tags: , ,

Slightly stale news, but news none-the-less… Word has it that there could be a Nexus One in the works for both AT&T and Sprint with their supported 3G bands.

Different sources with different tidbits of crumbs, our geeky friends at Gizmodo was kind enough to pull them together.

Short story: There is an FCC filing for a Nexus One that works over WCDMA bands I, II, and V. These are the 3G bands the not only AT&T use, but also many Canadian carriers. Also, a recent inquiry to Sprint Customer Solutions has surfaced. Notice the bold items.

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.

Thank you for showing interest in our products & services. Please let us
know if you would like us to assist you with anything else.

We all know by now that you can purchase an unlocked Nexus One from Google that works on T-Mobile’s networks, as well as AT&T (sans 3G). This is good news for those users dying to get a N1 but requires 3G (who doesn’t require 3G?).







About the Author

Chad Dreier
Just a dude that obsesses over science and technology, and, to contrast, a total plant nut... but not one of those crazy animal rights freaks... Steak = good. I collect knives, like things that go boom, and will take anything I can make over anything I can buy.





 
 

 
 

Samsung Galaxy Note Getting all Dolled up with Rags and Bones Sponsorship Deal

  It looks like Samsung is not stopping with the Super Bowl to push its massive 5.3″ Galaxy Note device. According to Billboard.biz Samsung and AT&T have entered into sponsorship deal that will see the Galaxy Not...
by Alex Hernandez
0

 
 
Samsung-Infuse-4G-Hands-On

Android 2.3.5 Update for the Samsung Infuse 4G Put On Hold

There is nothing like a OEM or carrier that lets their babies walk long before they are ready. Looks like the Android 2.3.5 update for AT&T’s Infuse 4G was not quite ready to run in the wild. Here is what was said on ...
by David Pena
0

 
 
Throttling

Top 5% of AT&T users still being throttled, threshold lowered to 2GBs

It is no secret that smartphone sales are way up, data usage is through the roof and streaming services are killing them. The device technology is there, but the cell tower technology just isn’t. It will be a while before...
by Stormy Beach
4

 

 
Atrix 4G

Update headed to the Motorola Atrix 4G Today

Horray for updates! Am I right? Even if the newest software version for your beloved Atrix 4G isn’t Ice Cream Sandwich, an update is still a welcomed sight. Starting today, the Atrix 4G from Motorola will be start to rece...
by Stormy Beach
2

 
 
Samsung-Galaxy-Note-ATT-560x377

AT&T Galaxy Note Confirmed with Snapdragon Processor Not Exynos

  Some slightly disappointing news for device users that want faster processors and that want AT&T’s Galaxy Note. Looks like the anticipated device will be rocking not the Exynos processor, but a Snapdragon proce...
by David Pena
2

 
 
sprint-logo-1

Sprint’s Valentine’s Deal for a Nexus S Will Sure Warm Some Hearts

That dreaded “Hallmark” holiday is drawing closer to us and there is nothing we can do about it. Us guys have to use our brains to come up with some creative gift or act to make our fair lady’s smile and make ...
by David Pena
0

 




6 Comments


  1. McHale

    First: Google did not submit the FCC approval, HTC did. The FCC tag does NOT say Nexus One like the original Nexus One did. Unless you have some documented proof that it is the Nexus One, it’s the Bravo.

    Second: Some idiot getting an email saying that “WE DON’T HAVE IT. IF WE GET IT, WE’LL ADVERTISE IT.” does not confirm anything.

    So why does your headline state both as fact when NOBODY has a clue?

    Jeesh, turn off the Star Trek, leave the house once in a while, and settle down.


    • CaraHulett

      First off: No where in the post does it say that Google submitted the FCC approval. And unless there’s documentation showing that it’s either handset, its speculation, hence the “Word has it that there COULD be…”

      Second: It doesn’t say “If”. It says “Once it IS launched…” Any logical person would assume they can expect to see it supported by Sprint in the future.

      Your comment is unfounded, even more so than you think this post is. And I love Star Trek.


  2. McHale

    the highest authority on the Sprint phone is a customer service rep who doesn’t even know what the phone is. Hell, if you asked if the “Wonderbread Paperweight” was coming out soon, you’d get the same response. Keep dreaming but the response does NOT confirm anything. ESPECIALLY SINCE SPRINT ISN’T THE ONE RELEASING THE PHONE – GOOGLE IS!

    Did any of you look at the FCC tags? Did nobody notice that one says Nexus One and the other does not? Have any of you ever followed HTC’s model numbers or FCC listings before?

    My point about the title of this article is misleading. Where’s any kind of announcement by ANYONE to substantiate it?

    And my point about Star Trek is still valid…


    • CaraHulett

      LOL! You make me laugh. No one claimed it was fact. There aren’t any words in the post itself to validate your argument. No one claimed Sprint was releasing the phone. And there is nothing stating it was confirmed.

      http://www.androidspin.com/2010/01/29/att-may-be-getting-the-nexus-after-all/

      There are the tags. Along with another post full of maybes for you to make an invalid argument against.

      Your point about the title may be the only valid point you’ve made and if you notice that’s the only thing I didn’t disagree about.

      As for Star Trek, you know you watch it in between your cynical postings in random blogs… ;-p



Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>