Google looking into potential Nexus S Gingerbread 2.3.3 mobile data bug

Google's latest Gingerbread update (2.3.3) hasn't been received too well by many Nexus S owners, with Google's decision to change the way colours are presented causing much consternation amongst users, including some on the Neowin staff. Now though it appears Google's flagship smartphone might have another update-related issue - this time stemming from the way the handset handles mobile data.

A lengthy thread over at the Google Support Forums shows more than a few people are suffering from a new bug related to the use of a 3G signal even when connected to WiFi.

According to thread starter 'fizzydx':

Since updating to Android 2.3.3 / I9020XXKB1 / GRI40 on my Nexus S i have experienced issues with WiFi & 3G, 3G allways remains enabled but not active (3G icon allways in status the bar) while the WiFi is connect to a network, the 3G icon should allways disappear when WiFi is enabled and connected to a network, but it doesn't.

We've seen similar behaviour at Neowin towers - some Nexus S handsets refuse to let go of their 3G data signal, with the 3G icon appearing even when the handset is connected to a WiFi base station. Other times users have witnessed the 3G logo appearing, disappearing and then reappearing constantly while the phone is in use. This then causes issues with the Nexus S connecting to Google's services correctly resulting in GTalk disconnects and other connectivity issues.

Google employee 'Paul' chimed into the discussion to say that Google is looking into the issue, though they were not previously aware of an issue.

Hi everyone, Thank you all for the detailed reports. This is the first I've personally heard of this problem. We're looking into it now.

Users speculate that the issue could be related to new APN settings found on handsets since the 2.3.3 update while others say disabling and re-enabling the phone's mobile data connection can provide a temporary fix. Unfortunately though, they have had mixed results when implementing a more permanent fix. 

Hopefully Google has more luck!

Report a problem with article
Previous Story

Xbox 360 gamers spend up to £63 a month on games in the UK

Next Story

Microsoft: WP7 NoDo due "sometime this week" [Update]

35 Comments

Commenting is disabled on this article.

i have same issue for some tme now on my htc desire running desire HD rom, nd i dont even have 3g here. what happens is sometimes usually when on market the E edge connection lits up.

Also another problem, though I'm not sure it's specific to 2.3.3: the first time the phone is activated, the "2G only" option is shown as disabled but you actually need to check this option then clear it, otherwise the phone won't use 3G.

A few features apparently behave that way, their status not being shown correctly the first time, it also happens with the ringer volume level under certain conditions. Overall, it looks like the releases could use more validating.

Running the stock OTA Gingerbread (2.3.3) on my Nexus One (rooted), runs beautifully with some seriously GREAT battery life when compared to Froyo (2.2.3). I hear quite a few N1 owners complaining about similar issues however I haven't experienced anything of the sort.

I've only seen this in the past when I use other ROMs. I see this occasionally on CM7 on my MT4G. CM7 is based on Gingerbread.

Its funny even on my Samsung Galaxy S....on 2.1 and now 2.2 I've had the 3G logo and data be used at home even tho it's connected to my WiFi.....

It sucks because your downloading something and think its coming off your WiFi ie home connection.....then you see your phones 3G data usage spike because its been using that instead!

I installed a APN on/Off Toggle Widget so when at home I turn 3G completely off and when i leave i press the button and turn it back on....

Point is....I shouldn't have too!!! When WiFi is active/connected the 3G should not be used full stop!

Baked said,
Its funny even on my Samsung Galaxy S....on 2.1 and now 2.2 I've had the 3G logo and data be used at home even tho it's connected to my WiFi.....

It sucks because your downloading something and think its coming off your WiFi ie home connection.....then you see your phones 3G data usage spike because its been using that instead!

I installed a APN on/Off Toggle Widget so when at home I turn 3G completely off and when i leave i press the button and turn it back on....

Point is....I shouldn't have too!!! When WiFi is active/connected the 3G should not be used full stop!

