Loss of 3G with T-Mobile Service

[d0lph1nk1ng#AC]

FWIW, I have no problems holding onto 3G with my Nexus One along my entire 30minute drive into work in Charlotte, NC

 

[Jeremy]

The problem with saying that it is a HTC only issue, is that many BB users experienced this problem as well.

Don't forget about my post earlier with other Nexus One users in the UK having the same problem. That would eliminate it being a carrier issue and make it a hardware/software issue.

 

[beaker#AC]

Don't forget about my post earlier with other Nexus One users in the UK having the same problem. That would eliminate it being a carrier issue and make it a hardware/software issue.

While it is true that one device having problems on multiple carriers makes it more likely this is a hardware issue and not a carrier issue, this info alone does not eliminate the possibility of a carrier issue.

Also, this isn't an issue of one device (HTC) having problems on multiple carriers. This is an issue of multiple devices having problems on multiple carriers. Many blackberry users have also reported of 3g dropouts so it seems that this issue is not unique to HTC.

 

[dwhall]

Come on now... We all know it is operator error

 

[dessa]

My N900 sitting right next to my Nexus is fully lit with 3g and 3.5g plus 5 bars. The Nexus jumps between edge, 3g and no signal. Its not TMobile. I hope it is software. Both my G1 and MyTouch had solid 3g.

Same here. My wife's MyTouch 3G will have 3 bars and solid 3G while my N1 will drop bars and 3G. Then seconds or minutes later, back up to 3G. Bounces around like crazy eating up the battery.

 

[MaxLaw]

OK...so it drops 3G--we ain't officially 3g yet here!

I ordered my Nexus One on the evening of the first day (1/5/10). Even though engraved, it arrived within 48 hours. Yeah, my T-Mobile 3G drops in and out, but it has not been an "official launch" or "official announcement (or any kind at all)" regarding 3G for Johns Island, SC. So, surprised I was to get ANY 3G. So, give it a rest for those who did not have an official announcement that they even had 3G--whatday say? (FYI, my Palm Treo Pro with Windows Mobile 6.1 NEVER had any 3G up to the last day that I used it--1/5/10.)

 

[KU Kitch]

I'd say from this article it looks like the radio works just fine, but the software has some sort of issue a la the iPhone... just what I think anyway

 

[showson1]

I'm personally getting better coverage (both 3G and not) than my MT3G did and haven't had the issue of it bouncing back and forth..

 

[LCW]

I've got pretty solid 3G signal strength and retention in my area (Detroit metro, Oakland county specifically... )... I don't seem to be subject to the 3G-to-Edge back and forth switching like many are experiencing...

Although I will say, the speeds are not up to where they should be... I can get only about 850-900 kbps max downlink.... uplink is a decent 400-430 kbps...

Far cry from the 7.2 Mbps that T-Mobile was to have "switched on" on Jan 5th...

 

[TaeKwonDonkey]

Lets try this again...

Those of you on Tmobile with 3G coverage should really check this out
http://forum.androidcentral.com/google-nexus-one/5461-how-only-get-3g-data-your-nexus-one.html

Even if it doesn't fix your problem, its always reversible so there's no harm in trying

EDIT: I've tried twice my hyperlinking isn't working sorry guys

 

[LCW]

Check out these articles...

Pattern emerges for Nexus One 3G problems, points to baseband firmware | Wireless News - Betanews

Eight days later, Google acknowledges 3G problems on Nexus One | Wireless News - Betanews


Seems like 32.19.00.16U_4.02.02.41 is the culprit... oddly, 32.19.00.16U_4.02.02.14 (which is what mine is - thought the .41/.14 was a typo at first!) and 21.19.00.16U_4.02.02.14 are not affected... Which explains why I have personally not seen this "3G switching issue" that some report...

Now... the question is, WHY 3 seperate basebands on identical devices that all are sold through one source (ie. Google.com) and seemingly one a single version available (ie. intended to run on T-Mo, but also sold unlocked...) are those turning out to be two separate "versions"? What's with the 3rd baseband? Overseas model?)


Mine is:

Baseband: 32.19.00.16U_4.02.02.14
Subsidized: No - bought unlocked
Shipped to: U.S.
Network: T-Mobile US
3G Issue?: NO


let's get a tally going....

 

[fmcgirt]

Seems like 32.19.00.16U_4.02.02.41 is the culprit... oddly, 32.19.00.16U_4.02.02.14 (which is what mine is - thought the .41/.14 was a typo at first!) and 21.19.00.16U_4.02.02.14 are not affected... Which explains why I have personally not seen this "3G switching issue" that some report...

Now... the question is, WHY 3 seperate basebands on identical devices that all are sold through one source (ie. Google.com) and seemingly one a single version available (ie. intended to run on T-Mo, but also sold unlocked...) are those turning out to be two separate "versions"? What's with the 3rd baseband? Overseas model?)


Mine is:

Baseband: 32.19.00.16U_4.02.02.14
Subsidized: No - bought unlocked
Shipped to: U.S.
Network: T-Mobile US
3G Issue?: NO


let's get a tally going....

Unfortunately, 2.19.00.16U_4.02.02.14 is what I have and it is most definitely affected in ABQ. All of this stuff about patterns and fixes is pretty much useless IMHO and is probably why we haven't seen any updates or fixes as yet.

Check out the T-Mobile Forums and the Google Support Forums for endless repeats of user conjectures, patterns, etcs, - the posts now number well over a thousand all over the US and the world. This is a big, complicated problem affecting many people with no simple solution in sight. With almost non existent customer support from Google it is made even worse.

Those in the media and elsewhere who are so happy comparing the iPhone to the Nexus seem to forget that good support is a major part of Apples's success with the iPhone which also has had a history of crappy radios on each model - which I can personally attest to. I am very worried about taking a large $ hit on this phone since my 14 day return date is drawing close and I am satisfied with it except for the reception part.

 

[Steven58]

n1 antenna problem causing 3G issues?

There is a demonstration on You Tube that shows that the N1 3G issue has to do with a poorly placed antenna. It shows that if you hold the phone over the bottom, you totally 3G, and then if you chance sides it restores. He did this several times proving it by showing the speedtest scores.

Has anyone been able to duplicate this?

Steven

 

[Rusty Shackelford]

Mine seems to be fit as a fiddle. The only time I've even come close to duplicating is in my basement on GSM with one bar, and it just drops connection all together. Thing is that it's already a weak signal, and I can duplicate with a Bold 9700.

 

[inrelief]

Likewise
CNR - can not reproduce.

 

[Jeremy]

Any of you on T-Mobile still suffering from this issue?

 

[dessa]

Since installing the update, it is better, but still not as good as my wife's MyTouch 3G.
It no longer cycles while I watch, dropping bars, dropping from 3G to Edge, but it still often has Edge while my wife's MyTouch has 3G. And, like the video referenced above, is directional/handhold dependent.
So, I'm "concluding" that they've fixed the "problem", and we are now seeing the limitations of the antenna/radio design. It just isn't as good at the margins as some other phones, like the MyTouch.