I received my brand new, sexy MBA yesterday and was well aware of the wifi issue many people are experiencing at the moment.
My configuration: 13inch, i7, 8GB RAM, 256GB and Broadcom BCM43xx 1.0 (xxxx.35) driver.
I DID NOT experience any signal losses or drops while surfing normally on the web (2hrs facebook, google, nytimes, Apple Forums, etc. all work fine on Chrome and Safari). So standard websurfing is NO indicator for the problem! However, I did ping my router (50x) and the results were really frustrating (1ms to 1299ms, with occasionally timeouts) and I knew my MBA was also effected.
However, I am a noob and I don't give a s**t about the pings as long as everything I need works flawlessly. BUT it doesn't.
I tested Skype which I use on a daily basis, connected my old MacBook Pro with the router of our neighbour (lol) and the MBA with mine and let them video-call each other. The first try was okay (38 minutes). The second and third attempt weren't - both calls crashed after around 10min, but immediately reconnected.
So I decided to read through the last 30 pages of this awesome thread and extract the two methods I thought are the most promising ones:
1) the script from richard_vd on page 75 (but he posted "Hey, just noticed my posting on page 75 (technical details on MBA wifi latency jitter), is gone...!" on page 86, so I don't have any idea what the script is for!)
richard_vd - could you please repost the details, please?
Well, then I don't know why it doesn't work for you. It works for me!
But since you already know the IP of your router you may just as well use this simpler syntax:
sudo ping -i 0.2 -s 0 192.168.2.1 >/dev/null
(you should replace 192.168.2.1 by your router's IP)
2) The "roll-back to .22 while still enjoying the 1.0 update" solution from team headcase & orchetect on page 86
headcase Raleigh NC
Here you orchetect - good luck:
http://www.filedropper.com/io80211familykext
orchetect Vancouver, BC, Canada
zqx321 -
I did a hash check on both IO80211Family.kext packages (.22 and .35) and it turns out the only change is the internal AirPortBrcm4360.kext component (which is the 802.11ac driver specifically). So it's safe to replace the entire IO80211 package.
Here is exactly what I did to roll back:
- Get the .22 version of IO80211Family.kext ( here )
- Open /System/Library/Extensions in Finder and move the existingIO80211Family.kext to the trash
- Copy the new IO80211Family.kext into /System/Library/Extensions
- Quit all applications and save your data, as the next step will reboot your machine.
- Run Terminal and execute these commands in this order:
- sudo chmod -R 755 /System/Library/Extensions/IO80211Family.kext
- sudo chown -R root:wheel /System/Library/Extensions/IO80211Family.kext
- sudo touch /System/Library/Extensions/
- sudo reboot
xxxxxxxxxxxxx
So I first tried the easy method no.1 and ran the script in terminal. And SURPRISE it did work "somehow". Pings were between 1-3ms with odd 13ms every now and then (stddev around 0.5ms), but overall it seemed to be stable and good. But after a OSX restart the pings are going looney tunes again (2ms-120ms, stddev 40ms) on both routers (mine and my neighbour's). And I guess Skype will crash again.
So, before trying solution no.2 I want to clearify a fundamental question of my (and maybe many other's) situation:
Do I really want to do work-arounds and mess with software-hacks, if there is still the chance that the whole problem is hardware-based? Is it maybe smarter to return the machine?
I don't want to pay 2000USD+ (yeah, I live in Germany and Apple Stuff is way more expensive than in the states) for a machine, which has a fundamental problem. But I could temporarily live with it, if I knew that the issue can be solved on the software side. There were rumors a couple of days ago that the OSX 10.8.5. update is around the corner. Might that update be the solution everyone is waiting for?