So wait you're saying you see it on the Galaxy? Hmmm... I wonder if Samsung made a change they weren't supposed to. I'd report that in the same place (to Google) mentioning what you are seeing. That might be good info.
It might be a radio bug and not a AOSP bug.

cybertimber2008 said,
I'd report that in the same place (to Google) mentioning what you are seeing. That might be good info.

Reported

cybertimber2008 said,
So wait you're saying you see it on the Galaxy? Hmmm... I wonder if Samsung made a change they weren't supposed to. I'd report that in the same place (to Google) mentioning what you are seeing. That might be good info.
It might be a radio bug and not a AOSP bug.

This is why I never buy anything Samsung when it comes to phones. I've learned this the hard way from my Windows Mobile days. Samsung has long delays on software updates, and issues such as the GPS bug that has plagued there devices. Do yourself a favor and go with either HTC or Motorola.

UndergroundWire said,

This is why I never buy anything Samsung when it comes to phones. I've learned this the hard way from my Windows Mobile days. Samsung has long delays on software updates, and issues such as the GPS bug that has plagued there devices. Do yourself a favor and go with either HTC or Motorola.

haha HTC. That made me laugh.

Sorry. My WinMo days tought me the same sad stories about HTC so I laugh at the sight of them and pass on.

Also possible: I don't think the phone can receive or make video calls over 3G when 3G is disabled. All phones I know/have that support video calling over 3G never disable 3G when it's available, just because you 'could' receive a video call. Disabling 3G when on WiFi would completely block off video calls.

Now, when you receive an MMS, it uses 3G always (at least on sprint), and SMS will use 1x. That would cause the 3G logo to appear temporarily.

But as far as no going away... that's another story. Google'll fix it quickly I'd say about 30 minutes after their office open tomorrow.

cybertimber2008 said,
Now, when you receive an MMS, it uses 3G always (at least on sprint), and SMS will use 1x. That would cause the 3G logo to appear temporarily.

But as far as no going away... that's another story. Google'll fix it quickly I'd say about 30 minutes after their office open tomorrow.

So you are saying Google will write and release an untested patch? That is not good.

However, I would be surprised to see Google get on anything fast. We have issues that are worse than this that have existed since 2.0 of Android.

It took how long to get copy and paste implemented in basic Google applications, even though they went after Apple and other for not having copy and paste? Not being able to copy and paste in basic applications like email was just disturbing, and only took them over a year to implement, and it still isn't fully functional in core Google Apps.

Maybe some OSS do gooder will write the fixes for Google, or they can get Samsung's developers to write the fixes as they have done in the past.

Maybe Google's developers are the joke they present themselves to be on the Android development forums. They consistently do not grasp things like async and how it is different than multi-thread, let alone more complex topics like the differences in object programming. They seem to think an object based model (and a broken one) is the same as an object oriented model.

Maybe they will get out a fast fix, but after watching Google and Android for over year, I just don't have the faith in Google that you seem to have.

thenetavenger said,

So you are saying Google will write and release an untested patch? That is not good.

However, I would be surprised to see Google get on anything fast. We have issues that are worse than this that have existed since 2.0 of Android.

You sound uninformed. Did you do any research before posting? Or did you just bable?

You do know that Android 2.3.3 is in DEVELOPMENT. The Nexus 1 and Nexus S are DEVELOPMENT phones. Where in the hell do you think Google will be testing it in.

If you don't know, let me educate you. Android 2.2 (aka Froyo) is the latest STABLE Phone OS and Android 2.3.3 (aka Gingerbread) is in Development. Before any phone gets Gingerbread, they are released first to the Nexus series of phones. This is where it works out there kinks. If you don't like that, Don't buy a Nexus device.

@thenetavenger: no, I don't think Google will *release* the fix 30 minutes after opening the office, but no one knows the source better than google. It'll be quickly "fixed", but the release, yet, that'll take some time after testing. Then again, the "SMS to wrong person" thing was fixed, tested, and released in like 7 business days wasn't it?

