Google Halts Fixing Nexus One 3G Reception Problems
Ever since the Nexus One smartphone from Google (Made by HTC) came out back in January, T-Mobile users have reported that no matter how strong the network coverage, the phone would fluctuate between 2G and 3G coverage, or wouldn’t have any 3G connectivity at all.
It became enough of an issue that T-Mobile created an official Nexus One 3G issues thread on their community forum in an attempt to log user’s issues in hopes to nail down the issue. Users were instructed to include where they were, and the specific issue they were having. Per the instructions, users were even encouraged to “test” out their issues by using another T-Mobile 3G phone in the same area. I’m assuming this was done to find out whether it was network (T-Mobile) or the phone (Google/HTC).
As you can guess, the user’s responded and logged their issues. In the meantime, Google threw up its own help forum on the issue as well and ensured folks that:
“We’re actively working with our partners to investigate these issues and identify what’s going on. Most people don’t seem to be running into this issue, but for those of you who are, we understand your concern and appreciate your patience. In the meantime, please continue to post information to this thread, and we’ll keep you updated.”
Well, the users kept at it, and around the beginning of February, Google rolled out a software update that among other things (multi-touch, Google maps, etc) included a fix for the 3G woes that users were complaining about. Well, since I am writing this story, it’s obvious that the update did not fix the 3G issues, and as a result, users kept complaining. Engadget even posted a story with a video of the Nexus One dropping down to 2G when the phone was held at the bottom (weird right?). I’m sure Google was hoping it was a simple fix, but after the update, the issue presumably got worse.
Users still complained on both T-Mobile and Google help forums, but I wasn’t even able to find any instance where either company made an attempt to resolve the issue, post February OTA update. That is until April 22nd, when a Google employee made a statement on their forum:
“Hey guys,
I’ve seen some recent speculation on this thread about an OTA to improve 3G connectivity and I want to give you an update on the situation. While we are continuing to monitor user feedback regarding the 3G performance on the Nexus One, we are no longer investigating further engineering improvements at this time. If you are still experiencing 3G issues, we recommend that you try changing your location or even the orientation of your phone, as this may help in areas with weaker coverage.
-Ry Guy”
…So that’s pretty much it. Not really sure what was the culprit, the network of the hardware, but Google stepped up and said “we’re done, so quit bugging us about it”. To add insult to injury, Google also had plans on releasing the Nexus One on Verizon’s network. They seemingly have since changed their minds (and their Nexus One website) to state that folks interested in an Android smartphone jump in line and by the HTC Incredible instead.
I suggest you follow their instructions.
Category: Mobile | Tags: 3G, google, HTC, Nexus One, smartphone, T-mobile
About the Author Terrance Gaines is a husband, father and self-proclaimed Technology Evangelist who shares tech news, reviews, tips and tricks on his blog BrothaTech.com as well as other sites and in print media. You can also find him talking "all things tech" on Twitter @BrothaTech.
See all posts by BrothaTech.
Here is the link to the HTC incredible http://phones.verizonwireless.com/htc/incredible/
Thanks for pointing out the bad link!
Glad I could help
Terrance, I just put the breaks on purchasing the Nexus, thanks to you. You're right I should do some more research. I tried the link you provided for HTC incredible but it wasn't working. I think Verizon moved the site. Thanks for the heads up on this.
@Ileane
Between Google Apps, Calendar, and Gmail (Docs could use some work) I've been pretty happy with Google products (software).
It just sounds like they need to step up their hardware game just a tad more. The N1 was their first foray into the smartphone bidness…that is already flooded with players. So their misstep was prolly magnified due to the already solid competition.
You know, your statement “with the name Google behind it you expect it to work” made me think…A LOT of their products are typically flawed…look at their product catalog…most of the items don't even “Talk” to each other…but we continue to use them b/c for the most part are they're fine. I will however continue to snoop around and poll other N1 owners….good point.
Based on my research, there was no rhyme of reason to who, what, when, and where the problems came from. and I'm sure most of the folks who weren't having any problems were not that vocal with their satisfaction.
It's not a bad phone, you will just have to do some SERIOUS research (coverage in your area, other folks in your area with the N1 & if they have problems, etc) before you buy.
But, when you buy a smartphone with the name Google behind it, you expect it work out the gate. You shouldn't have to conduct a major research campaign just to find out if you will have any problems.
So if I was in your position, I would be torn as well. Maybe you can buy an extended warranty with the phone just in case you are one of the victims?
DARN IT! I was JUST abt to get one in 2 weeks…hmm…I do enjoy my HTC – T-Mobile My Touch, but I am attracted to the faster processor on the Nexus One. The only other android device TMobile offers is the Samsung Behold and I haven't had a Samsung mobile handset in YEARS…not sure I want to go back. This news is disheartening…