Previous 1 191 192 193 194 195 Next 4,659 Replies Latest reply: Oct 29, 2014 11:58 PM by jasonb b Go to original post Branched to a new discussion.
  • Jameson! Level 1 (40 points)

    What's really strange is that 6.02 has fixed the problem for many, but also made the problem worse or done nothing for some.   I'm in the lucky group.   My i5 and Mini both show amazing improvement with 6.02.   I've connected to may networks over the last few days, and only once, in my office, did I have to restart the phone.   Speeds have been super for me.


    Makes you wonder what's different from device to device.

  • Yepa Level 1 (0 points)

    I just spent 3 hours trying to upgrade my router ios and found out that the iPhone 5 needs both A&G bands enabled on a 802.11n network.  I have a Cisco Valet M20 that only has 2.4ghz (G Band) and I could not get my Apple to connect to the N - only network.  When I downgraded the setting to G + N the iPhones connected.


    A little silly but I'm sure there are reasons that Apple can answer.  It would be nice to have the capability to set my network to only N since that would keep the higher speeds.

  • marshallfromct Level 1 (0 points)



    Every one here has to stop Apple from changing routers ect.  This is the biggest scam since antenna get.  At least there you got a free case!!

  • sbailey4 Level 1 (25 points)

    Yeah its so random make you wonder. I have a buddy with iPad 2 or 3 and its been fine. Last week he updated to iOS 6 (guess it was 6.0.1 by the time he did it) and now he has the "stand 2 ft close to router for it to work" syndrom. New Netgear router. He was perfectly fine with iOS 5.1.1.  Has done every fix mentioned everywhere and no difference. So in his case you would think its 100% software. Except it appears newer netgears have something against iOS 6. Heard reports of downgrading firmware to older versions and it works. Again for some not others. Very strange thats for sure. Unless Apple is using different vendors for some of the hardware and certain chips from certain suppliers dont play well with iOS6. 

  • Paul Derby Level 1 (120 points)

    Obviously, this is a complicated situation or it would have not occurred or been fixed. There are a lot of combinations that have to work together:


    Devices:  iPhone 4 and below that do not have 802.11n and have 802.11b and g

    iPhone 5 that has 802.11a and n


    Routers from multiple vendors.  Amongst these routers there are single transmitter routers that only use 2.4Ghz and dual transmitters that use 2.4Ghz and 5Ghz.  2.4 allows b/g/n 5 allows a/n


    The various routers have settings for WEP, WPA and WPA2.  WPA Auto is tough to implement and only a few vendors access points work well at doing auto negotiate correctly.


    WPA authentication can be either PSK or 802.1x

    the WPA algorithm can be either TKIP or AES  Auto negotiation is an advanced option and buggy clients fail to negotiate.


    So if you take all the vendor access points at each release level  and all the devices and their release levels and settings the combinations are daunting, especially given the variability with the access points and access point settings.


    It might be helpful to list what does and doesn't work when posting.  Fill in as much as you can for your situation following the format I've listed below.    Together we can build a  "settings matrix table" and see what does and doesn't work knowing the underlying settings on both the IOS device and the WiFi Access Point.  If a pattern emerges that works consistently, then people can upgrade and configure their devices to get something that works. 



    *********************   Template for reporting WiFi connectivity performance

    Device:  iPhone 5, US AT&T model

    OS: IOS 6.0.2 using SSID that broadcasts only on 5Ghz


    Access Point:  Ruckus 7363

    Transmitting a unique SSID on 5Ghz, 801.11a/n on channel 36, 40MHz channel width


    Encryption method WPA with PSK authentication (not set to auto-authenticate), AES encryption  (not set to auto-negotiate)

  results:   Throughput:  28 Mbytes/sec down, 23 Mbytes/sec up


    Comment:  works as expected


    ******************************************************************************** *********

    I don't think whining to the press does much to solve technical problems.  Providing good test data back to Apple can help. Apple has a long history of working hard to release working products.  When things don't work, they have always worked to fix the problems. Apple has never consipired to make things difficult for their consumers or to pump out junk to pump up their stock prices.  ALso, they don't hire folks to put out "we are working on it" press releases and status reports.  Instead, they focus on fixing and testing and releasing.


    If we can pull together all the settings for the various combinations that do and don't work, then we can send that to Apple's official bug reporting site and it might help them solve the problem.  I will be happy to submit the aggregated data to Apple's "" web site where they do respond and answer questions and follow up.


    If you are interested in helping to build this table, just post your equipment configuration details and I'll pull together the data and send it on to Apple development to augment what they already have.

  • sbailey4 Level 1 (25 points)

    All good info! And Apple has in the past put out stellar products. The big issue is all these variables you spoke of have existed for some time and the Apple devices with iOS 5.1.1 and previous worked. As soon as iOS6 comes out all HE** breaks loose. While I agree with the fact that there are so many different items (as you mentioned) its a wonder WIFI ever works! So many vendors and options and versions and firmware levels etc. However the truth is that it did work for the most part up until iOS 6. There is no denying that. It would seem to be a bit easier to resolve with that in mind. Look at the wifi code that actually worked in iOS 5.1 and see what the heck  was changed in iOS 6. Those guys are smart and wifi is not a new technology. Just make it work like it did with iOS 5 and all this would not be an issue. OR allow effected users to downgrade to the version that was working for them until its resolved.


    I have not had issues myself with my 4s (lucky I guess) but I know folks who have been brought to dead in the water with WIFI only iPads and a business who all employees who upgraded their iDevices (iPhones mostly) could no longer connect to brand new Netgear router. None of those employees has issues until they updated and the ones that didn't upgrade maintained connectivity.  Anyway you bring a good point with the template but I believe it will be a bit of a moot point as Apple will never see it or use it most likely. However it COULD help users here figure some combination that may work for them until Apple gets it fixed. So thanks for that!

  • sbailey4 Level 1 (25 points)

    Oh and BTW there are as many fixes that have worked  for some or not worked for others as there are the many options and variables you mentioned. Makes it even more complicated and confusing. I mean if changing WPA2/AES to WPA2/TKIP  in your router fixes it for some why not others? Some need the exact opposite to make it work! Some change their DNS and it works and some it makes no difference (not sure how that would solve anything anyway but.....). Setting static IP address fixes some others makes no difference.Oh and lets not forget iOS 6.0.2 fixed some and still not others with iP5 and iPadMinis. Its really bizzar all the variables that have worked for some but not others. Again Apple has their work cut out it would appear (or look at iOS5 code and copy paste ) lol

  • Paul Derby Level 1 (120 points)

    Apple will see the data if it is sent to them through their developer bug reporting system.  I've offered to do the submission.  They have always gotten back to me for every bug I've submitted.


    The BIG difference was adding 802.11n to the 5Ghz band to the iPhone 5. The drivers for IOS 6 added this complication into the mix. 802.11n in 5Ghz behaves a little differently than 802.11n in the 2.4Ghz band.  It doesn't take much to mess up this fragile technology as we all know and have experienced.

  • sbailey4 Level 1 (25 points)

    Ah makes since. Thanks for the explanation. And yes that would be super if you can actually submit that info. Certainly should help pinpoint some common abnormality. Thanks for your efforts hopefully folks will submit some good data.  For the record the business owner I mentioned earlier had a Netgear router, newer model like a month old when iOS 6 came out (sorry dont have the model or specifics) but simply changing  the encryption from WPA2/AES to WPA2/TKIP solved it in that instance. Mostly iPhone 4 and 4s's. And after we made that change they connected right up like nothing ever happened.

  • Russ T Level 1 (5 points)

    Paul Derby wrote:


    Apple will see the data if it is sent to them through their developer bug reporting system.  I've offered to do the submission.  They have always gotten back to me for every bug I've submitted.


    Forgive my ignorance but is the developer bug reporting system only for those who have developer accounts? If so, what's the best channel for the rest of us?


    After getting my replacement, the senior advisor emailed me to see if the new phone was working. I explained I was still having issues and he asked for some information, said he was submitting a ticket to the engineering team and that's the last I've heard from him. I emailed a few days after to see if there was any update but he never responded. I don't want to make any assumptions and I hope it did actually make it to engineering.


    I would agree that if they were taking the reports and doing something with the information, that would be the best. But with the inconsistent responses we've all had with Apple Support and Geniuses, it just feels like this is something they aren't really concerned about addressing. They issue a fix in iOS 6.0.2 yet some of their reps continue to claim there is no known Wi-Fi issues?


    I can only speak for myself - I went through the proper channels and it got me no where. I feel like they don't really care too much about the problem but maybe I'm just making assumptions. I would guess that's where the "let's notify the media" comes into play - some way to pressure Apple so they actually take us seriously.


    Making this issue more frustrating is for those of us using all Apple Hardware including an Apple router. It doesn't give me great confidence when you'd think at the very least they would have thoroughly tested their own phones with their own routers.


    I certainly don't claim to know all of the intricate details that play into this problem nor do I think of myself as an expert nor do I expect perfection from any technology. What I do expect is a bit of transparency. "Yes, we know there is a problem and we're really sorry because we know it's frustrating. We're working on it and if you'd like to be part of the solution, give us some information and we'll do the best we can." Goes a long way with me.

  • Paul Derby Level 1 (120 points)

    sbailey4, is your setup working or not?  It would help to know if you are having problems or not and also to know all the settings in your setup that are listed in the template I put in my earlier post.


    My guess is that your friend was running on the 5Ghz transceiver and changing to TKIP using 5GHz reduces the bandwidth and makes negotiation between the client and the AP much easier.


    But if you can get all the data the pattern of what works and fails may appear from the aggregated data.  Right now there is a lot of speculation about one setting or another without knowing the rest of the settings, the firmware levels and the manufacturer of the access point.

  • Paul Derby Level 1 (120 points)

    Yes, the bug reporting system is for those with developer accounts.  Yes, Apple IOS devices should work with Apple access points. All of this stuff should just work, there is no question about that.  Apple engineering should probably be tied closer to the Apple genius staff and the Apple support staff.....  there are plenty of ideas that we all have on ways to "arm chair" manage Apple to do a better job and how we can use the media to embarrass Apple and how we can post over and over our dissatisfaction with WiFi failures and frustrations on all the social media sites and we could even  carry around signs at their stockholders meetings, but none of that gets the data that the engineers need to isolate the problem areas so they can fix the problem(s).


    Yes, we would probably all feel better if Tim Cook apologized on behalf of Apple for releasing hosed up WiFi. That still doesn't get good, empirical data to the engineers to help them solve the problem. Changing one setting and moving from failure to success isn't good data unless that setting change is tied to the devices, manufacturer of the AP, firmware/software levels of all the hardware involved and the settings for all the devices.


    Is it possible for 20 or 30 of you to take a deep breath, relax, and gather up your data and post it so we could all take a look at a bigger picture of the combination of settings and maybe see what works and what doesn't?  The devices, manufacrturers model numbers, settings and software level numbers and whether that combination works or not might help get some relevant data that would be helpful for the engineering team to use toward solving this situation.

  • CRZ24 Level 1 (0 points)

    Well for the last 3 months what I noticed is N does not work on my ip5. If set to B,G,N then it works but very flakey. If set to G only then it works great, but is limited (slower buffering). On my router if Any selection involving N I cannot disable WMM. So depending on the router if WMM is on always when using N that can be a problem. And the router that let you disable WMM when using N could be the difference in routers?

  • Russ T Level 1 (5 points)

    Look, Paul - if my response came off as a personal attack or something of that nature, I am truly sorry for that was not my intent.


    The fact is that I - along with others - are frustrated (obviously) and a lot of this is venting frustration.


    As for emprical data - help me understand the good it will do to post it on here? That's what we've been doing, haven't we? If there's more specific data - I'm happy to provide it but again I ask the question - what good is it going to do here? How does that get it to the engineers who actually need to make the changes? Point being, I want to be part of the solution; I've tried to be part of the solution; I do care about the "big picture" and I certainly realize (as I've stated numerous times in my posts) that this is a complex issue.


    Apple should be gathering this data, not us. They should be troubleshooting and fixing the problem, not us. I get that there are a lot of very intelligent people who post on here, many of whom are professionals in some branch of IT. But unless you actually work for Apple or have some sort of pull with them, I don't see us swapping info doing a whole lot of good.


    Again, I'm just venting my frustration and looking for a solution. All that being said - I'll be happy to post my data on here - again - if it will help in finding that solution.

  • Paul Derby Level 1 (120 points)

    CZ24, what's the manufacturer, model and firmware/software level of your access point?  If you have an access point with 2 transmitters are you using the same or different SSID's for the two frequencies?


    Are you using WPA or WPA2?  PSK authentication or something else?  TKP or AES encryption?


    If you have a two transmitter access point, is your iPhone 5 locking on 2.4GHz or 5 GHz?


    Definitely that ability to change or not change WMM is important to know, too.  WMM changes the quality of service algorithms for 802.11n and can drastically impact throughput.  That's why it helps to know which router manufacturer, model and firmware level you have. 


    The full set of data would help a lot if you could report the entire environment and all the settings.