You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Battery Issues with 9.1 AT&T Wi-Fi Calling

Is anyone else having major issues with CPU thrashing/battery drain when attempting to use Wi-Fi calling on AT&T?


I've had nothing but issues with AT&T's Wi-Fi calling. When it was first released back on October 8, 2015, it was unusable for me - calls to certain people failed or only one party could hear the conversation on those calls. So after a few attempts testing, I gave up. With the release of 9.1, Wi-Fi calling worked properly and calls were handled well. I was happy to see Wi-Fi calling working, as my desk is in a low signal area and I was looking forward to better voice calls.


However, after upgrading to iOS 9.1 I noticed that my battery drained rapidly and my phone was often hot to the touch. I started documenting this drain and would often have a dead phone by 3PM. Over the weekends and in the evenings, my phone seemed normal. I didn't have any of these issues with my 6 while at my desk, so I began looking for the difference. I turned off LTE Voice and Wi-Fi calling and my battery life returned to normal. The next day I turned LTE Voice back on and there was no negative impact on the battery, so the issue seems to be Wi-Fi calling alone.


I wanted to find some way to quantify the effects of Wi-Fi calling on my phone, so I did some searching in the App Store and found an app (System Status - activity monitor, network info, battery charge & memory manager) that allows me to monitor CPU, Battery, Memory usage of my 6s. It shows that as soon as WiFi calling is triggered (turned on & activated by a poor cellular signal), my CPU usage jumps from the 5-10% range to a minimum of 50% and stays there as long as WiFi calling is active. I have confirmed that it is not the fact that WiFi Calling is switched on, but it must be active (Wi-Fi appears in the status area next to AT&T.) Moving to an area of good cellular signal drops the CPU usage as soon as the phone stops using the feature (even though it’s still enabled in the settings.)


Heres a link to a video that I shot showing the impact of WiFi Calling on my phone: https://youtu.be/iaYR6aKy96k You can see that the act of triggering WiFi Calling pegs the CPU at 50% and in the minute that the feature is active, the battery drops 2% from 89% to 87%. There is another thread that deals with carrier settings, but it's for a European carrier: https://discussions.apple.com/thread/7296648?tstart=0


Anyone else seeing anything like this with AT&T? Other US carriers?

iPhone 6s, iOS 9.1

Posted on Nov 13, 2015 8:06 AM

Reply
4 replies

Jan 16, 2016 5:18 AM in response to Brackintosh

It looks like AT&T Mobility has rolled out VoWiFi as an experiment. Thanks for being a beta tester!


There are three key challenges, of which AT&T has apparently tackled two:

  • Emergency calling location. They've definitely worked hard on this to update their ALI database with your address.
  • Handoff from WiFi to VoLTE or Circuit Switched (CS). It appears that when you place a call and move out of th wifi coverage but within LTE/GSM covetagel, the call often doesn't handoff.
  • Battery footprint. VoWiFi isn't nearly as efficient as VoLTE or Traditionap circuit-switched GSM, but (I believe) it takes more energy to transmit a megabyte over LTE than it does over WiFi.

These are all unproven conjecture, but they match my experience and yours.


-- Mark at http://200ok.info/

Jul 23, 2016 10:30 AM in response to Brackintosh

Sorry about the late reply about how I solved the problem, but this thread was called out on mackungfu.org and I realized that I didn't post what fixed my issue here, only at macintouch.com.


Follow Up 4/11/16:

Looks like I found the issue.

The only location where I have access to WiFi and the LTE signal is weak enough to trigger WiFi calling is here in the office. This weekend I used Airplane mode to force WiFi calling at my house and there was no problem with the CPU issue. I did some tests using a Verizon MiFi and WiFi calling worked without any issues. So when I got back in the office this morning, I switched to our guest network and the issues were still there. Tested from the office with the MiFi and no problems.


Began to suspect that it was an issue with our Sonicwall settings, so I did started looking at the network requirements for WiFi calling and came across a post on the Apple Support Forums that mentioned that the MTU Size needed to be 1500 and our Sonicwall’s MTU size on our primary WAN connection was set at 1404. I bumped that up to 1500 and turned on WiFi calling - no CPU problems so far.

Jul 23, 2016 10:38 AM in response to Brackintosh

Brackintosh wrote:


Sorry about the late reply about how I solved the problem, but this thread was called out on mackungfu.org and I realized that I didn't post what fixed my issue here, only at macintouch.com.


Follow Up 4/11/16:

Looks like I found the issue.

The only location where I have access to WiFi and the LTE signal is weak enough to trigger WiFi calling is here in the office. This weekend I used Airplane mode to force WiFi calling at my house and there was no problem with the CPU issue. I did some tests using a Verizon MiFi and WiFi calling worked without any issues. So when I got back in the office this morning, I switched to our guest network and the issues were still there. Tested from the office with the MiFi and no problems.


Began to suspect that it was an issue with our Sonicwall settings, so I did started looking at the network requirements for WiFi calling and came across a post on the Apple Support Forums that mentioned that the MTU Size needed to be 1500 and our Sonicwall’s MTU size on our primary WAN connection was set at 1404. I bumped that up to 1500 and turned on WiFi calling - no CPU problems so far.

Thanks for the followup. That's a really subtle finding; who would normally think of checking the MTU today? There was a time when MTU was a critical setting (for example, over DSL it had to be 1492), but there's no reason to deviate from the default (and upper limit) 1500 bytes today. Congratulations on your detective work!


For readers not familiar with it, MTU (Maximum Transmission Unit) is a limit on the packet size on a local area network. In general, the larger it is the more efficient the network will be.

Battery Issues with 9.1 AT&T Wi-Fi Calling

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.