iPad 3 Why 3G does not work after being on WiFi

Unfortunately the new ipad is not compatible with lte in the uk, so we have no switch to turn off and back on. After speaking to Apple tech support who asked me to reboot the ipad my 3g worked for a good half hour (switching wi fi on and off) however after a few hours on wifi 3g was again not responding despite showing a good signall. Another reboot was neccessary. The support assistant said the next thing to do is a full restore, but I don't see mch point loosing all my settings and waiting for a 50gb sync if ths won't fix it!

Today the iPad3 ran for Almosen Twelve hours without losging the 3G/Edge connections.

I started the Day by disabling the WiFi and only with Running the cellular Data Network.

Riding the Bus home, switching cells, finally it just stopped working between 5:08 and 5:15 PM.

No WiFi usage at all. I emailed the system log into my email account, but don't know who to send the log file to. The log file is full of debug traces and I know the event is bracketed in the log file. I only wish I knew how to send this to a developer.

Somewhere in this short sequence the cell connection stopped working..

Apr 13, 2012 5:18:02 PM - SpringBoard [23] (Notice): Posting 'com.apple.iokit.hid.displayStatus' notifyState=0

Apr 13, 2012 5:18:02 PM - SpringBoard [23] (Notice): MultitouchHID: detection mode: 0->255

Apr 13, 2012 5:18:02 PM - UserEventAgent [12] (Warning): DEBUG: Changing screen blanked state: 1

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000345.467539]: AppleDPDisplay::setLCDStateGated:(0x81d49840) Disabling

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000000.000707]: AppleDPDisplay::terminateLink:(0x81d49840) Waited 0 ms for display to disable

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000000.000022]: AppleDPDisplay::terminateLink:(0x81d49840) ret=0x00000000

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000000.000729]: AppleDPDisplay::deviceTerminated:(0x81d49840) device=0x9e64c300

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000000.000102]: AppleDPDisplay::setPower:(0x81d49840) enable=0 ret=0x00000000

Apr 13, 2012 5:18:02 PM - kernel [0] (Debug): [000000.000021]: AppleDPDisplay::setLCDStateGated:(0x81d49840) enable=0 ret=0x00000000

Apr 13, 2012 5:17:46 PM - CommCenter [15] (Notice): Client [com.apple.persistentconnection[apsd,60]] is telling PDP context 0 to go active.

Apr 13, 2012 5:17:27 PM - SpeedTest [564] (Warning): Carrier Name: Swisscom

Apr 13, 2012 5:17:27 PM - SpeedTest [564] (Warning): URL: http://www.speedtest.net/speedtest-config.php?mode=iphone&carrier=Swisscom&conne ction=1&lat=47.355221&lon=8.437785&model=iPad3%2C3

Apr 13, 2012 5:17:26 PM - kernel [0] (Debug): launchd[564] Builtin profile: container (sandbox)

Apr 13, 2012 5:17:26 PM - kernel [0] (Debug): launchd[564] Container: /private/var/mobile/Applications/94B5472D-0BF2-46B0-9AC9-C0262A765FAB [69] (sandbox)

Apr 13, 2012 5:17:16 PM - CommCenter [15] (Notice): No more assertions for PDP context 0. Returning it back to normal.

Apr 13, 2012 5:17:16 PM - CommCenter [15] (Notice): Scheduling PDP tear down timer for (356023336.712711) (current time == 356023036.712720)

Apr 13, 2012 5:16:12 PM - CommCenter [15] (Notice): No more assertions for PDP context 0. Returning it back to normal.

Apr 13, 2012 5:16:12 PM - CommCenter [15] (Notice): Scheduling PDP tear down timer for (356023272.041623) (current time == 356022972.041634)

Apr 13, 2012 5:16:12 PM - CommCenter [15] (Notice): Client [com.apple.persistentconnection[apsd,60]] is telling PDP context 0 to go active.

