Definitely July! [edit]

I'm not 100% on this but wouldn't it motorola's responsibility to make blur work with gingerbread? (which if i had to put money on it, is what is causing the problems)
 
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 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!
 
For the most part yes

Connection problems since 2.3.4 update - Nexus One/Nexus S Forum - Google Phone Forum

Connection problems since 2.3.4 update

--------------------------------------------------------------------------------

Every since I got the OTA upgrade to 2.3.4 last week I'm having a very hard time keeping connections.

Right after the initial reboot I was only able to connect to edge for quite a while. This was at home where I always have a rock solid 3G signal.
Since then I'm often dropping out of 3G and going to edge and often even "G". At time I'm unable to make a call, I'm dropping calls, I'm losing signal completely and people are not able to hear me. I could see it being just one of those things if it happened once, but it's been bad ever since the upgrade. Any idea what the hell is up?

It's a non rooted nexus one BTW.
 
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!

Then yes, that's a Google problem. I have a hard time believing though that all of the issues with GB on the DX is Google's fault. I admit though that I don't know what they all are as I've had no interest in checking into them. What I do know is that once you touch the source code for whatever reason, whether it be for Blur or whatever, all bet's are off so to speak as far as its performance.
 
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.

One bug that's in Android bugs the crap out of me is this one:
If you're using Bluetooth A2DP streaming and you connect to a wireless AP it can cause the A2DP streaming to start skipping. If the wireless AP is good, it's less likely to happen, but if it's crappy, look out. It is beyond annoying. I might just have my phone forget that AP since most of the time it 1. goes down and 2. I turn off my wireless radio anyway to prevent it from happening.

Either way it's a known issue in Android that has been around for a bit.
 
For the most part yes

http://forum.androidcentral.com/xperia-play/91883-drops-data-conectivity.html

Drops data conectivity

--------------------------------------------------------------------------------

So, randomly during the day my phone loses all data connectivity, says i am no longer in my coverage area and that my data is roaming and i will incur serious charges to continue using my data. I don't hardly ever go more than twenty miles from home and never had a problem with my OG droid. The only fix i come up with is rebooting my phone and that dosent fix it all of the time. Any help?
 
Also, name me one Verizon 4G LTE device currently running on Gingerbread?

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.
 
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?
 
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.
 
Yep. Have you read the name printed on the top of the phone?
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.
 
You said, "tell Google to fix it." I agree, and I'm sure they have.

Ultimately though, Motorola (or HTC, etc.) and the carrier are responsible for the software they're putting on the phone. If there are bugs, then they have to work those out. Or just don't put the software on it. This is a major reason why updates come so slowly.
 

Trending Posts

Forum statistics

Threads
956,455
Messages
6,968,322
Members
3,163,549
Latest member
jimmyrichard