E-2043
Level 1 (2 points)

Q: iOS 8 Wi-Fi problems

WI-Fi problems on iPad Air, iPad mini with Retina display and iPhone 5S after upgrading to iOS 8.

Typical results from OOKLA Speedtest before upgrade: Ping 17 ms, Upload 21 Mbps, Download 4.4 Mbps

Typical results after upgrade: Ping 39 ms, Download 2.9 Mbps, Upload 0.47 Mbps

iPad 2 with iOS 7.1.2 get 15 Mbps download and 4.4 upload on the same network.

Resetting network settings on the iOS 8 devices did not improve the performance.

Changing band on the router from 2.4 GHz to 5 GHz did give me back the speed on all devices.

However the speed occasonally drops on the iOS 8 devices, and the signal strengt can go from full til lost connection without moving the devices.

Also sometimes the Wi-Fi SweetSpots app report 0 mbps when the signal strenght is indicated as full and then suddenly go up to around 58 Mbps again.

It is almost like the device is trying to use cellular network that I do not have on the iPads before it suddenly switches back to Wi-fi nettwork again.

I am thinking about going back to my iPad 2 with iOS 7.1.2 that is working perfectly until the Wi-Fi issues are resolved.

 

Any help will be very much appreciated!

iPad Air Wi-Fi, iOS 8

Posted on Sep 20, 2014 9:17 AM

Close
E-2043

Q: iOS 8 Wi-Fi problems

  • All replies
  • Helpful answers

