Timeline for Wi-Fi keeps going down on MBP 2015
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2015 at 20:06 | comment | added | Arnas | Well, it seems that it fixed the problem. Thanks for the help anyways! | |
| Jul 16, 2015 at 3:49 | history | edited | Ruskes | CC BY-SA 3.0 |
added 5 characters in body
|
| Jul 15, 2015 at 23:28 | comment | added | Ruskes | Nice, so you did had a network profile problem, I thought you deleted it already once. But it seems to work now :) | |
| Jul 15, 2015 at 23:06 | comment | added | Arnas | Whoa, I tried this neat trick: pastebin.com/uq1P2taM and here're the results: pastebin.com/tJ7T71Tw I've been browsing the net the whole time, watching youtube videos etc., and I had only a few time outs. I'll use my mac for a little bit more and I'll report the results tomorrow. | |
| Jul 15, 2015 at 22:52 | comment | added | Arnas | Here are the results: pastebin.com/VN65P7c2 The first timeout was after I visited Facebook for like 2secs and then clicked on a youtube link. A browser opened the youtube link and when the video started loading the wi-fi timed out. After that I closed the browser and did absolutely nothing, but as you can see there are a few more time outs anyway. | |
| Jul 15, 2015 at 22:46 | comment | added | Ruskes | OK, lets do a endurance test. Open a application called Terminal (in your Application/Utility folder). Now copy the following or type "ping 8.8.8.8" and press Enter and let it run for 3-5 minutes. Observe the time reported. What you are doing is sending a small file to google and getting a respond indicated in time displayed. The time should remain approximately constant and below 200. After you are done watching and to stop it press "ctrl+C" | |
| Jul 15, 2015 at 22:19 | comment | added | Arnas | Did everything exactly as you said. After browsing for like 1min, I tried to play a video on youtube and it kept loading. Then I tried to go to google.com and it couldn't load it either. Everything started working again after like ~30secs or so. | |
| Jul 15, 2015 at 22:07 | history | answered | Ruskes | CC BY-SA 3.0 |