Retina Macbook Pro WiFi and Bluetooth issue

Exact same issue here. Additional my Wifi drops also when I am connected to my HDMI Monitor through Thunderbolt-Adapter.

1. Bluetooth: off; HDMI-Display: disconnected; 60mbits WLAN
2. Bluetooth: off; HDMI-Display: connected; 40mbits WLAN
3. Bluetooh: on; HDMI-Display: connected; 20mbits WLAN

Well.. thats not acceptable.

Is anyone experiencing these drops with a thunderbolt connected device?

Even, when my router was on a fixed canal, my Wifi was completely gone, after I plugged in my external monitor... at least, I have slow internet now...

MacBook Air, late 2013

Greets

I'm writing this 2 years after your post and discovered today after several weeks of frustration over slow WiFi that I also have the same problem on my late 2013 fully loaded 15" Retina MacBook Pro (1TB SSD, 16GB RAM etc). I have the Logitech Bluetooth sound adapter (square thing that looks like an Apple TV), so it appears Apple have still not fixed the problem. I also own an Apple Bluetooth Magic Mouse and am still trying to find out if it also effects the WiFi.

Wireless technology is a black art, and sadly Apple have never been that good at it despite their other pluses. My colleagues with PCs don't suffer these issues. I am always blown away/jealous how their YouTube videos start right away, whilst mine stall and stutter - even when connected to the same network. Am convinced it is because the aluminium case of Apple products interferes with/weakens WiFi signals and/or that Apple use the wrong WiFi chips in their gear.

For over 10 years, and I have owned about 10 PowerBooks/MacBooks, I have found the WiFi on each to be problematic, same with iPads, that are also metal based.

Not so my Android handsets and tablets that are plastic, or in the case of the Sony Tablet Z, it is glass.

Come on Tim, sort it out mate*!

*Buddy that side of the Atlantic! 🙂

Hi,

What worked for me was only enabling 802.11b/g on my router. When my MBPR connected to 802.11g the wlan connection worked fine along with my bluetooth devices; magic mouse and apple keyboard.

Of course not an optimal solution.... Apple needs to fix this

I have this same issue. On the latest publicly released version of OS X. MBP Retina 15". When I'm connected to my Bose SoundLink Mini while on WiFi, the Bluetooth connection makes the sound really odd and I'm losing 1/2 of the "broadcast". Instead if I use my iPhone 5S just next to the computer (on the same network and regardless of whether the computer is also connected to the WiFi), it works just fine.

😟

@Reitffunk

802.11ac with 80MHz bandwidth is 1300 MBit/s, which means the actual speed is 650 MBit/s.

650MBit x 1024 = 665.600 KBit x 1024 = 681.574.400 Bit / 8 = 85.196.800 Byte / 1024 = 83.200 KByte / 1024 = 81,25 MByte

So if Apple would really support 802.11ac as advertised by them, you should actually get up to 81,25 Megabyte per second. Just a hint for you guys ...

Well, I have resolved the issue, although at cost! Purchased Airport Time Capsule, connect MBPr on 5Mhz with BT mouse, all probs gone! Now I'm not saying go out and purchase this device to resolve issue as Apple obviously have probs with 2.4mhz and BT devices on MBP & MBA, but I wanted the backup device so killed 2 birds with one stone! ;-)

Since I wrote about the issue here I have talked to a 2nd line support rep. We did a few things incl. resetting PRAM, etc. and also deleted cache, start-up processes. Was quite a lot of things on mine because I move the full system from my older MacBook when I switched. So it runs faster now, which is good. Although, I've noticed, the issue is still there.

My best guess right now, and I think it goes along with what "logib" is saying, is that it has to do with the strength of the WiFi connection. If it fluctuates and is not strong enough, this issue seems to appear. I have thick walls both at home and at the office and the WiFi connection is not 100%. So I will make some changes to the location, buy an Airport Time Capsule and extend the WiFi use Airport Expresses set as repeaters/extenders.

I have had this exact problem on Pro Retina Machines 2 off Built 1 year appart. So can't be a batch issue with supplier parts like the Retina Screen problems. Good news is, the current Macbook Pro Retina using the 802.11 AC standard doesn't suffer from this problem. Apple have had long enough to fix this, There have been driver updates, I have tested this fault from 10.8.5 upto the current 10.9.2 Mavericks build.

It is consistently faulty on all versions of OS X. If it's a driver fault then apple are not fixing this. This is a design Issue with the Integrated wirelles/bluetooth ASIC it's a single chip handling both functions.

I have tested this with wireless hardware from many different manufacturers, including Enterprise class hardware and nothing makes any difference. Having proved the current MBP with 802.11AC wirless doesn't suffer the problem I am going back to the store with the 2 MBP's I have to blow the Genius's Mind and see If I can get them to swap out with the AC Models, if not going for a refund.

It simply isn't acceptible on a premium peice of hardware for apple to ignore these problems. Either fix the driver if it is a software glitch or recall and replace the wireless/bluetooth hardware for one that works.

