-
All replies
-
Helpful answers
-
Dec 20, 2014 10:07 AM in response to PNWmacby mac2050,I think PNWmac has it pegged.
Apple is throwing a few apps engineers at the problem but not the developers. They have decided it would just cost too much to really fix. We all need to think about plan B.
-
Dec 20, 2014 11:52 AM in response to tomstephens89by eyeane,I truly believe that Apple are very focused on this wifi issue, it is obviously a very difficult problem to fix, but they do have to be absolutely sure they fix it this time when they do release 10.10.2 It would be commercial suicide if they don't get it right, after one failed attempt 10.10.1 . Whilst very frustrated, I for one am supporting Apple and prepared to wait. Please just don't make to too long.
Apple is an extremely large organisation and reckon there is a fair size team trying to fix the issue/s.
I for one wish them a Happy Christmas, lets hope they have a nice Christmas present for us all.
-
Dec 20, 2014 12:06 PM in response to eyeaneby Pitiger,I am not sure which version of the 10.10.2 you are referring to but it has been released. I am not a developer or so. I am a plain user and noticed the update yesterday and installed it. It did not help at all. Besides this, yes Apple is probably working on the issue but it really does not make sense not to provide feedback. We do not what they think and if they indeed are trying to solve the problem. We even do not know what the problem is. Everybody is suffering a symptom and nobody knows what the source of the issue is. People get frustrated not only because they cannot connect to the Internet, but because they get no response from Apple. They feel like they are shouting but their voice is not heard. That can be more frustrating than having the problem itself. So there should be a channel Apple should be utilising to update their work on fixing the issue. Otherwise people will be wondering what to do. They do not know when to expect a solution. Two weeks? One month? Two months? When?!?!
-
Dec 20, 2014 2:22 PM in response to Pitigerby Drumwiz,Changing my DNS servers to Google's was a huge improvement, I'm running at around 90% I'd say but still get connection drops or slowdowns every now and then. Still unreliable.
Got a message from the Apple WiFi engineering team yesterday asking me to let them know if I don't get a seed invite by Monday morning. Yeah okay, I'll just be here struggling with a computer that can't connect, enjoy your weekend Engineering team.
-
Dec 20, 2014 2:37 PM in response to eyeaneby Florian Innocente,I don't know how much effort they put int resolving this issue but after several messages in this forum, I was contacted by the Wi-Fi Engineering team this week.
They asked me about diagnostic reports. I sent them 3 or 4 after my connexion dropped-off. I don't know if it will be useful, I haven't heard back, but at least they are apparently monitoring the issue and the discussions here.
-
Dec 20, 2014 4:47 PM in response to Florian Innocenteby hexdiy,but at least they are apparently monitoring the issue and the discussions here.
Monitoring discussions here will be marginal but existent. Monitoring the issue, yesss, big time, seeing all the invites to normal users here. Don' tell me nothing is being done. Defcon 3, I guess.
Well, I've got a spare MacBook Pro Core 2 Duo at their disposal right now (the first model to be Yosemite compatible, I think), so bring it on.
My production Macs wil stay on Snow Leopard 10.6.8 for the time being, no kidding.
-
Dec 21, 2014 4:26 AM in response to tomstephens89by Sean Dougherty2,I'd been having VERY slow internet speeds. Sometimes the connection would seem as if it dropped. What's strange is that running a speedtest (speedtest.com) showed a perfectly fine connection. I spent about two hours on the phone with Apple yesterday and after trying multiple solutions from re-installing the system to clearing wifi networks, nothing worked. Here's what is interesting: I'm primarily a Google Chrome user and so I'd been experiencing these issues when using Chrome. I tried using Safari and had none of these problems. The file that takes 20 - 30 minutes to download via Chrome takes about 25 seconds in Safari.
Have the people on this thread been having this issue across software?
-
Dec 21, 2014 4:37 AM in response to tomstephens89by bcoppinger,Still having Wifi problems in the latest seed. I separated my 2.4 and 5ghz networks to different SSIDs on my router. 2.4 works now, but 5Ghz displays same behavior since updating to Yosemite, which is an unusable Macbook. Hope this helps someone, its been frustrating to say the least.
-
Dec 21, 2014 5:55 AM in response to souko.vueby joeinoregon,I have been having frequent (every 30 seconds to a couple minutes at most) dropping of wifi on my Macbook Air with Yosemite since I installed it several months ago. My wife has Mavericks on her laptop and doesn't ever drop wifi. We're both connecting to the same network. I tried every possible fix and workaround I could find on the 118 pages of this thread, including flashing my router yesterday and updating the firmware.
Then I used this method on page 102:
*************************
souko.vueDec 1, 2014 1:42 AM
Re: OSX Yosemite Wifi issuesin response to tomstephens89
Here's another possible solution/workaround:
1. Option + click your wifi and click on Open Wireless Diagnostic
2. Press CMD + 4 to bring up Scan
3. Press Scan Now and it should provide you with the best channels for each 2.4/5Ghz band
4. Go to your router and change your channel
*************************
Apparently, my router was on Channel 6 along with 4 others in the neighborhood. I logged into the router via http://192.168.0.1 and changed the channel to 11, which was suggested as best channel in the left-hand side of the window from the wireless diagnostic scan tool.
I have no idea why the Mavericks laptop is perfectly fine with the router on channel 6 (as well as her iPhone with older iOS software), and my laptop with Yosemite and phone with iOS8 drops connection continuously, but since I've made the change to an unused wireless channel, I have not dropped the wifi signal once. I'm sure this won't help everyone as this problem seems to be multifaceted, but I'm pointing out souko.vue's post in hope that it might help some more of us.
-
Dec 21, 2014 8:08 AM in response to Sean Dougherty2by jndupuis1,I use Firefox as my browser. I have noticed your problem as well. I can't make Firefox my default over Safari because it screws things up. I have to keep Safari as my default browser. I ran into issues with on line banking as well. The bank recognizes Safari. Try to use Firefox. No go. Firefox has unusual download speeds, but, Safari is stable?
-
Dec 21, 2014 8:13 AM in response to bcoppingerby jndupuis1,Have you tried this? System Prefs>Network below connections click on gear, select Set Service Order then drag WIFI to top of list. Connect to your 5 GHz then restart. See if your WIFI connects upon desktop loading. Check stability of 5 GHz and see how that works out.
-
Dec 21, 2014 10:57 AM in response to tomstephens89by subigya,After spending my entire day off trying to patch wifi woes, i gave up. I'm back to Mavericks. I have been a proud Apple customer for a decade now but not anymore, this is the first time I've had an issue that has forced me to perform a clean installation. Horrible experience! sorry about the rant!
-
Dec 21, 2014 11:22 AM in response to tomstephens89by Bob7777,I downloaded Mario Ciabarra's tool described above in this thread. It seems to have done the trick for me. I haven't had any WiFi dropouts since then and I tried to induce them with powering up the iPhone near the MBP, plugging the phone into the MBP to do a backup, etc. Once the phone does its backup through iTunes there is lots of changed data which then needs to get backed up through Time Machine to my older Time Capsule. All of that is working OK. Could surf via Safari and Firefox throughout the process and aside from the usual very slow performance of iPhoto (IMHO its been slow since 2008) while it attempts to see if any pictures need to be pulled into the MBP from the iPhone the system has been performing as I would expect. Also, I am running 8.0.2 of Safari which is more recent than 10.10.1 but is GA software through the App Store, not beta. I've lived 60 years without Airdrop, so it would appear I can live a little longer without it. The same can not be said about WiFi. It seems like there are quite a number of different problems in this thread with differing severity, so this probably will not solve everyone's problem, but it might solve yours if you have a similar config to me. The simple act of dropping awdl0 which was posted way back didn't work, but Mario's tool must be doing more.
My config is:MacBook Pro (15-inch, Mid 2012)
Time Capsule 802.11n 2TB (the flat one, not the tower)
OSX 10.10.1 with Safari 8.0.2
Mario's tool is downloadable from this page: https://medium.com/@mariociabarra/wifriedx-in-depth-look-at-yosemite-wifi-and-aw dl-airdrop-41a93eb22e48I also changed Airdrop discoverability to No One, as suggested.
Thank you Mario. -
Dec 21, 2014 11:35 AM in response to tomstephens89by jndupuis1,I have a Mac Mini late 2012. To test my theory of this being a Unix, Intel Chipset Driver and Hardware Driver problem, I used Boot Camp when running Yosemite 10.10.1. I installed my Windows 7 Pro the Apple drivers installed (unattend ) just fine. My Mini ran beautifully!! No issues WIFI or otherwise under Windows. Has anyone tried to run their Windows 7 or 8 using Boot Camp in Yosemite 10.10.1 or .2 and acheived positive results like myself? I reverted back to Mavericks and using Boot Camp, put my Mac Mini with Mavericks and Windows 7 pro like nothing ever happened. I hope someone can confirm the same findings as I. Confirmation of this from a Mac Book Pro owner and a Mac Mini owner.
Sincerely, John Dupuis
-
Dec 21, 2014 1:52 PM in response to jndupuis1by hexdiy,@ John Dupuis: I've been following this thread from the beginning, and if I recall correctly, quite a few people have reported correct behaviour with Bootcamp Windows here. You may well be correct: some of the issues (in this here mixed bag of problems and complaints) will probably be reduced to BSD, Intel Chipset Driver and Hardware Driver combined.