Google Acknowledges Nexus One 3G Issues

Posted: Jan 11 2010, 11:35am CST | by , Updated: Aug 11 2010, 6:50pm CDT, in News | Mobile Phones

/* Story Top Left 2010 300x250, created 7/15/10 */ google_ad_slot = "8340327155";

Buy This Now On Amazon

I was out on Greenville Avenue the other day testing my Nexus One's AR apps during an ambitious, 20-degree-weather bar crawl. Then whole time, I had to deal with the infuriating issue of my brand-new, fastest-smartphone-in-the-world Google phone staying stuck on T-Mo's 2G EDGE service. I've been using T-Mobile for a while; this issue didn't feel like a problem with their service.

Like many other Nexus One owners, I'd noticed a major issue with my new phone's software. Apparently, a software error has quite a few Nexus Ones switching randomly between EDGE and 3G, even when the 3G service is working well. After a few days of confusion, T-Mobile (via Electronista) has acknowledged the issue and started working to find a solution.

T-Mobile is asking users with multiple 3G devices to test whether there really is a difference in the Nexus One. They're also asking for details on any service fluctuations or related issues with the Nexus One. From where I'm standing, this seems like a firmware issue, which means it isn't T-Mobile's fault. However, since Google seems to be a bit lacking in customer service, it looks like T-Mo is handling the public relations aspect of all this. Hopefully that means the guys at Google are busy working on a solution.

This story may contain affiliate links.


Find rare products online! Get the free Tracker App now.

Download the free Tracker app now to get in-stock alerts on Pomsies, Oculus Go, SNES Classic and more.

Latest News


The Author

<a href="/latest_stories/all/all/5" rel="author">Robert Evans</a>
The excitement about new smartphones, tablets and anything mobile drive Robert to unearth the latest rumors and developments in this fast moving space. He adopted 4G as soon as it become available and knows where the mobile market is going.
Robert can be contacted directly at




comments powered by Disqus