These two standards can work together seemlesly, we should not have to put specific configurations onto wireless AP's to get any level of performance out of this combination. Public Hotspots?, we can't change their settings can we. These devices have such limited expansion ports that using a wireless dongle isn't an option when I am using every port when sitting at my desk, looks like the solution from apple is for us there customers to go out and buy more products to fix their problems or just not use bluetooth?

Exactly what I think!

But my MBA (late 2013) is also using 802.11AC and is actually suffering from this problem. The generation before also, I have tested it at a friends MBA.

HI Reitffunk,

Would be interested to know which Wireless AP's You have in your setup as I have only had the oportunity to test the new machine with a single AP (BT HUB) it is a 5GHz unit so it maybe the case that yours is a 2.4GHz Unit.

Jep, my Router (Hitron) is 2.4ghz. I have not the oportunity to test 5ghz.

I have the same issues but only noticed when using the bluetooth with my iPhone.

I have a MBPR 13'' and a Time Capsule 2nd gen.

These are the pings, starting with bluettooth off:

64 bytes from 192.168.0.1: icmp_seq=191 ttl=64 time=6.074 ms

64 bytes from 192.168.0.1: icmp_seq=192 ttl=64 time=4.092 ms

64 bytes from 192.168.0.1: icmp_seq=193 ttl=64 time=2.781 ms

64 bytes from 192.168.0.1: icmp_seq=194 ttl=64 time=11.214 ms

64 bytes from 192.168.0.1: icmp_seq=195 ttl=64 time=4.278 ms

64 bytes from 192.168.0.1: icmp_seq=196 ttl=64 time=9.911 ms

64 bytes from 192.168.0.1: icmp_seq=197 ttl=64 time=8.883 ms

64 bytes from 192.168.0.1: icmp_seq=198 ttl=64 time=1.945 ms

64 bytes from 192.168.0.1: icmp_seq=199 ttl=64 time=4.525 ms

64 bytes from 192.168.0.1: icmp_seq=200 ttl=64 time=6.645 ms

64 bytes from 192.168.0.1: icmp_seq=201 ttl=64 time=5.355 ms

64 bytes from 192.168.0.1: icmp_seq=202 ttl=64 time=1.846 ms

64 bytes from 192.168.0.1: icmp_seq=203 ttl=64 time=2.347 ms

64 bytes from 192.168.0.1: icmp_seq=204 ttl=64 time=1.861 ms

64 bytes from 192.168.0.1: icmp_seq=205 ttl=64 time=8.025 ms

64 bytes from 192.168.0.1: icmp_seq=206 ttl=64 time=1.610 ms

64 bytes from 192.168.0.1: icmp_seq=207 ttl=64 time=13.977 ms

64 bytes from 192.168.0.1: icmp_seq=208 ttl=64 time=1.886 ms

TURNED ON:

Request timeout for icmp_seq 210

Request timeout for icmp_seq 211

Request timeout for icmp_seq 212

64 bytes from 192.168.0.1: icmp_seq=209 ttl=64 time=4226.581 ms

64 bytes from 192.168.0.1: icmp_seq=210 ttl=64 time=3781.849 ms

Request timeout for icmp_seq 215

Request timeout for icmp_seq 216

64 bytes from 192.168.0.1: icmp_seq=211 ttl=64 time=6693.941 ms

Request timeout for icmp_seq 218

64 bytes from 192.168.0.1: icmp_seq=212 ttl=64 time=7156.087 ms

64 bytes from 192.168.0.1: icmp_seq=213 ttl=64 time=6570.162 ms

64 bytes from 192.168.0.1: icmp_seq=214 ttl=64 time=6218.885 ms

64 bytes from 192.168.0.1: icmp_seq=215 ttl=64 time=6590.468 ms

64 bytes from 192.168.0.1: icmp_seq=217 ttl=64 time=5131.870 ms

64 bytes from 192.168.0.1: icmp_seq=218 ttl=64 time=4385.010 ms

64 bytes from 192.168.0.1: icmp_seq=219 ttl=64 time=3475.738 ms

64 bytes from 192.168.0.1: icmp_seq=220 ttl=64 time=2547.355 ms

64 bytes from 192.168.0.1: icmp_seq=221 ttl=64 time=3357.110 ms

64 bytes from 192.168.0.1: icmp_seq=222 ttl=64 time=2854.540 ms

64 bytes from 192.168.0.1: icmp_seq=223 ttl=64 time=2291.333 ms

64 bytes from 192.168.0.1: icmp_seq=224 ttl=64 time=2383.404 ms

64 bytes from 192.168.0.1: icmp_seq=225 ttl=64 time=2800.225 ms

64 bytes from 192.168.0.1: icmp_seq=226 ttl=64 time=2158.479 ms

64 bytes from 192.168.0.1: icmp_seq=227 ttl=64 time=1580.256 ms

64 bytes from 192.168.0.1: icmp_seq=229 ttl=64 time=2064.874 ms

