What's new

Facetime iPad sleep bug

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Morbeas

Occasional Visitor
I've been having this problem for a few months now and I'm at the end of my rope. The issue is, after my iPad Air 2 (running iOS 8.4) goes to sleep, it will not receive any FaceTime calls. If I wake it, it will go back to receiving calls without any issues. At first I thought there was some iOS bug that disconnected the wifi after going to sleep but that can't be the problem since I continue to get emails and Facebook notifications. There's actually a YouTube video from a few years ago that explains it perfectly:


I'm currently living in Germany. My ISP is Vodafone xDSL running on an EasyBox 904 modem/router. For testing purposes, I have also used my Asus RT-AC87R running in AP mode but the result hasn't changed. After troubleshooting this for months, I decided the issue must be a hardware related problem with the iPad so I went back and exchanged with a brand new unit but unfortunately, the issue persists.

I would REALLY appreciate it if someone could help me solve this issue before I lose my mind.

Thanks very much in advance.
 
I've had this happen to me on iPad Mini (WiFi only, no 3G/LTE)...

Go into Settings/General, scroll down a bit, and you'll see a setting for "Use Side Switch", change it from "Lock Rotation" to "Mute"...

Then toggle the physical side switch down (if up) and then back up again (so that Ringer is not muted) - for me this worked...

Might not work for you, but it's worth a try...
 
I have an Air 2, so no mute switch. :\

PS. I also have a WiFi only model.

hokay...

1) If you have a smart cover, remove it temporarily
2) Sign out of both iMessage and Facetime
3) Check DND (Do Not Disturb), it's in control center, swipe up from bottom, ensure that the "Crresent" icon is not highlighted - if it is, tap it to ensure not highlighted
4) Reset network settings, the iDecvice will reboot- it won't find wifi, so don't do this just yet...
5) After the iDevice restarts, do this... HomeButton/Power-Sleep key together - this forces a hard reboot - it also clears any OS/App caches, which here, likely is a good thing
6) After the restart, find and login to your WiFi network
7) Log back into iMessage with the AppleID of choice, then login to Facetime...
8) Replace SmartCover/SmartCase...

Then you should be ok, but perhaps not...
 
Yeah, I've done all that. Actually, as stated in my original post, I went and got a brand new iPad but the result remains the same. The only thing that it could be is the router. I've pretty much eliminated all other possibilities at this point.
 
I don't see any possible way it could be the router. It sounds like a bug in iOS8.4, or possibly the hardware of the Air 2.
 
No way it's the hardware since this is the second device. It also can't be 8.4 because things were the same with previous versions as well. Last clue that it has to be the router is the fact that the video above is from 4 years ago. If there was a software issue, Apple would've fixed it long ago.
 
Hmmm... one other item - is it not ringing, or not seeing the incoming Facetime page at all? Most debug efforts have been around the ring not happenings, not the device is not responding to the page...

Call from one Apple ID to another Apple ID (don't do both on the same Apple ID), watch the iPad, it should give some kind of alert, if not the audio alert, the screen should wake up and show the incoming FaceTime call...

Another question - FaceTime only? or does this also happen with iMessage?
 
No, the call doesn't come through at all (neither the screen wakes up, nor the audio notification comes through. Just like in the video above). If I open the cover of the device as it's being called, it starts ringing.

PS. I just tested (I had not tested that before) and iMessage didn't come thru either. :(
 
I don't see how what you are describing could possibly be a router issue. It sounds like the issue is completely client side. The only possible router side issue I could see it being is that the DHCP lease is expiring and for some reason the router is not properly assigning a new lease when the client requests it will the client is asleep. That said, I have never heard of such an issue where it was sleep related like that. I've seen clients that won't request a lease renewal while they were asleep, but that is a pure client side issue. I haven't seen any kind of bizarre router side issue where a malformed lease renewal occurs and only impacts the renewal while the client is asleep.

Do ANY other notifications work while the device is asleep? Or is this facetime only?
 
No, the call doesn't come through at all (neither the screen wakes up, nor the audio notification comes through. Just like in the video above). If I open the cover of the device as it's being called, it starts ringing.

PS. I just tested (I had not tested that before) and iMessage didn't come thru either. :(

Take the cover completely off the device, and just let it sleep - does the problem still happen?
 
I have been beating at the same problem for a year. Not the cover, the mute switch, do not disturb, or bad wifi. Or resetting. My solution was to get a MagicJack and hook it to a phone so i can tell my wife to wake up the ipad. Problem continues after installing IOS 10. Obviously a bug
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top