@UndergroundWire: You are WAY wrong. 2.3.3 is not development, and the Nexus phones aren't development testbeads. 2.3.3 is released, and anyone can check out the source at any given time, and ship it on a phone. Infact, my HTC Hero is running 2.3.3 thanks to Cyanogenmod and another developer, which they checked out from Google's source, made some changes, compiled and released.

cybertimber2008 said,
@thenetavenger: no, I don't think Google will *release* the fix 30 minutes after opening the office, but no one knows the source better than google. It'll be quickly "fixed", but the release, yet, that'll take some time after testing. Then again, the "SMS to wrong person" thing was fixed, tested, and released in like 7 business days wasn't it?

@UndergroundWire: You are WAY wrong. 2.3.3 is not development, and the Nexus phones aren't development testbeads. 2.3.3 is released, and anyone can check out the source at any given time, and ship it on a phone. Infact, my HTC Hero is running 2.3.3 thanks to Cyanogenmod and another developer, which they checked out from Google's source, made some changes, compiled and released.

No, You're wrong what @UndergroundWire said was correct.

Owatonna said,

No, You're wrong what @UndergroundWire said was correct.

Android 2.3 is a full platform release. The Nexus S phone has shipped to consumers running this OS. Android 2.3 is only in development in the sense that it sometimes receives patches to fix bugs in the final version that originally shipped with phones.

