>> London Lad wrote:
RParker, I hear what you say and thank you for a civilized reply, but:-
At home I use a cluster of four Cisco AP541N wireless access points. I have run this set-up for just over 4 years with zero issues. Wireless N, WPA2 encryption, 20Mhz spacing, latest software etc etc. I have numerous clients, 2x apple tv, an airport express, 2x freesat boxes, a TV, 8 CCTV cameras, 2x airplay speakers,2x windows laptops, 3 x iphones 2x ipads, plus visitors equipment from time to time.
All the iphones and ipads that were updated to ios8 developed the bug. No ios7 products have a problem, no non Apple products have any problem
I use 2 offices, one has a BT home hub 5? wi-fi router, the other has a BT fibre set up and a BT businesses router providing Wi-Fi.
I spend time in friends offices and houses and they have a selection of wi-fi set-ups. In my companies workshop we have 6 or 7 wi-fi routers set up to provide different environments for testing. My iphone 5s running ios8.2 shows the bug symptoms on all of them as does my ipad 3.
Prior to ios 8 I had no wi-fi related problems.
I have found that setting my waps to wireless g only and WPA (not WPA2) will eliminate the password rejection problem but the slow / no hand off, slow speed and airplay problems remain.
If you are correct (and I don't believe this for one minute) and apple have made ios8 only compatible with a handful of wi-fi routers that most people have never come across its still a problem with ios and not the properly certified router.<<
OK I see your point.
It worked and the only change made was with respect to the iOS. OK that's good information..
However, I bet that if I brought my iPhone 6 plus to your setup it will work for me, how do I know that because I have taken my iPhone 6 out of the country recently, and I have been on a few planes, at 4 different airports, and many hot spots with just about every router brand you can think of and a bunch I never even heard of.. I didn't want to pay roaming so I used WiFi everywhere and whenever possible.
Ask me how many times I lost connection.
ZERO.
So you have problems but you are trying to pin this on iOS 8.. you said the magic word UPGRADE, there really is no such thing as an "upgrade" it merely replaces the binaries with newer binaries and not "refresh" the binaries with newer program.
So your phone had settings that worked before iOS8 came along, everything is great.
Now you move from iOS 7 to iOS8, and it fails.
Yea that does sound like a problem, but that's a problem with inherited settings. If iOS8 were the root of the problem than ALL iOS8 devices would have the SAME problem but they do not, I am proof of this, and I upgraded from 8.0, to 8.01, to 8.1, 8.1.2, 8.1.3 and now 8.2.. still not a problem.
So you cannot simply blame the OS, that's my only point from the outset. We share the same binary code, something else must be a problem which is probably why you are upset with Apple, and while that DOES sound like an issue with Apple, its hard to argue with logic that iOS7 worked but now iOS8 does not, that's a very sound argument to stand on.
I came late to the WiFi forums but the posts *I* saw said that iOS8 is the problem but clearly it's not, something on your phone was not fully tested with iOS8 that is causing a problem but iOS8 as a WHOLE works perfect, the upgrade with existing settings and firmware (you may have revealed a deeper problem that Apple is not prepared to admit) .
firmware is on wifi devices, and for devices to work firmware (which is an OS for hardware) and the OS for the entire phone must be in harmony. Alas this doesn't sound like it in your case.
This is a great starting point to discuss with Apple on what the next steps will be, It must be a very specific, limited problem. Not giving excuses for Apple, just saying it could be a manufacturing or parts issues, like maybe FoxCon slipped in some defective hardware that didn't manifest itself until iOS8 was introduced, I don't know.
Thanks for your reply, I can't offer any more solutions for you, it seems like you did a great job already, I can find no compelling reason to ignore your findings.