first Previous Page 126 of 223 last Next

  • by elcpu,

    elcpu elcpu Feb 21, 2015 12:49 PM in response to mmurray47
    Level 6 (16,265 points)
    Photos for Mac
    Feb 21, 2015 12:49 PM in response to mmurray47

    The London Times....  Prepare for a new phone bill shock

  • by ctscanner,

    ctscanner ctscanner Feb 21, 2015 2:30 PM in response to elcpu
    Level 1 (0 points)
    Feb 21, 2015 2:30 PM in response to elcpu

    Can someone please post the actual link to the London Times article about Apple wifi issues causing huge data bills?  I googled and can't find it.  Thanks!

  • by Bootsox,

    Bootsox Bootsox Feb 21, 2015 2:59 PM in response to ctscanner
    Level 1 (0 points)
    Feb 21, 2015 2:59 PM in response to ctscanner

    The article sits behind The Times paywall (I read hard copy), someone might be able to post the full article but an abbreviated version is as follows:

     

    Eventually, after hours on the phone to Vodafone, and hours browsing Apple and Vodafone forums, I realised that the problem seems to affect the iPhone users. Because of a quirk of iOS, the Apple-produced software that powers iPhones, users who think they are connected to wi-fi may be inadvertently connecting to 3G without noticing if the wi-fi drops out. The problem seems to strike particularly after iOS is updated, or when users upgrade their iphones. Debbie Gracie, 50, from Hawick in Scotland, and her daughter, Kristen, 21, a student nurse, both experienced an unexpected surge in data usage after updating to the new iPhone 6 and iOS8. “Within one week I had used 1GB of data”, says Debbie. “Before that id struggled to use up my 500MB of data on my old phone. I’ve started switching 3G off when I’m not using my phone so they cant charge me, but I’m still running out of data before my month is up.”

                Online forums tell a similar story. “Apple needs to fix whatever is going on with iOS8. We haven’t changed our phone habits and went from using less than 1GB a month to 3.5GB in two weeks,” said one user on Apple.com Another user added: “I find it ridiculous that Apple is still telling customers that this is the first time they’ve heard of the problem.

  • by allisonfromval,

    allisonfromval allisonfromval Feb 23, 2015 11:20 AM in response to E-2043
    Level 1 (4 points)
    iWork
    Feb 23, 2015 11:20 AM in response to E-2043

    II've been having the same post-ios8 wif-Fi issues as everyone else-nothing fixes it for very long. I've already switched out my router and my 5s phone for another 5s. Does anyone know if upgrading to a 6 might solve it?

  • by rccharles,

    rccharles rccharles Feb 23, 2015 11:40 AM in response to allisonfromval
    Level 6 (8,522 points)
    Classic Mac OS
    Feb 23, 2015 11:40 AM in response to allisonfromval

    Does anyone know if upgrading to a 6 might solve it?


    It's the luck of the draw.  Some iPhone 6 users reports these problems.  Most do not of course.

     

    ( read the article just above yours. )

     

    Robert

  • by tbirdvet,

    tbirdvet tbirdvet Feb 25, 2015 4:23 AM in response to rccharles
    Level 4 (3,025 points)
    Mac OS X
    Feb 25, 2015 4:23 AM in response to rccharles

    I have a 6 and had the issues.  It has been much better after I moved up to an AC type router of some reason.

  • by malbecsranger,

    malbecsranger malbecsranger Feb 26, 2015 6:37 AM in response to danyboy2012
    Level 1 (0 points)
    Feb 26, 2015 6:37 AM in response to danyboy2012

    because of the WIFI issues i replaced recently my iPhone 4 with an OnePlus One with CyanogenMod 11S.

  • by old_chap,

    old_chap old_chap Feb 27, 2015 5:20 AM in response to malbecsranger
    Level 1 (16 points)
    iPhone
    Feb 27, 2015 5:20 AM in response to malbecsranger

    Sorry but I haven't read through all 126 pages

     

    Basically since I upgraded to iOS 8.1.3 my phone keeps dropping wifi connection (at home, work anywhere). Sometimes at home I try scanning, it finds my hub with full signal - but I'm prompted to enter password! Because of this I've exceeded my data allowance, have now turned off 3g to avoid

     

    From the various comments I've read on first pages I presume it's a software bug? It never happened before upgrade

     

    I'm not that technical, but is there anything I can do about it?

  • by Carlcats,

    Carlcats Carlcats Feb 27, 2015 5:34 AM in response to E-2043
    Level 1 (0 points)
    Feb 27, 2015 5:34 AM in response to E-2043

    I have replaced my Iphone 5s four times in the last 6 months and replaced the SIM card twice. Have done factory reset etc. For the latest test, I used a ping app and let it run for 30 min. with no packet loss... yet I loose internet connection.. Since I rely on VOIP to communicate (thanks T mobile for the terrible signal at my house), I can see when it drops out of VOIP. I hope apple fixes this problem sooner rather than later. It is a pain to have to "reset network" on the phone five times a day!

    PS: We also have a Samsung Note 3 at the house and it has better T-mobile cell signal and never drops the network.. I like everything else about my iphone, but I may have to consider Samsung or LG for the three other phones in my household!

    Apple, you are starting to look like Microsoft with premature releases that have not been properly tested.. Oh yeah, lets just use our customers for testing and be a reactive company.. we'll fix it after our clients identify the problem with an "update" and save all that testing money ie: the Microsoft business model... LOL

    PING 192.168.0.1: 64 data bytes

    ---

    64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=26.588 ms

    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=27.951 ms

    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=4.674 ms

    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=28.127 ms

    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=26.825 ms

    64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=39.956 ms

    64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=2.875 ms

    64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=27.348 ms

    64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=30.558 ms

    64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=28.513 ms

    64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=27.036 ms

    64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=28.318 ms

    64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=26.152 ms

    64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=27.527 ms

    64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=27.890 ms

    64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=26.717 ms

    64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=27.665 ms

    64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=27.542 ms

    64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=27.825 ms

    64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=31.834 ms

    64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=27.833 ms

    64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=27.869 ms

    64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=44.200 ms

    64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=29.759 ms

    64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=27.766 ms

    64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=28.027 ms

    64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=29.244 ms

    64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=8.150 ms

    64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=31.549 ms

    64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=27.796 ms

    64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=27.322 ms

    64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=26.602 ms

    64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=2.733 ms

    64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=26.809 ms

    64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=27.338 ms

    64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=28.303 ms

    64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=33.441 ms

    64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=4.020 ms

    64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=27.798 ms

    64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=36.680 ms

    64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=26.608 ms

    64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=26.714 ms

    64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=26.530 ms

    64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=27.953 ms

    64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=28.116 ms

    64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=30.093 ms

    64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=27.160 ms

    64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=29.567 ms

    64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=27.834 ms

    64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=27.008 ms

    64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=27.833 ms

    64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=27.451 ms

    64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=3.846 ms

    64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=31.316 ms

    64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=27.099 ms

    64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=28.238 ms

    64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=33.108 ms

    64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=27.940 ms

    64 bytes from 192.168.0.1: icmp_seq=58 ttl=64 time=3.617 ms

    64 bytes from 192.168.0.1: icmp_seq=59 ttl=64 time=27.861 ms

    64 bytes from 192.168.0.1: icmp_seq=60 ttl=64 time=27.808 ms

    64 bytes from 192.168.0.1: icmp_seq=61 ttl=64 time=4.448 ms

    64 bytes from 192.168.0.1: icmp_seq=62 ttl=64 time=32.675 ms

    64 bytes from 192.168.0.1: icmp_seq=63 ttl=64 time=27.803 ms

    64 bytes from 192.168.0.1: icmp_seq=64 ttl=64 time=27.019 ms

    64 bytes from 192.168.0.1: icmp_seq=65 ttl=64 time=29.213 ms

    64 bytes from 192.168.0.1: icmp_seq=66 ttl=64 time=27.054 ms

    64 bytes from 192.168.0.1: icmp_seq=67 ttl=64 time=27.840 ms

    64 bytes from 192.168.0.1: icmp_seq=68 ttl=64 time=27.555 ms

    64 bytes from 192.168.0.1: icmp_seq=69 ttl=64 time=28.260 ms

    64 bytes from 192.168.0.1: icmp_seq=70 ttl=64 time=27.686 ms

    64 bytes from 192.168.0.1: icmp_seq=71 ttl=64 time=30.915 ms

    64 bytes from 192.168.0.1: icmp_seq=72 ttl=64 time=27.842 ms

    64 bytes from 192.168.0.1: icmp_seq=73 ttl=64 time=31.950 ms

    64 bytes from 192.168.0.1: icmp_seq=74 ttl=64 time=28.089 ms

    64 bytes from 192.168.0.1: icmp_seq=75 ttl=64 time=27.359 ms

    64 bytes from 192.168.0.1: icmp_seq=76 ttl=64 time=27.453 ms

    64 bytes from 192.168.0.1: icmp_seq=77 ttl=64 time=30.056 ms

    64 bytes from 192.168.0.1: icmp_seq=78 ttl=64 time=27.845 ms

    64 bytes from 192.168.0.1: icmp_seq=79 ttl=64 time=27.932 ms

    64 bytes from 192.168.0.1: icmp_seq=80 ttl=64 time=3.742 ms

    64 bytes from 192.168.0.1: icmp_seq=81 ttl=64 time=28.078 ms

    64 bytes from 192.168.0.1: icmp_seq=82 ttl=64 time=27.498 ms

    64 bytes from 192.168.0.1: icmp_seq=83 ttl=64 time=27.860 ms

    64 bytes from 192.168.0.1: icmp_seq=84 ttl=64 time=3.448 ms

    64 bytes from 192.168.0.1: icmp_seq=85 ttl=64 time=27.813 ms

    64 bytes from 192.168.0.1: icmp_seq=86 ttl=64 time=27.646 ms

    64 bytes from 192.168.0.1: icmp_seq=87 ttl=64 time=27.971 ms

    64 bytes from 192.168.0.1: icmp_seq=88 ttl=64 time=27.137 ms

    64 bytes from 192.168.0.1: icmp_seq=89 ttl=64 time=27.674 ms

    64 bytes from 192.168.0.1: icmp_seq=90 ttl=64 time=33.577 ms

    64 bytes from 192.168.0.1: icmp_seq=91 ttl=64 time=28.998 ms

    64 bytes from 192.168.0.1: icmp_seq=92 ttl=64 time=32.813 ms

    64 bytes from 192.168.0.1: icmp_seq=93 ttl=64 time=28.443 ms

    64 bytes from 192.168.0.1: icmp_seq=94 ttl=64 time=3.490 ms

    64 bytes from 192.168.0.1: icmp_seq=95 ttl=64 time=27.205 ms

    64 bytes from 192.168.0.1: icmp_seq=96 ttl=64 time=28.333 ms

    64 bytes from 192.168.0.1: icmp_seq=97 ttl=64 time=26.934 ms

    64 bytes from 192.168.0.1: icmp_seq=98 ttl=64 time=3.230 ms

    64 bytes from 192.168.0.1: icmp_seq=99 ttl=64 time=28.051 ms

    64 bytes from 192.168.0.1: icmp_seq=100 ttl=64 time=28.446 ms

    64 bytes from 192.168.0.1: icmp_seq=101 ttl=64 time=3.620 ms

    64 bytes from 192.168.0.1: icmp_seq=102 ttl=64 time=28.216 ms

    64 bytes from 192.168.0.1: icmp_seq=103 ttl=64 time=30.213 ms

    64 bytes from 192.168.0.1: icmp_seq=104 ttl=64 time=29.482 ms

    64 bytes from 192.168.0.1: icmp_seq=105 ttl=64 time=3.695 ms

    64 bytes from 192.168.0.1: icmp_seq=106 ttl=64 time=27.340 ms

    64 bytes from 192.168.0.1: icmp_seq=107 ttl=64 time=28.449 ms

    64 bytes from 192.168.0.1: icmp_seq=108 ttl=64 time=28.200 ms

    64 bytes from 192.168.0.1: icmp_seq=109 ttl=64 time=31.881 ms

  • by jarred125,

    jarred125 jarred125 Feb 27, 2015 6:20 AM in response to old_chap
    Level 1 (0 points)
    Feb 27, 2015 6:20 AM in response to old_chap

    No need to read all the pages, just 3 back there is some details on the issue. It is a software issue, it is NOT related to your router in the house, etc. I have high end equipment at home used in corporate environments and still suffer the problems everyone on here is talking about. There is a good article that discusses the issue from a technical perspective, search for "WiFried iOS 8" and you'll find the article (medium dot com).

     

    Let's hope Apple is up to the task .. otherwise they will have a lot of upset customers. Between my wife and I we have 4 iOS devices and 1 Macbook and each have the problem. My cousin's family has 4 iOS devices as well and experience the same issue (on newer AC hardware). My friend's family has 5 iOS devices and they experience the issue as well. I run support for two locations that have numerous people connecting to enterprise grade hardware and they experience the same issue (at random times). It is a bug in OS X and iOS (they share a codebase).

  • by old_chap,

    old_chap old_chap Feb 27, 2015 6:39 AM in response to jarred125
    Level 1 (16 points)
    iPhone
    Feb 27, 2015 6:39 AM in response to jarred125

    Thanks for that - I was beginning to think it was my phone & started looking for a replacement (possible Android to avoid the issues with Apple). My wife's iPhone doesn't have any problems but realised she's using IOS 7

     

    Wonder how long before Apple decides to take notice?

  • by elcpu,

    elcpu elcpu Feb 27, 2015 7:19 AM in response to old_chap
    Level 6 (16,265 points)
    Photos for Mac
    Feb 27, 2015 7:19 AM in response to old_chap

    This has been going on since September. Apple has called a few of the posters here (me included) to collect data but they have not solved the problem which is now five months old. I have been told that the programmers are working on the iWatch and our issues are not as important. Lot of us are loosing confidence on Apple products. They need to fix this NOW.

  • by Lisa G from the OC,

    Lisa G from the OC Lisa G from the OC Feb 27, 2015 7:49 AM in response to jarred125
    Level 1 (4 points)
    iCloud
    Feb 27, 2015 7:49 AM in response to jarred125

    Thank you for your post.  It confirms that I am spending too much time on this issue and am just working around it painstakingly.  But that means I will also not buy another Mac until this gets fixed as it wouldn't benefit.  I will go back one more time to the Genius Bar on this as I'm no longer under Apple Care but my reformat is. 

  • by Carlcats,

    Carlcats Carlcats Feb 27, 2015 9:09 AM in response to Carlcats
    Level 1 (0 points)
    Feb 27, 2015 9:09 AM in response to Carlcats

    I'm doing a factory restore and will only download the network ping app to check the network stability.. This will also discard the "apple" excuse that if i restore from a back up I may be restoring the problem too... will test the VOIP and see if the network is still unstable.. will post results later today.

    c

  • by nazarite99,

    nazarite99 nazarite99 Feb 27, 2015 9:46 AM in response to elcpu
    Level 1 (0 points)
    Feb 27, 2015 9:46 AM in response to elcpu

    I completely agree with you elcpu, I sent the following information to them on the Feed back form (link below as it is also the place to report a bug).  This is the second time that I have done this.  What I did not mention is that I am losing confidence in there ability to make working software.  I would bet, that the Apple Watch software will be extremely buggy and they will have to focus more time on that and not fix and issue that has been around since September...since September (now 5 months).  Really...really Apple engineers!   Delegate this issue to other engineers!

     

    "I continuously lose Wi-Fi connection on my iPhone 6 (64GB - Space Grey) from various wireless routers.  This has happened from my home wireless router, in the past and continuously occurs from my work wireless router.

     

    This has been an on going issue, for me, since November 2014 and I have had my phone exchanged twice and my wife's iPhone 6 (16GB) once. 

     

    This is pathetic, as many people/customer's know this is a known issue.  I have also spoken with two Apple reps that have gathered information from my previous phones and I have even sent in my phone to your engineering team earlier this year.  Fix this horrible iOS software".

first Previous Page 126 of 223 last Next