Previous 1 81 82 83 84 85 Next 2,159 Replies Latest reply: Nov 21, 2015 7:04 AM by mirvine1 Go to original post Branched to a new discussion.
  • headcase Level 1 (15 points)

    Yeah, you're probably correct if the bug exists on both the OS X driver and the Windows 8 driver.  I guess I'll try nonetheless, just to see the results...

  • KaushikRay Level 1 (0 points)

    Thanks but i am testing a laptop (Dell 2011 i3 using Windows 7) which is nearly 2.5 years old and half the spec of my "advanced" laptop and gives 2-3 ms. This is my first Mac device and i am really heartbroken. I know nothing in the this world is perfect and am fairly patient but atleast hope Apple comes out with their thoughts on the issue and hope the brings us to their side.

  • headcase Level 1 (15 points)

    Based on a quick test of booting from the Recovery Partition of my 2013 MBA and then pinging my local router, it would appear the 1.0 software update from Apple is indeed causing the wireless latency issue.  When I ran a quick ping test, I was experiencing 2-3ms consistently vs. the 200+ms I have with the 1.0 software update for the 2013 MBAs.


    So... others are welcome to also test their own MBA by booting from their built-in Recovery Partition (restart your Mac and hold down the Command and R keys).  Then launch the Terminal application to try pinging your router or access point and see what your ping times are.


    The only thing I'm now debating, is whether to back up my personal files & restoring my MBA as new from the Recovery Partition, or wait until Apple releases another software update for the bugs in this Broadcom wifi chip.  As I wasn't expeiencing the wifi connectivity drops before the 2013 MBA 1.0 software update, I'm fine with rolling back to that driver for now.  Hmm... decisions, decisions. 


    Then again, I suspect someone will extract the older wireless driver from a MBP and provide a method to roll that back into an updated MBA, as others have done it before until Apple fixes the issue...

  • stumbleone Level 2 (290 points)

    I posted yesterday on this.  I restored my MBA to the earlier version of the Broadcom WiFi firmware (.22) from the 1.0 update version (.35) and my ping times went down to under 3 ms from 30+ ms.  For me that was the right thing to do but then my MBA has never exhibited any of the problems discussed here so it may not apply to other folks whose machines are not working properly.

  • KaushikRay Level 1 (0 points)

    is there any way to go back to the previous version ?

  • headcase Level 1 (15 points)

    I hear ya.  As someone else commented, I think the network engineers at Apple and Broadcom got a little overly aggressive in remedying the wifi connectivity issue with the newer .35 driver, and accidentally introduced this wifi latency issue. 


    As I work at Cisco and know how tempermental wireless networking can be (an understatement), I know how it can take a while for the network engineers to have a stable fix in place.  That said, I'm leaning towards rolling my Mac back to the .22 driver one way or another, for the time being.

  • KaushikRay Level 1 (0 points)

    I am new to Apple; can you please advice how i can go back to the previous version?

  • headcase Level 1 (15 points)

    If its a new MacBook Air, the easiest thing to do is boot from the Recovery Partition that is built into every MacBook Air now (by holding down the Command and R keys when restarting), and following the steps to restore your Mac as new.  Just make sure you back up any personal files you might have created on the Mac to a USB thumb drive or some other device first.

  • stumbleone Level 2 (290 points)

    Might also note the 10.8.5 OS update is probably imminent and who knows what kind of WiFi machinations they might have in there, including incorportorating the 1.0 update.  So if using the Recovery Partition method might want do apply now before the 10.8.5 rears its unknown head.


    To be fair, 10.8.5may  also have a more permanent fix but nobody knows at present.

  • headcase Level 1 (15 points)

    Yeah -- excellent point.  For someone who's been in the tech industry for too long, I usually hold off on installing the latest releases until I see how it impacts others... just wish I did the same for the 1.0 update.  Doh!

  • raducan.mihai Level 1 (0 points)

    Notice to all of you concerned about ping values: if they were ok before the update that is good news, because it means it is software related and an update can fix the issue.

  • Sabled Level 1 (0 points)

    Guys i have 0 issues with my new macbook air 2013. No drops no slow speed and if i ping i get:


    PING ( 56 data bytes

    64 bytes from icmp_seq=0 ttl=64 time=1.664 ms

    64 bytes from icmp_seq=1 ttl=64 time=1.757 ms

    64 bytes from icmp_seq=2 ttl=64 time=1.716 ms

    64 bytes from icmp_seq=3 ttl=64 time=3.207 ms

    64 bytes from icmp_seq=4 ttl=64 time=3.307 ms

    64 bytes from icmp_seq=5 ttl=64 time=3.118 ms

    64 bytes from icmp_seq=6 ttl=64 time=3.145 ms

    64 bytes from icmp_seq=7 ttl=64 time=3.202 ms

    64 bytes from icmp_seq=8 ttl=64 time=4.083 ms

    64 bytes from icmp_seq=9 ttl=64 time=3.258 ms

    64 bytes from icmp_seq=10 ttl=64 time=3.221 ms

    64 bytes from icmp_seq=11 ttl=64 time=3.140 ms

    64 bytes from icmp_seq=12 ttl=64 time=3.355 ms

    64 bytes from icmp_seq=13 ttl=64 time=3.096 ms

    64 bytes from icmp_seq=14 ttl=64 time=1.754 ms

    64 bytes from icmp_seq=15 ttl=64 time=3.357 ms

    64 bytes from icmp_seq=16 ttl=64 time=3.139 ms

    64 bytes from icmp_seq=17 ttl=64 time=2.254 ms

    64 bytes from icmp_seq=18 ttl=64 time=3.254 ms

    64 bytes from icmp_seq=19 ttl=64 time=3.213 ms

    64 bytes from icmp_seq=20 ttl=64 time=3.190 ms

    64 bytes from icmp_seq=21 ttl=64 time=3.219 ms

    64 bytes from icmp_seq=22 ttl=64 time=3.177 ms

    64 bytes from icmp_seq=23 ttl=64 time=3.382 ms

    64 bytes from icmp_seq=24 ttl=64 time=1.719 ms


    --- ping statistics ---

    25 packets transmitted, 25 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 1.664/2.917/4.083/0.655 ms


    I think that these nunbers are OK but i have installed 1.0 patch and i get about 40-80.000ms so i think the problem is patch. I have reinstalled OSX and now i get 0.500ms again.


    So, guys, what do u think, is my macbook air affected? I can return it and get full refund but I'm not sure if my macbook is OK or is affected with that issue.

    Please help me, don't know what to do, thanks!

  • andyman2 Level 1 (0 points)

    They're all effected.  Prior to 1.0 patch, people seem to be having random problems connecting to certain wireless routers.  After the 1.0 patch, the connection speed is erratic and unrelable.

  • KaushikRay Level 1 (0 points)

    I restored my OS-X and the timings has gone back to


    306 packets transmitted, 306 packets received, 0.0% packet loss

    round-trip min/avg/max/stddev = 1.480/3.387/23.638/1.867 ms



    So the update definitely made the pings erratic .

  • raducan.mihai Level 1 (0 points)

    @ Sabled: Can you test your connection on Skype and/or similar VoIP programs and tell me if you encounter any issues?

Previous 1 81 82 83 84 85 Next