You can read more about shipping versions here (http://developer.android.com/) and here (http://source.android.com/). Android 3.0 is chronologically the latest official, stable release. But note here (http://source.android.com/compatibility/index.html) in the 3rd paragraph that the Android 2.3 platform is the latest to have source code fully released to the community, rather than only manufacturers such as Motorola (with their shipping consumer tablet XOOM).

UndergroundWire said,

You sound uninformed. Did you do any research before posting? Or did you just bable?

You do know that Android 2.3.3 is in DEVELOPMENT. The Nexus 1 and Nexus S are DEVELOPMENT phones. Where in the hell do you think Google will be testing it in.

If you don't know, let me educate you. Android 2.2 (aka Froyo) is the latest STABLE Phone OS and Android 2.3.3 (aka Gingerbread) is in Development. Before any phone gets Gingerbread, they are released first to the Nexus series of phones. This is where it works out there kinks. If you don't like that, Don't buy a Nexus device.

Uhh..This ^^ is one of those stupid comments that makes me feel like I could go free with expletives, but I guess my post would get removed. LOL


Are you kidding me? Nexus S shipped with 2.3. 2.3.3 is NOT a development OS since it was RELEASED to PUBLIC just like 2.3 was and 2.2 was and 2.1 was, etc.. Nexus S is NOT ONLY a development phone. It is SOLD BY GOOGLE to ALL CUSTOMERS. Google tests their OSes internally on THEIR OWN DEVELOPMENT PHONES.

If whatever you said was correct, would you like to be a lab monkey used in a pharmaceutical lab? Because that's exactly what you mean by your comment - all Nexus 1 and Nexus S phones are Development phones. What an idiotic thing to say when it's sold to non-developers.

Get your ****ing facts straight before you post. Morons are the reason why Google and Facebook make money.

Edited by Jebadiah, Mar 7 2011, 8:22am :

As one of the comments states their own team basically debunked that article the next day: http://www.androidcentral.com/...xus-s-and-nexus-one-finally

Samsung is working on 2.3 roms for the Galaxy S as well, there have been leaked roms. It's a released OS not a beta/development toy.
The nexus One & S are phones used by developers for development on the most up-to-date final OS, they are not public beta platforms.

yakumo said,
As one of the comments states their own team basically debunked that article the next day: http://www.androidcentral.com/...xus-s-and-nexus-one-finally

Samsung is working on 2.3 roms for the Galaxy S as well, there have been leaked roms. It's a released OS not a beta/development toy.
The nexus One & S are phones used by developers for development on the most up-to-date final OS, they are not public beta platforms.

What was released for Galaxy S is a leak. It's not official and there are no plans to roll it out. The HTC Flyer which was announced in Mobile World Congress leaked the existence of 2.4 which is also Gingerbread.

UndergroundWire said,

You do know that Android 2.3.3 is in DEVELOPMENT. The Nexus 1 and Nexus S are DEVELOPMENT phones. Where in the hell do you think Google will be testing it in.

yakumo said,

The nexus One & S are phones used by developers for development on the most up-to-date final OS, they are not public beta platforms.

No, Android Dev phones are Android Dev phones. Nexus One and Nexus S run "pure" Android, but they aren't Dev phones (Least, not branded as such anyway).

http://developer.android.com/guide/developing/device.html
To find a a place you can purchase the Nexus S, visit google.com/phone. To purchase an Android Dev Phone, see the Android Market site (requires a developer account).

http://developer.htc.com/adp.html
This update applies to the Android Dev Phone for developers only. The Android Dev Phone with its unique color and pattern can be seen here. This update will not work on the T-Mobile G1 or any other Android powered phone...

See?

thommcg said,


No, Android Dev phones are Android Dev phones. Nexus One and Nexus S run "pure" Android, but they aren't Dev phones (Least, not branded as such anyway).

http://developer.android.com/guide/developing/device.html
To find a a place you can purchase the Nexus S, visit google.com/phone. To purchase an Android Dev Phone, see the Android Market site (requires a developer account).

http://developer.htc.com/adp.html
This update applies to the Android Dev Phone for developers only. The Android Dev Phone with its unique color and pattern can be seen here. This update will not work on the T-Mobile G1 or any other Android powered phone...

See?

Pure Google experience are development phones. They are the only phones that can get updates right away. No manufacturer have announced Android 2.3.X on any phones coming out this year. Why is this so hard for people to understand.

UndergroundWire said,

Pure Google experience are development phones. They are the only phones that can get updates right away. No manufacturer have announced Android 2.3.X on any phones coming out this year. Why is this so hard for people to understand.


I really can't believe you are STILL replying to this!
- Nexus S 4G is coming with 2.3 (although, yea, it's a Nexus, and Google)
- HTC Flyer is coming with 2.3
- The new sony (xperia?) is coming with 2.3
- The GX2 (arriving with 2.2) will be updated to 2.3 this year

And that is all that has been *announced*. Pretty sure most carriers/suppliers have learned not to commit to a release until they are sure they'll release it. *cough motorola samsung*

cybertimber2008 said,

I really can't believe you are STILL replying to this!
- Nexus S 4G is coming with 2.3 (although, yea, it's a Nexus, and Google)
- HTC Flyer is coming with 2.3
- The new sony (xperia?) is coming with 2.3
- The GX2 (arriving with 2.2) will be updated to 2.3 this year

And that is all that has been *announced*. Pretty sure most carriers/suppliers have learned not to commit to a release until they are sure they'll release it. *cough motorola samsung*

What about the devices that have announced 2.4 on it?

cybertimber2008 said,
Well none of them are "Google Development Phones are they? +2 to the timber!

They are development phones in a sense. Don't take it literal. Just like the Motorola Xoom, HTC G1 and Motorola Droid were development devices. It's not a development for the manufacturer. It's for the "geeks" that no what they are doing. All those devices are pure Google devices in a sense. The boot loader is not signed and no customization software came packed with those devices.

After the introduction of the H1 and Droid, Google decided to release just a pure Google phone.

Just to educate you even more, this is straight from the horses mouth: http://android-developers.blog...us-one-developer-phone.html You see how Google calls it a DEVELOPER phone. Hopefully we can put this issue to rest.

The reason why I keep responding to this is because we live in an age of Google. God forbid someone see this page in a related search and see's answers like yours that they are not developer phones. People are lazy when it comes to looking for good information and will take your word as gospel. I just like to be thorough with my information.

-10000000 to the timber. FAIL