Late 2013 Macbook Pro Retina 13'' Wifi Issues

I don't understand your answer... What does it have to do with my problems ?

It looks like you paid a lot of money for something which does not work as advertised. Since Apple has not done anything to solve it, depending on the country you live in, there are laws to enforce your rights. You can complain here in a forum where no Apple support ever reads anything (that I know from talking to them on the phone about this problem) or you take actions. Depends on if you are willing to accept this situation, because Apple told me that this is normal behaviour. Don’t expect them to do anything.

I'm not complaining about anything. I didn't see the specifications, I just expected to buy one of the best current laptops and not to have problems I didn't have with another laptop from Apple bought 4 years ago.

When you buy a new version of a product it's expected to receive at least the features of the old one. I'm comparing the new one with a MacbookPro of 2008... 4 years and less features ?

Besides I'm talking of 50-100 Mbps ... A very normal and popular speed connection (even 2 or 3 years ago)

What kind of answer is that ? :-P

Where I said 4 years I meant 6 years.

With my 2008 macbook I can connect to WiFi 802.11n and have 80Mbps... Why on earth couldn't I enjoy same features 6 years later ?

Definitely a software issue; I have followed someone's earlier suggestion for a botched temporary solution. This solution means that it is definitely something to do with sleeping/power-saving. I think that user input is tied to sleep of the wifi too - completely illogical as, during streaming at least, the user isn't always going to use the keyboard/touchpad.

Before using the internet, open Terminal and ping your router every 0.2 seconds. It prevents the wifi from sleeping.

However, there are still LOADS of random failed pings.

Rory, as i described I already used the 0.2 ping "solution" with no success.

It doesn’t matter if you have seen the specifications or not, but that is what the device should be able to, acording to their advertisment. Now see what numbers you get. Is that what you expected? Is that the „not to have problems”? If you are someone who is willing to pay a premium price for a speed which was popular a few years ago, a speed which is way below than the advertised 1300 MBit/s, then just stick with it. Again: either you are satisfied with that or you need to take actions, because just like I told you before, Apple will not solve this problem, no matter what people are posting here, that was a clear statement of them.

Do you have any antivirus installed? the "era" of a Mac-have-no-virus-attach must stop. MacOS PC can have the same attack as a Windows PC...

Again Marcel, I'm NOT expecting 1300MBits, 2500 or satellite connection , I'm JUST expecting the same features at least than the same serious laptop of 6 years ago.

P.D. I'm talking about 100Mbits, not 1300 , for God's sake !

Call AppleCare and ask for 100 MBit/s. But don’t be surprised to hear the same answer, that is what I am trying to tell you. So unless you find here someone who is willing and able to fix the current firmware/driver/OS you are out of luck with your expectations … ;-)

anjo108,

If you believe that's so, cite a case in which a Windows virus has caused any damage to OS X.

Clinton

anjo108 wrote:

Do you have any antivirus installed? the "era" of a Mac-have-no-virus-attach must stop. MacOS PC can have the same attack as a Windows PC...

That's simply not true.

There are no OS X viruses in the wild.

This usually gets us into a shoving match:

There are no OS X viruses in the wild.

But there IS Mac Malware, so you have to be cautious and not go clicking on links in emails and go downloading stuff from Torrent sites.

So-called "Virus protection" software is very intrusive, and provides no additional protection over what is already built into Mac OS X.

Grant Bennet-Alder wrote:

But there IS Mac Malware, so you have to be cautious and not go clicking on links in emails and go downloading stuff from Torrent sites.

Correct; the post I was responding to was specifically referring to anti-virus programs, which are unneeded on OS X (and would not protect you from malware anyway, as no third party software can protect you from yourself.)

This is not unlike the old joke that goes "This is a UNIX virus. Log into your system as the superuser and randomly delete files from your disk. Thank you." 😀

We need to keep one thread per issue.

I got involved in this thread because it was the only one that mentioned the following issue:

When the Late 2013 apple laptop (mine is a macbook pro 15" retina) running 10.9 (10.9.0, 10.9.1, and 10.9.2 so far) goes to sleep while connected to an 802.11n network (in my case a 5ghz wpa2 network on acisco linksys ea3500) and it wakes up in range of the same network, on wake up it'll behave as though it thinks it is connected to this same network, while being unable to successfully communicate. EG pinging the first hop (router) will time out. This lasts (for me) indefinitely until the aiport is turned off and turned on again, or another network is joined and the original network is rejoined. Other work arounds have been to use a USB or thunderbolt network adapter, either wifi or wired, to reset the router (which disconnects and reconnects as switching networks would), to restart the machine, or just run windows. This seems to be at best because Apple's broadcom drivers don't exactly work for all cases of networks. Limited success is found once-or-twice in resetting the SMC, deleting plists relating to the network location and zapping pram. The wireless networks on which the Late 2013 apple laptops exhibit this behavior, do not exhibit these failings to any other devices, mobile phones, tablets, nor other computers, and otherwise would never need resetting nor replacing nor upgrading, and given that the same hardware could run windows with no other change needed, the routers are not at fault.

Slowdowns, interference, channel hopping, frequency bands and selecting routers doesn't seem to be in the scope of possible contributing issues nor sollutions to the aforementioned. Work arounds involving not using the 10.9.x drivers for this broadcom chipset are, to some extent besides the point.

I'm naming this issue the stuck-wifi-on-wake issue.

Now something odd happened during my upgrade to 10.9.3 that has so far been resolving this issue, which is the only issue I can talk about having had. Let me update another post with that.