Hacker News Reader

Comment by untog | Hacker News Reader

Here's hoping my Macbook will successfully reconnect to Wifi when waking up. I'm not optimistic, though.

Just do what I did. `brew install sleepwatcher` and then make a script at `~/.wakeup` to turn wifi off and back on again:

    networksetup -setairportpower en0 off
    networksetup -setairportpower en0 on

I finally did this after the El Capitan GM didn't fix my issue.

I will try this, thanks.

I'll have to give this a try. Thanks!

I made a quick little zsh alias for the wifi commands:

  wifi () {
  	local opt=$1
  	case "$opt" in
  		(on) networksetup -setairportpower en0 on ;;
  		(off) networksetup -setairportpower en0 off ;;
  		(toggle) networksetup -setairportpower en0 off
  			networksetup -setairportpower en0 on ;;
  		(scan) /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Resources/airport en0 scan ;;
  		("" | -h | --help) echo "Usage: wifi <option>"
  			echo "option:"
  			echo "\ton\tSet Airport adapter on"
  			echo "\toff\tSetAirport adapter off"
  			echo "\ttoggle\tTurns wifi off and then on again"
  			echo "\tscan\tList available wifi networks"
  			return 0 ;;
  	esac
  }

Note that this is only tested on my computer, ymmv, etc.

I'm so glad I use linux so I don't have to mess around with shell scripts to get my laptop working.

I remember using Linux on a laptop; <sarcasm>everything worked so well without any tweaking whatsoever.</sarcasm>

I'm just praying that my wifi doesn't start disconnecting again every 1 minute...seriously wifi is one of the most basic things to have in a laptop. Why is it so hard for Apple to get this right?

Here's to hoping Bluetooth on my Macbook won't stop working every time I put the computer to sleep. Then hanging the entire system when I try to toggle it off/on.

Oh man, I thought I was the only one. I've searched a bunch about this online but couldn't find anything. This mainly happens when I'm connected for an audio speaker. Weirdly, connecting it to my Bluetooth keyboard after the fact sometimes helps?

Oh man, the buggy Bluetooth stack in 10.10 is a huge source of frustration for me. At first I thought it was my peripherals, but they work without any trouble within EFI or Windows on the same hardware. I even tried poking at the stack using Bluetooth Explorer (part of Xcode), to no avail.

Well, to answer my own question - nope, still having problems with Bluetooth in 10.11. Normally, I wouldn't complain about something so basic, but it's really, really annoying when something that I use every day (like my BT mouse) only works sporadically in Mac OS X.

Edit: I've tried creating a new network location, resetting PRAM, resetting SMC, deleting Bluetooth PAN, re-installing the OS. Nothing seems to work reliably, and I don't know what else to try at this point.

Try this: http://osxdaily.com/2015/02/18/remove-bluetooth-pan-wi-fi-co...

You shouldn't be optimistic.

I own a number of different machines running the same software and one of these machines just has flaky wifi. Random disconnects or stalls during large downloads. No software update is going to fix that machine.

This happened to me. I just upgraded my router to a new Airport Extreme, and all those problems magically went away.

If you have a router that supports 2.4ghz and 5ghz networks, try using the 2.4ghz one and give each network its own SSID. That's what worked for me, but it's obviously a shot in the dark.

This. Create "MySSID 5" and "MySSID 2.4" (or however), and then rank the two in priority order, 5 over 2.4. Then the OS will prefer the (usually less crowded, but shorter range) 5GHz network and fall back as needed.

I used to have the two on the same SSID, but I found my adapters (or the OS) would gain an 'affinity' for 2.4 as the stronger signal and never use 5.

I have not rebooted my macbook (late 2012) running yosemite for 9 months. I always put the lid down after work and in the morning lift it up.

I never have any problems with performance, nor do I have issues with wifi.

I'm a full stack dev, so always running with a vm, sublime, irc app, chrome and terminal.

Everything just works fine for me.

Will be upgrading tomorrow. Like I did for Yosemite and Mavericks.

No problems with performance, no issues with Wifi...

... but probably significant security issues, given that you've missed 10.10.2 + 4 security combo updates.

And 10.10.3 + 1 security combo update.

And 10.10.4.

And 10.10.5.

(which isn't to be snarky, but more 'odd' that a confessed Day 1 Updater then doesn't touch system updates until the next major release).

Why did you have to phrase it like that? I don't feel it benefits discussion. It doesn't feel like the HN way.

If you had done an inquiry into the matter, linked to a stack exchange discussion on this bug persisting or being fixed that would've been a lot more useful. Maybe some technological quirks would surface that we could learn from. It's such a shame submissions like these, which the author clearly has spent a lot of time on, will get derided with snark like yours.

Now jkimmel continued in this vain; your comment has anchored the discussion in what i feel is a negative way.

Because it is frustrating to debug a closed system.

I am all for starting a stack exchange discussion when working on things that built communally and not locked down. However, when you are paying Apple for a product, it is frustrating to deal with things being broken and on top of that you have to circumvent their restrictions.

Because it is frustrating. Judging by my post getting positive votes as opposed to negative ones, it appears I am not alone in this. Incremental improvements to the Mail app are lovely, but I (and many others) do not use it. I use wi-fi all the time.

If you Google "macbook wake up wifi does not work" there are plenty of complaints, a couple of half-hearted solutions, but not much else. I didn't link to any of them because it isn't worth anyone's time to have to read them.

Yes, I am technically minded. As such, I could debug this further and further, but:

1) I can only go so far. This problem requires Apple to issue a fix, and they're definitely aware of it.

2) it's a little like asking a car mechanic to do some car repairs in his spare time for fun. My Macbook is a tool, I want it to just work.

Yeah, I totally get where you're coming from. I'm not asking for you to debug and fix the problem. I get that this is deep-seeded, and the ball is on Apple's court.

I just don't want HN to be a place of one-liners. In your original post you were complaining without adding any substance. Sorry if I sound harsh, it just really irks me. Maybe I should've left it at a down-vote, this back-and-forth is not particularly fruitful either.

I just don't want HN to be a place of one-liners. In your original post you were complaining without adding any substance.

I guess we can agree to disagree - I don't really know what useful substance I could provide. Plenty of people experience the same thing, and I don't think posts should be wordy just for the sake of not being one-liners.

Worked out though, with fogleman providing some good feedback!

Reply on news.ycombinator.com