Google 'no longer investigating' fix for Nexus One 3G issues, advises 'changing your location'
By Vlad Savov 
posted April 22nd 2010 3:29AM
posted April 22nd 2010 3:29AM
[Thanks, Ryan]
posted April 22nd 2010 3:29AM
A look back on popular stories from today in a specific year.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I wonder when Engadget will report the Froyo reports flooding the web since yesterday.
@TareG
go on....?
@TareG yes, please do...
@Jono20
JIT Compiler
Free Additional RAM
Flash 10.1 Support
Activation of Color Trackball
Enable FM Radio
OpenGL ES 2.0 Enchancements
Cross multitouch resolution fixes
http://www.slashgear.com/android-2-2-froyo-in-testing-google-io-release-tipped-2182635/
http://www.unwiredview.com/2010/04/21/android-2-2-froyo-already-in-testing-might-be-announced-in-may/
http://www.androidpolice.com/2010/04/21/android-2-2-froyo-on-its-way-soon/
There's a 3-links limit on Engadget comment posts put u get the picture.
@TareG
By the way, "not engineering software fixes" could very well mean the problem is -indeed- with Tmo's 3G network, and NOT the phone itself.
@TareG Apparently the JIT makes a huge difference. If you go on linpack, you'll see N1s running froyo getting 40mfps! Overclocked, hacked JIT enabled N1s only get 20-30...I can't wait.
@TareG
How about Engadget reporting about the lack of true hands-free Bluetooth operation will all US Android phones....and the lack of any word from Google about a future cure or that the problem exist!
WinMo and Blackberry's provide true hands-free Bluetooth, why can't Android phones???
Is it a software problem? OS problem? A patent infringement problem?
@TareG Probably when some say, different handset in the same network, in the same place, and that are working better, it IS related to the network, yeah, yeah, bla, bla,..
@TareG Well, then how come most complaints are about comparing the N1 to other T-Mobile devices that get perfectly good 3G? I don't even hear of the HD2 have 3G issues either.
@TareG Maybe, but it makes you wonder why the release of this phone on Verizon has been help up for so long. I think this may be just the last factor making me consider the Incredible instead.
@TareG - "problem is -indeed- with Tmo's 3G network, and NOT the phone itself."
Yes! And because they realize the AT&T N1 is not having the same issues. Case closed!!
@Frankenstein Black
Wow that's fucked up! What are the owners supposed to do? Move to another part of the city or another city altogether?
@TareG Still a great phone nonetheless it has some issues that needs attention. Opinions-- http://j.mp/google-phone-disadvantages
@Ted S
What are you talking about. I have my N1 hooked up to my car and I can make and receive calls without ever touching the phone.
@Ted S Holy s*&! you're kidding me, right??!
I called the Nexus One Teh Fail about 2 months ago when the sales figures came out. The thing (along with every other Android phone, of which most have me colored "unimpressed" regardless of the media hype) can't do wireless Bluetooth...which is one of the major reasons I stepped up to a smartphone in the first place??
Yup, it's official. Reception issues + "no longer investigating further engineering improvements" + no hands-free Bluetooth + low sales figures = TEH FAIL.
@TareG I think the consensus is that the problem is in the phone hardware, and it doesn't have a software fix.
@dinoSnake You mean the N1 only does wired bluetooth?
@dinoSnake
agreed, no matter how they spins it... nexus one is a fail
The Nexus One case is hard to understand. I have a G1 and I have the Nexus, both of them have the same 3G signal. This is why I do not think that it's a hardware issue. So far, I'm a happy camper with my Nexus.
@dinoSnake What is TEH
@esmail
If you're on Verizon, I don't see much reason to bother with the N1 over the Incredible unless you REALLY prefer the form-factor or really don't want Sense and its potential to hold up OS updates.
I suspect the imminent release of the Incredible is a large part of the reason why the N1 hasn't come out yet on Verizon.
@ctitanic my thoughts exactly..I have never had a SINGLE issue with the N1 signal, and my cousin and sister both have G1s and sometimes I have signal when they don't...that's why I don't believe it.
@Frankenstein Black No! No way! all of the bandwagon clowns claimed that AT&T network sucks and T-Mobile is best. They all said that! There's no way T-Mobile's excellent and perfect network could do such a thing.....
$hit hitting the fan in 5... 4.... 3...
@LiveFromThe215 I sold my 3Gs a couple weeks ago and got a ATT band N1 and I have had zero problems with it. I can hold my hand over the bottom of it and everything. This phone is great and I have less network problems with this than I did my iPhone. However, this article makes me a little uneasy. I don't want to have a problem (like the multitouch problem) and hear Google just say sorry we are not using anybody to try and fix it. I am not crossing my fingers for a multitouch first because as I can see it is a hardware problem. I really don't play games but I am not going to sit here and make excuses for Google or HTC. I spend $529 for this phone we shouldn't have to deal with these problems and then hear Google say there is nothing we can do. The incredible doesn't have this and.neither will the EVO. So what's the deal why should all the N1 and desire people get screwed?
@LiveFromThe215 I've never had the problem as reported. Not once. No matter how my hand covers the phone.
yikes, that doesn't look good
@drewsmobiletech
Agreed. In fact, after being somewhat cautious about "3G issues" with AT&T on iPhones (I don't think I worried that the phone itself had problems, I was more or less worried about AT&T), I got a N1 and it smokes on AT&T's 3G. In fact, I have yet to use wifi with any frequency, because I get 3G everywhere and wifi drains the battery faster. So I guess AT&T's 3G network isn't as bad as everyone [engadget] claims it to be. It's funny how the hype caused people to prematurely buy N1's on Tmob's network when they could have just waited a couple of months and got them on AT&T and not had any problems. Google would have had a lot less of a headache about it, anyway. The irony is that verizon has yet to get the N1.....oh well.
Its T-Mobile. I have one, and I get better 3G than I did with my G1. Also, the AT&T Nexus one has none of these 3G issues, proving the blame lies with T-Mobile.
@B3astofthe3ast
Exactly. Whenever there's a slight possibility that one of 10 explanations could implicate the Nexus One hardware, you find an Engadget post composed by the speed of light stating this single possibility as a fact.
It's specific to T-Mo.
@B3astofthe3ast
That's not necessarily true. The two versions have different 3G radios, the most relevant component when discussing 3G reception issues.
@B3astofthe3ast
Yeah, AT&T nexus one is great, I've had mine since they came out and I have had zero issues.
-Taylor
@B3astofthe3ast
Nope, not true at all! I had the AT&T version and the problem of not holding a 3G signal is alive and well. I suspect a hardware issue, which is why I returned it.
@TareG read my comment and other comments below it's not T-mobile. Used it with Vodafone around Europe, several Asian carrier etc. All having the same issue.
@Sean76 yeah, my landline nexus one isn't getting good reception either, i took it back.
@B3astofthe3ast Okay, then those of you out there with the T-Mobile HD2.. speak up.. how's the 3G?
@B3astofthe3ast The problem is not with the network only...AT&T users get it (not as often) too, as well as people using the phone abroad.
@Sean76 No problems with N1 on ATT here, holds 3g just fine.
@B3astofthe3ast I am a N1 T-Mo owner and 3G coverage is great from where I am. (Big North American city) Go out to the boon docks and 3G suffers. It IS T-Mo. Not the phone. But what do you expect for $60 dollars a month?
@B3astofthe3ast - It is TMO. Same issue with my Bold2 9700 and HD2. The HD2 is jumping even more so than the N1. The Bold2 simply drops from 3G to GPRS on most calls for me. It's pathetic.
@B3astofthe3ast at&t N1 here. Never had any 3g issues, just an odd glitch that prevents me from sending a text message. The prevalence is low and can be fixed with a reboot.
Hardware seems fine.
Considering how long HTC has been making 3g phones, I would assume its the network. But that's just me and my terrible t-mobile experience talking.
Great work Google! In fact, why don't all Nexus One users just attach a coat hanger to to the device?
So basically: "You bought a defective phone, deal with it."
@verygoodyear
first gen hardware is, well, first gen hardware. I'm sure it will be improved on the Nexus Two. I've been using an N1 for months and have had no issues at all with my reception.
@verygoodyear
lol "move to a different location" as in... "hold your phone towards the sky!!!"
Outstanding customer service, Google, out-f'ing-standing.
@verygoodyear
Or you could ignore the Engadget FUD and see that people on networks OTHER than T-Mobile don't seem to be having any issues. But that would be sensible.
@Tes It's probably a compound of both issues. Whatever the case, being told to turn the phone sound or move location (!) isn't a fix.
@verygoodyear Useful 3g reception is not that big of a deal. Build a bridge & get over it. Lots of love, Eric.
@verygoodyear
How could it be a "compound" if it's not affecting anyone else? What is unique in the situation apart from the carrier? What is Google supposed to do to fix T-Mobile's infrastructure? If your internet stops working do you call Apple or Dell to get them to contact your ISP on your behalf?
@verygoodyear
My nexus one is great. It's an AT&T nexus one though. I suspect the issues are related to tmobile's network.
So it's not "you just bought a useless phone", it's "you're on a useless network."
-Taylor