The new iPad has unstable 3G connection

1.) that is what exactly happened to me! Speed is just like gprs speed (when i am travelling around the city)

Same problem here in India.

Updated to 5.1.1 yet have the problem. iPad only connects to Edge and 3G doesn't connect easily whatsoever. Tried resetting rebooting & just about everything. 3G comes on it's own and goes back to edge tried the same sim card on the iPhone 4S and 3G works (tried in the same location). Why can't the iPad just have an enable 3G button under network?? Anyways will try to restore later on this week and will let you know. Hope this bug fixes!

I'm in Italy, my iPad is a DLXH and I've got the same problems with G3 connection, it works maybe for a day or two then I have to power cycle my iPAD in order to be able to connect to G3 again.

I'm Spain, I updated to 5.1.1 and I have same problem, I can't conect to 3g or edge conection after severa, hours at wifi

I'm from Greece, I also updated with the 5.1.1 firmware, but the 3G signal is totally RANDOM and NEVER STABLE.

I only get it after switching off and on flight mode, cellular data, or setting manually the carrier (Vodafone), BUT... when I turn off and back on the device the 3G is not there, instead I only get 2G signal (GPRS, the "o" icon). And the thing goes on and on...

Since this extremely expensive device is my tool of work, I expressly URGE Apple to fix this as soon as possible.

THANX.

Update to 5.1.1 seems to work for me, no problem in switching from and to 3G/2G/WiFi, no problem with network speed.

Italy, TIM, iPad serial DLXH

Ciao!

First of all, I must say that when 3G signal gets lost and turn into 2G (the "o" icon) IT REFUSES TO GET BACK INTO 3G, NO MATTER WHERE I AM, EVEN IN A STRONG 3G AREA!

Experimenting with turning off and back on several device settings (yes, unfortunately, we resort to that, since all else, including the last 5.1.1 firmware, has failed, just to use our device), I found out that in order to have (at least for a while) a 3G signal, I must do as follows:

1) turn off automatic search of the carrier (mine is Vodafone, Greece)... I must select it manually, otherwise any other action is futile, and

2) regularly (when the 3G signal gets lost) turn off the cellular data and watch the carrier icon until all the bars completely disappear, THEN TURN BACK ON the "cellular data" setting.

ONLY THIS WAY, finding 3G signal is feasible.

I address to APPLE engineers to read this post.. it might be proved useful in order to FIX this bug.

THANK YOU.

The 3g connection of my new Ipad has been very unstable after the update to IOS 5.1.1. since last week. It regularly disconnects from 3g network and then it doesn't have any internet connection at all. It's very annoying because I always have to switch settings/mobile data off and on again to get 3g connection back that I only have for the next x hours, but not for days or for a longer time...then, it gets lost again and again.

Before the update (that was meant to solve the problem of unstable 3g connection...), the 3g connection of my new Ipad had been perfect and stable without any problem and I haven't had this problem before,so it must be rooted in the software and the IOS system (update?!?), I think.

That is definitely not what I expect from a product of this price level (and from an Apple product.) They need to fix it ASAP!!!

What do you think, can I do anything to solve this problem on my Ipad or should I wait for the next IOS update? (that will either solve the situation or worsen it...)

Btw, I'm from Hungary (Europe), using Vodafone Hungary 3g network.

I'm exactly in the same situation for my iPad.

I think we have to wait for the next upgrade (hurry up Apple!).

Nice!:(

Where are you from? Which network are you using? Have you had this problem prior to the update 5.1.1. as well?

How did you solve the 3g problem? Ipad replacement or upgrading to 5.1.1. helped both you and your brother?

Ups, sorry, I should have read it before asking...:)

But all in all, its strange that so many have this problem... Some of them are lucky and either a replacement or the update 5.1.1. Could solve this problem... Mine is even caused by the update, I think..