Apr 13, 2012 5:16:08 PM - kernel [0] (Debug): 012302.236652 hsic-baseband::deviceReadyInterrupt: interval of 99ms, should be >= 100ms

Apr 13, 2012 5:15:49 PM - kernel [0] (Debug): 012282.956943 hsic-baseband::deviceReadyInterrupt: interval of 74ms, should be >= 100ms

Apr 13, 2012 5:15:43 PM - kernel [0] (Debug): 012277.053206 hsic-baseband::deviceReadyInterrupt: interval of 99ms, should be >= 100ms

Apr 13, 2012 5:15:18 PM - kernel [0] (Debug): 012252.287713 hsic-baseband::deviceReadyInterrupt: interval of 99ms, should be >= 100ms

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): virtual void AppleRGBOUT::do_power_state_change(): fSoft: 0 fHard: 1 swapBusy: 0 fController: 0 -> 0

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleSynopsysOTGDevice::handleUSBCableDisconnect

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleSynopsysUSBEHCI[0xc1e68c00]::UIMInitialize - HSIC ports enabled

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleSynopsysUSBEHCI[0xc1a98c00]::UIMInitialize - HSIC ports enabled

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBCMWLANCore::powerStateWillChangeToGated(): cap 0x8000, stateNum 1, dev 0x81e99400 (this 0, provider 1)

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBCMWLANCore::powerStateDidChangeToGated(): stateNum 1, pol 0x81e99400 (this 0, provider 1)

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBCMWLANCore::powerStateDidChangeToGated(): No fBus, deferring reconnect bus...

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleD1974PMUPowerSource: AppleUSBCableDetect 0

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleD1974PMUPowerSource: AppleUSBCableType Detached

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleSynopsysOTGDevice::handleUSBCableDisconnect

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): set_crc_notification_state 0

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000016.635849]: AppleDPDisplay::setLCDStateGated:(0x81d49840) Enabling

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.001788]: AppleDPDisplay::setPower:(0x81d49840) setting bl deadline for 193 ms from now

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.000028]: AppleDPDisplay::setPower:(0x81d49840) enable=1 ret=0x00000000

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.000018]: AppleDPDisplay::setLCDStateGated:(0x81d49840) enable=1 ret=0x00000000

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBaseband::resetDetectInterrupt with 0

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.039413]: AppleDPDisplay::devicePublished:(0x81d49840) newDevice=0x9e64c300

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.031841]: AppleDPDisplay::trainLink:(0x81d49840) Waited 31 ms for link training

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.000168]: AppleDPDisplay::initiateLink:(0x81d49840) Waited 73 ms for display to enable

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): [000000.000021]: AppleDPDisplay::initiateLink:(0x81d49840) _dpDevice=0x9e64c300 ret=0x00000000

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBCMWLANCore::powerOnSystem() : Powering On

Apr 13, 2012 5:12:18 PM - kernel [0] (Debug): AppleBCMWLANCore::powerOn(): stateFlags(4a21)

Apr 13, 2012 5:12:18 PM - CLTM [12] (Error): CLTM: resetting temps: now = 1334329938, last update = 1334329766

Apr 13, 2012 5:12:17 PM - CommCenter [15] (Notice): Telling CSI to exit low power.

Apr 13, 2012 5:12:17 PM - SpringBoard [23] (Notice): Posting 'com.apple.iokit.hid.displayStatus' notifyState=1

İ am having the same 3 g problem in Turkey using the GSM operator Turkcell . Can anyone help for solving that issue

So, as I stated before I am also one of the "lucky" ones in the US that has this problem; but something interesting happened when I open iTunes and connected the iPad to it. By the way, I am using Verizon. A message just pop up stating that an update to the carrier settings for your iPad is available and if I want to download it now! Has anyone in the US using AT&T or Verizon got this message? I downloaded it and I guess on Monday I will find out if this helps or not. I will be out of the "home" area and using the extended 3G where I'm going. I will let you guys know if this really solve the problem.

