Q: mac osx 10.9 Mavericks wifi issue

I sure hope it's just a software issue as you say, but the only thing that helped was disabling bluetooth. That says signal interfence to me yeah? Nothing else I've done changes anything.

Just adding myself to this list. I have several friends with MacBook Air 11, 13 and other Mac users that all have this problem. It does somewhat depend on location/router, sometimes it connects fairly fast, but depending on the router brand/model it just doesn't connect until it timesout, then you click the wifi AP you want, and it connects. It definitely starts after the user upgrades to Maverick. I turned off bluetooth and it seems ok, but sure hoping @pple offers a fix as this is totally unacceptible.

I thought one benefit of Apple hardware was fantastic reliablity and support, not bugs they still can't fix or understand even though they only support such a tiny amount of total wifi adapters/OS<--->hardware performance compared to say.....what Windows has to deal with???!!!

Totally agree. Absolutely the same issue and behavior here on my MBP 13 Retina, Late 2012. This has started after the upgrade to Mavericks and lasts since the 10.9.1 update. And as it was working well using 10.8 I am sure this is a software problem.

What somehow really annoys me that it seems to be a common problem with Mavericks but looks like Apple is just ignoring that or has anybody here received acceptance of this issue by them already?

For those who beleive it is a bluetooth hardward problem remember that the one and only common denominator is the upgrade to Mavs/Mavs factory install. No problems on any other OS X and all routers are having problems.  Only some people get resolution by turing off bluetooth. Others do a PRAM reset and there are a few other fixes that some are lucky to have worked.  Mine hangs on the dreaded ! sign in the signal icon when rebooting or coming out of a long sleep but so far it always connects. I do know it never happens on a short sleep and it does not matter it I am connected to the charger or not. I still say it's the power manager but whatever it is they really yuked it up as it is 4 months old and keeps on going. And they are selling new products that have the problem installed.  I have seen other threads that Mavs have casued problems and again the one common thread is upgrading to Mavs. I think Apple droppled the Apple bad and if Jobs was alive he would be livid and he would be standing out their apologizing.

It really is kind of sad how the vision and quality of their products has begun to diminish just because Jobs passed away.

I may have found the explanation for this issue, at least on my box.

I upgraded from an up-to-date 10.8 to Mavericks, the auto connection never worked for me (MBP Retina 15" Early 2013).

Tried reset the PRAM and SMC, didn't work.

But I noticed that the preferred networks list (under Network Preferences, Advanced, Wifi tab) was empy. it shouldn't be, I had a lot of network configured.

Deleting the wifi authentication entry in the keychain and recreating the wifi connection made the job. I guess that clicking on "+", and then in "Select network" would have done it as well.

Hope this helps

What brought the cure in the case of my two late-2012 Macbook Pro Retinas was first following kemplar's advice of deleting all locations and adapters (including VPNs) in Network Preferences. This alone did not help though. Before reinstalling the adapters (I did not set up any custom locations anymore), I ran Disk Utility and repaired permissions. After that, I first rebooted, then reinstalled adapters, and have had no more of the intermittent wifi dropouts I encountered on both machines in intervals of 10 minutes on average since.

After the Mavericks update, the Wifi connection would just stop silently every 5-30 minutes, without any sign or message, the Wifi symbol still showing full bars. To reactivate Wifi I would either have to switch Wifi off and on again or run a Network Diagnostics.

The above fix has now proven stable for many times longer than the usual dropout intervals.

Hi,

I wrote an app to fix this Wifi issue on Mavericks: gum.co/PingFixer

Kevin

@kgc327 If you put the source on Github for me to see then I'll consider handing you $5 for the app, but until then I'm a little paranoid. Even your "support" twitter account is brand new with no history. I have no idea who you are or what lives inside your app. Also, even if it's legit I have no idea if your app will actually fix my issue; it'd be a shame to spend the money and not have it work.

I see no reason for you to hide the source. Only a select few of us with the problem would be able to compile the app and install it for free. Even then, someone like myself would gladly give you $5 to package up a nice little fix into an easy to install app as long as I knew EXACTLY what it was doing. If it was a full product you were selling I'd be less concerned but you're bascially charging us all $5 to install a user-created bug fix. I'm not even sure Apple would be cool with that.

I'm a little reluctant to put the source online, but I could do that...

Anyways, more about me: http://kevinchiu.org/

I've also added a 100% money back refund policy if it doesn't work for people.

I appreciate the fix if it's legit, but reluctance to put the source up for such a tiny app that does one tiny task and costs five dollars only makes me more paranoid.

A guarantee doesn't really reassure me.

Well, if the following works for you, the app will work too:

1. Find your router IP.

2. Ping it every .2 seconds.

The app is also sandboxed using Apple's app sandbox, in case you're worried about security.

Kevin

I'll give the ping fix a shot to see if that even fixes the issue. Still doesn't mean that it's not doing something else I'm not aware of in addition to keeping the wifi card alive. The app sandbox is great, but all I have is your word lol.

Moot point anyway. Ping did not fix anything.

i posted about the ping "workaround" https://discussions.apple.com/message/24119041#24119041 on 2014-JAN-10. This workaround works nicely for me. The key point is the ping needs to be continuous (every 15 seconds in my case).