64 bytes from 192.168.0.1: icmp_seq=230 ttl=64 time=4443.228 ms

64 bytes from 192.168.0.1: icmp_seq=231 ttl=64 time=5500.466 ms

64 bytes from 192.168.0.1: icmp_seq=232 ttl=64 time=4566.887 ms

64 bytes from 192.168.0.1: icmp_seq=233 ttl=64 time=3628.656 ms

64 bytes from 192.168.0.1: icmp_seq=234 ttl=64 time=2628.834 ms

64 bytes from 192.168.0.1: icmp_seq=235 ttl=64 time=1659.183 ms

64 bytes from 192.168.0.1: icmp_seq=237 ttl=64 time=1.535 ms

64 bytes from 192.168.0.1: icmp_seq=238 ttl=64 time=23.115 ms

64 bytes from 192.168.0.1: icmp_seq=239 ttl=64 time=18.512 ms

64 bytes from 192.168.0.1: icmp_seq=240 ttl=64 time=992.461 ms

64 bytes from 192.168.0.1: icmp_seq=241 ttl=64 time=3757.997 ms

Request timeout for icmp_seq 246

64 bytes from 192.168.0.1: icmp_seq=242 ttl=64 time=5440.372 ms

64 bytes from 192.168.0.1: icmp_seq=243 ttl=64 time=5335.303 ms

64 bytes from 192.168.0.1: icmp_seq=244 ttl=64 time=5237.465 ms

64 bytes from 192.168.0.1: icmp_seq=245 ttl=64 time=4854.104 ms

64 bytes from 192.168.0.1: icmp_seq=246 ttl=64 time=4810.173 ms

64 bytes from 192.168.0.1: icmp_seq=247 ttl=64 time=4313.290 ms

64 bytes from 192.168.0.1: icmp_seq=248 ttl=64 time=3742.104 ms

64 bytes from 192.168.0.1: icmp_seq=249 ttl=64 time=3694.445 ms

64 bytes from 192.168.0.1: icmp_seq=250 ttl=64 time=3666.179 ms

64 bytes from 192.168.0.1: icmp_seq=251 ttl=64 time=3938.817 ms

64 bytes from 192.168.0.1: icmp_seq=252 ttl=64 time=3733.709 ms

64 bytes from 192.168.0.1: icmp_seq=253 ttl=64 time=3234.810 ms

64 bytes from 192.168.0.1: icmp_seq=254 ttl=64 time=2548.955 ms

64 bytes from 192.168.0.1: icmp_seq=255 ttl=64 time=2522.766 ms

64 bytes from 192.168.0.1: icmp_seq=256 ttl=64 time=1799.997 ms

64 bytes from 192.168.0.1: icmp_seq=257 ttl=64 time=1405.623 ms

64 bytes from 192.168.0.1: icmp_seq=258 ttl=64 time=865.899 ms

64 bytes from 192.168.0.1: icmp_seq=259 ttl=64 time=71.260 ms

TURNED OFF AGAIN:

64 bytes from 192.168.0.1: icmp_seq=260 ttl=64 time=4.474 ms

64 bytes from 192.168.0.1: icmp_seq=261 ttl=64 time=2.404 ms

64 bytes from 192.168.0.1: icmp_seq=262 ttl=64 time=5.575 ms

64 bytes from 192.168.0.1: icmp_seq=263 ttl=64 time=1.592 ms

64 bytes from 192.168.0.1: icmp_seq=264 ttl=64 time=4.158 ms

64 bytes from 192.168.0.1: icmp_seq=265 ttl=64 time=4.265 ms

64 bytes from 192.168.0.1: icmp_seq=266 ttl=64 time=1.790 ms

64 bytes from 192.168.0.1: icmp_seq=267 ttl=64 time=6.348 ms

64 bytes from 192.168.0.1: icmp_seq=268 ttl=64 time=5.359 ms

64 bytes from 192.168.0.1: icmp_seq=269 ttl=64 time=5.360 ms

64 bytes from 192.168.0.1: icmp_seq=270 ttl=64 time=4.717 ms

64 bytes from 192.168.0.1: icmp_seq=271 ttl=64 time=7.758 ms

64 bytes from 192.168.0.1: icmp_seq=272 ttl=64 time=1.464 ms

I decided to turn off the app that was using he bluetooth but it's not a viable solution.

Does anybody know if there's an update or something similar to the way they addressed this same issue with MacBook Airs?

Thank you!

The funny thing is, Apple doesn't care about this issue. They know, you can complain as much as you want, but next time you buy a notebook, you are gonna buy a Macbook Pro again.

I bet we will never see a fix fot this bug.

Hi,

I have resolved anything after I have read this post:

http://www.imore.com/how-fix-mavericks-wi-fi-zapping-bluetooth

Carmelo

I've also been noticing the same problem on my Early 2013 Macbook Pro. I've tried the technique described above, which involves removing the bluetooth prefrences file, but it didn't seem to work for me. Hopefully there will be a fix soon