My iPad appeared to work for a few days after I changed my SIM PIN. However, as others suggested I can confirm that this did not provide a long-term fix. My iPad remains as broken as ever.

Come on, Apple. Please acknowledge this problem and at least let us know that you are working on a solution...

I'm having the same problem. When iPad 3 comes out of sleep, almost every time I have to turn it off and on to get 3G working again, even though the 3G logo and bars are showing, it just keeps on giving the no cellular network error.. My 4S on the same carrier works no problems. Very frustrated.

..so I thought I give it a t try and reset my Network Sessions.

For some minutes I was even able to work on 3G !!!

The side effect of cause was that I was unable to login to my WiFi Router anymore (unable to access WLan Error) I tried several times. Another Router that I have works perfectly. The old Ipad works perfectly with both Routers and the iPad 3 worked perfectly before (besides the 3 G issue)

After Resetting Network settings again. It suddenly worked.

WHAT AN INMATURE PIECE OF HARDWARE THIS IPAD. SHAME ON YOU APPLE!!!!

CONFESS!

UPDATE!

OR RECALL THIS RUBISH!!!!

I have tried everything!

3rd iPad changed by the local Apple distributor in Singapore. Still the same issue - 3G does not work after turning off wifi. It is getting really frustrating. The store and Apple Support does not seem to want to admit that this is a real problem! Can't possibly reset the iPad every other time I step out of wifi range.

Wonder if Apple has any solution to this worldwide problem.

Is it true that in Australia they are giving full refunds to guys who have encountered this issue and not wanting to sit and wait anymore?

After being on wifi and going out of wifi range I am unable to use 3G. Although it shows full signal nothing will work over 3G connection - continually gives me error messages.

Only thing that works: restart ipad. Nothing else works.

Any help out there?

I too have tried resetting network and everthing recommended on apple support, still no good. I've called Optus and they say nothing is wrong with network.

For me the problem isnt just when coming off wifi, it's also happening when on 3G only and almost every time I wake the iPad up to use it. How do I notify apple about this without having to see a genious?

"Is it true that in Australia they are giving full refunds to guys who have encountered this issue and not wanting to sit and wait anymore?"

Apple Australia are refunding iPads because the ACCC took them to court for misleading advertising of the 4G features in this country (there is not yet any compatible 4G network in Australia), so the offer for a refund applies as part of that court settlement not because of any perceived defect or failure of the iPad.

I'm at the Apple store now in Chadstone Victoria typing this. They told me if I want a refund I have to return it to the online store, so they offered me a replacment iPad instead. I am waiting for them to bring the replacement over and we will see how that goes. I'm certainly not holding my breath on this fixing anything. If the replacement does not work, I'll then go for the refund.

Sorry, I have no solution, hope Apple accept there is a problem very soon, presently appear to be not listening and burying ther heads in the sand!!!

I too am experiencing this on my new iPad.

Frustrating and annoying.😠

I could get a refund on the 4G premise that was issued to all purchasers in Australia, but this is not the solution I want. I really like this new iPad and wish to keep it and be able to use it to its' full capabilities.😟

Apple support online, or phone.

AppleCare if you have taken that as an extra insurance.

Good luck as I do not see either as a solution until they accept there is a problem!!!

Presently eyes and ears are closed tightly.

Despite the numbers proclaiming to be affected in this forum...numbers don't lie.

I've booked in to see a genius on Thursday at Chadstone in Victoria to show them the problem so that they can log the issue and hopefully something gets done.

Is this issue pretty much on every new ipad? I have a 64Gb. Thing is, I don't want them to replace it again (would be the second time due to issue with screen) only if the replaced one will have the same problem.

Don't get replacement as you are only getting a machine that I'm sure will have same problem (in my humble opinion)

This appears to be a worldwide problem and seems to be software related not hardware. An iOS update required.

Atleast the problem will be logged with Apple thus giving rise to the number of customers that are struggling with this data connectivity issue.😉

Reading through the forums there would appear to be many temporary fixes, but not much that is permanent.