Brand new rMBP 13" Wifi Problems

Question

Level 1

0 points

Brand new rMBP 13" Wifi Problems

I've just set up my newly arrived rMBP, and migrated my prior computer (late 2010 MBA) to it from a Time Machine backupd. I made sure to update the Yosemite version on each first. I had not been having Bluetooth-wifi issues on the MBA since a couple of OS X upgrades back, although I had experienced some of those problems previously. I now find that the MBP is having a slow-wifi issue. If I disable bluetooth, it functions fine. Otherwise, wifi speed slows to a crawl. What can I do? Might I have caused this problem by not doing a clean install?

MacBook Pro (Retina, 13-inch,Early 2015), OS X Yosemite (10.10.2)

Posted on Mar 25, 2015 12:56 PM

Reply

Answer 1

dominic23

Level 10

83,916 points

Mar 25, 2015 1:37 PM in response to gshall

A new Mac comes with 90 days of free tech support from AppleCare.

AppleCare: 1-800-275-2273

Best.

Reply

Answer 2

gshall Author

Level 1

0 points

Mar 27, 2015 5:35 PM in response to gshall

After myriad tests, I called Apple Support. Following the initial conversation, I had a useful, engaging, educational session with a senior adviser, who took hours with me, while we tried all different things. No success. I live 100 miles and a ferry ride from the nearest Apple store, so none of my options going forward were attractive.

Finally, after we had signed off, I thought of one thing we hadn't tried to isolated during all this work. The Magic Mouse itself (old). It was the mouse. It was the doggone mouse! Mouse and bluetooth on, malfunction. Mouse and bluetooth off, great function. Mouse off, bluetooth running (I made sure to be running my bluetooth speaker, too) -- EUREKA!!! Wi-fi speed was fine.

Moral of the story: test all hardware first.

The mouse is broken. I just ordered a new one.

Reply

Answer 3

gshall Author

Level 1

0 points

Jul 21, 2015 10:49 PM in response to gshall

I was mistaken. The mouse was not broken. There still was an issue. The next Yosemite update solved the problem, but then it recently returned, and the succeeding update has not fixed it.

Reply