It's their software
Go into the forums here and find me any device from any manufacturer that currently runs on Gingerbread where there are no reported problems with Gingerbread.Then the bugs would be on every phone with GB. I haven't seen the reports of this being an across-the-board issue with all GB phones. This really falls on the manufacturer and the carrier, i.e., Motorola and Verizon, not Google.
Go into the forums here and find me any device from any manufacturer that currently runs on Gingerbread where there are no reported problems with Gingerbread.
For the most part yesAre they the exact same problems? If not, then it's hard to say it's Google.
For the most part yes
For the most part yes
Neowin.net - Google looking into potential Nexus S Gingerbread 2.3.3 mobile data bug
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!
Interesting - though I've never really seen Moto or any other maker actually fix a problem that was in Android itself - IMHO they seem to be spending the lion share of their time polishing the UI.Neowin.net - Google looking into potential Nexus S Gingerbread 2.3.3 mobile data bug
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!
For the most part yes
Also, name me one Verizon 4G LTE device currently running on Gingerbread?For the most part yes
Also, name me one Verizon 4G LTE device currently running on Gingerbread?
Did you read ANY of my posts regarding gingerbread and OTHER phone manufacturers?Not sure what that has to do with anything. The issue is whether the issues with Gingerbread on the DX is Google's fault. I still say that it's more Motorola's issue. Motorola is taking Gingerbread, modifying it, and putting in on their device, and then selling it (with their name on the device) to Verizon and the consumer. If the software doesn't work, they should either fix it or create a workaround, tell Google to fix it, or don't put it on the device. Regardless, Motorola modified it and put it out on their device.
You said, "tell Google to fix it." I agree, and I'm sure they have.Not sure what that has to do with anything. The issue is whether the issues with Gingerbread on the DX is Google's fault. I still say that it's more Motorola's issue. Motorola is taking Gingerbread, modifying it, and putting in on their device, and then selling it (with their name on the device) to Verizon and the consumer. If the software doesn't work, they should either fix it or create a workaround, tell Google to fix it, or don't put it on the device. Regardless, Motorola modified it and put it out on their device.
Did you read ANY of my posts regarding gingerbread and OTHER phone manufacturers?
Look. You can disagree if you like, but the only thing common to the issues reported by users who have Gingerbread on their phones, regardless of manufacturer, is Gingerbread. From your info, it doesn't look like you own an Android device, and presumably have never owned an Android device. You can't really, honestly think you have any idea about which you speak. That's not an insult or personal.Yep. Have you read the name printed on the top of the phone?
You said, "tell Google to fix it." I agree, and I'm sure they have.
Yep. And I have also read the two names on the back of the phone.Yep. Have you read the name printed on the top of the phone?