-
All replies
-
Helpful answers
-
May 16, 2014 9:35 AM in response to bpkaby Steve Wilkinson,I think they have, they just never seem to really get to the root of the problem. They just keep fixing it for some sub-set of users, and then another sub-set has the problem. I had the problem years ago on and off with various OSX point revisions on a number of laptops (back in the 2005-2007 time-frame). When I got my new 2013 MBA, it had the problem out of the box, as soon as I added a BT Apple Mouse (I used it for a month or so before adding the mouse with zero problems). The problem went away again after one of the Mavericks updates. I'm currently on 10.9.2, so we'll see what happens when I go to 10.9.3 now.
-
May 16, 2014 12:01 PM in response to seb101by remihio,I solve the same problem by doing the steps in this link.
http://www.imore.com/how-fix-mavericks-wi-fi-zapping-bluetooth
-
May 16, 2014 1:07 PM in response to seb101by Setsuna666,Since this issue was driving me crazy (I use bluetooth alot, with a mouse and headset), I tried to find a fix for it. While it is a hack and in no way official, I think I managed to make one.
I didn't test it extensively, so it might not work perfectly, but from what I tested so far, it seems to fix the issue.
What my solution does, is disable bluetooth before the computer goes to sleep and re-enable it after 5 seconds from waking up from suspend, which give enough time for the wifi to connect without issue.
1. Download Sleepwatcher 2.2 from its website to you website, to your desktop and then run the following commands in a terminal: http://www.bernhard-baehr.de/
$ cd ~/Desktop/
$ sudo mkdir -p /usr/local/sbin /usr/local/share/man/man8
$ sudo cp ~/Desktop/sleepwatcher_2.2/sleepwatcher /usr/local/sbin
$ sudo cp ~/Desktop/sleepwatcher_2.2/sleepwatcher.8 /usr/local/share/man/man8
$ sudo cp ~/Desktop/sleepwatcher_2.2/config/de.bernhard-baehr.sleepwatcher-20compatibilit y.plist /Library/LaunchDaemons/
$ launchctl load /Library/LaunchAgents/de.bernhard-baehr.sleepwatcher-20compatibility.plist
2. Download Blueutil from its website and install it: http://www.frederikseiffert.de/blueutil/
3. Create the 2 sleepwatcher scripts, in the terminal type the following commands and copy this content:
$ vi /etc/rc.sleep
#BEGINING OF /etc/rc.sleep. DO NOT COPY THIS LINE#!/bin/bash
/usr/local/bin/blueutil off
exit 0
#END OF /etc/rc.sleep. DO NOT COPY THIS LINE
$ vi /etc/rc.wakeup
#BEGINING OF /etc/rc.wakeup. DO NOT COPY THIS LINE
#!/bin/bash
$(sleep 5 && /usr/local/bin/blueutil on) &
exit 0
#END OF /etc/rc.wakeup. DO NOT COPY THIS LINE
4. From the terminal, change the permission of the 2 scripts
$ sudo chmod a+x /etc/rc.sleep
$ sudo chmod a+x /etc/rc.wakeup
5. Now, try to suspend and resume your laptop and everything should work correctly
-
May 16, 2014 1:48 PM in response to Setsuna666by mikkelnl,Wow, thanks. This is working so far! Awesome, thanks for sharing.
For future reference: for step 3, you'll need root access in terminal, do this by typing:
sudo -s
-
May 16, 2014 1:59 PM in response to mikkelnlby Setsuna666,Oh, yeah sorry! Forgot to put sudo before the vi command. Thanks!
-
May 16, 2014 5:47 PM in response to Setsuna666by Setsuna666,Just made an installation script for the fix.
It can be downloaded here: https://github.com/Setsuna666/osx-wifibtfix/archive/v1.0.1.zip
The source code is available on github: https://github.com/Setsuna666/osx-wifibtfix
-
May 16, 2014 8:37 PM in response to Setsuna666by antzcrashing,Setsuna, this seems great. Can you also create a separate thread for this fix, and link it from here. That way we keep all responses to it together. I am hesitant to try because it adds significant software, does it also include an uninstall option if there are issues? How many have had success with it? Anyone cannot get it to work with the installer?
-
May 16, 2014 9:33 PM in response to antzcrashingby Setsuna666,Yeah, sure will look into creating a thread for this specifically. For the initial release, I didn't include any uninstall function to the script, but will definitely add one soon.
The 2 softwares included are the following:
- Blueutil - Allow bluetooth to be controlled from command line
- SleepWatcher - A daemon that monitor when the system goes to sleep and resume from it. Then, run script depending on the state
There is little risk from try it, and removing it is quite easy.
Here are the uninstall steps:
1. Uninstall blueutil by deleting the binary from /usr/local/bin/
$ sudo rm /usr/local/bin/blueutil
2. Remove SleepWatcher, binary, scripts and documentation
$ sudo rm /usr/local/sbin/sleepwatcher
$ sudo rm /usr/local/share/man/man8/sleepwatcher.8
$ sudo rm /etc/rc.sleep
$ sudo rm /etc/rc.wakeup
$ sudo rm /Library/LaunchDaemons/de.bernhard-baehr.sleepwatcher-20compatibility.plist
Nothing get changed on the system, only added, so removing it is as simple as deleting the files that have been added by the install script.
Hope this helps.
-
May 16, 2014 9:45 PM in response to Setsuna666by Setsuna666,Just added an uninstall script in the latest release: https://github.com/Setsuna666/osx-wifibtfix/archive/v1.0.2.zip
-
May 16, 2014 9:53 PM in response to Setsuna666by Setsuna666,Just created a post specifically for my script: https://discussions.apple.com/thread/6227237
-
May 17, 2014 4:17 PM in response to bpkaby egolnik,bpka,
It would appear there may be multiple causes for this problem. The Bluetooth fix did not solve the problem for me. (I don't use Bluetooth at all) For me, the only solution that has worked consistently is to turn off ipv6 over wifi
[ In terminal: networksetup -setv6off wi-fi ]
( To undo: just turn ipv6 back on in System Preferemces/Network/WiFi.Advanced/TCPIP/ipv6 )
This is the only solution that has worked for me and since I do not need ipv6 support there is no downside for me.
-
May 18, 2014 9:53 AM in response to Steve Wilkinsonby Steve Wilkinson,Supposedly, 10.9.3 has fixed the issue regarding bluetooth and wifi. Mine has been OK for some time, but I'm curious if this is the case for others.
-
May 18, 2014 9:56 AM in response to Steve Wilkinsonby Setsuna666,I'm still having the issue even after upgrading to 10.9.3, that is why I am trying to maka a fix.
-
May 18, 2014 10:05 AM in response to Setsuna666by Steve Wilkinson,Nuts, sorry to hear that. I sure hope Apple takes this seriously some day and gets to the root of it. Sounds like a neat work-around you've made though.
-
May 18, 2014 10:30 AM in response to Mike Erstadby olivierventurini,It works for me. Thanks.
but worrying now that you said it is only a temporary fix