Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

WiFi 10.10.2

C

ct1211

macrumors 6502
Original poster
May 3, 2012
321
51
Michigan
Some good news for me so far. I updated to 10.2.2 this morning and my intermittent WiFi issue may be fixed. I say this because i am getting instant lock on WiFi when I wake my computer. I had grown used to the little WiFi symbol doing a 20-30 second hunt since I first installed Yosemite. I hope all of you with these problems notice the fix.

P.S. If something else IS broken, please don't tell me. :D

P.S. P.S. Spoke too soon. A note just popped up telling me my Apple keyboard batteries are low. Yosemite update ate up my keyboard batteries! I know this because i just put in fresh ones last May and its only January. :eek:
 
ct1211 said:
Some good news for me so far. I updated to 10.2.2 this morning and my intermittent WiFi issue may be fixed. I say this because i am getting instant lock on WiFi when I wake my computer. I had grown used to the little WiFi symbol doing a 20-30 second hunt since I first installed Yosemite. I hope all of you with these problems notice the fix.

P.S. If something else IS broken, please don't tell me. :D

P.S. P.S. Spoke too soon. A note just popped up telling me my Apple keyboard batteries are low. Yosemite update ate up my keyboard batteries! I know this because i just put in fresh ones last May and its only January. :eek:
Click to expand...

Yosemite ate your keyboard battery? Had a bit to much to drink recently?
 
My H600 logitech headset stop working using the USB dongle.
The Bluetooth way work fine but then the microphone is not supported.

otherwise everything works
 
About 60% of our undergrads run MBPs, so I figure within 24 hours or so we should have some pretty definitive data on 10.10.2.

When 10.10 was first released out help lines where flooded with wifi issues. User stopped calling cause the got used to the complete lack or reliability.

10.10.1 - got some more calls, mostly of the "I thought this was going to fix my wifi issues" variety. Strangely it did also seem to cause some new odd reliability issues for some of our Ethernet users (many centered on DNS problems)

10.10.2 - I hope the ghost of SJ has been cracking the whip at Cupertino and expecting perfection from their SW folks.... this is getting old...

Me I'm holding off for 24 hours.
 
No WiFi issues so far with OS X 10.10.2 on my Quad-Core Mac Mini 2012.
But it's of course too early to judge.

It's as always a complete fresh installation without tools like WifriedX.
However I have disabled the aps and systemstats demons.

The additional development time seemingly has paid off. A lot of visual issues have been fixed. The system log also is less filled with absurd messages.
 
Seemed much better this morning but was only using it for 20-30 mins. Connected to wi-fi almost instantly though, much quicker than before. I only bought my first macbook pro in November and I'm loving it except this really annoying dropped wi-fi
 
crashoverride77 said:
Yosemite ate your keyboard battery? Had a bit to much to drink recently?
Click to expand...

Your humour detection feature is clearly broken.

----------
colorspace said:
About 60% of our undergrads run MBPs, so I figure within 24 hours or so we should have some pretty definitive data on 10.10.2.

When 10.10 was first released out help lines where flooded with wifi issues. User stopped calling cause the got used to the complete lack or reliability.

10.10.1 - got some more calls, mostly of the "I thought this was going to fix my wifi issues" variety. Strangely it did also seem to cause some new odd reliability issues for some of our Ethernet users (many centered on DNS problems)

10.10.2 - I hope the ghost of SJ has been cracking the whip at Cupertino and expecting perfection from their SW folks.... this is getting old...

Me I'm holding off for 24 hours.
Click to expand...

Surely a better approach would be to advise THEM to hold off while YOU test? Even if the devices aren't yours that would be a better way to approach it?
 
simonsi said:
Your humour detection feature is clearly broken.

----------



Surely a better approach would be to advise THEM to hold off while YOU test? Even if the devices aren't yours that would be a better way to approach it?
Click to expand...

Reality detection is clearly broken ;-)

Most of the folks itchy to apply the latest software are usually our undergrads especially those of the freshman/first year variety (aka teenagers) -- we advise them to do a lot of thing....
 
colorspace said:
Reality detection is clearly broken ;-)

Most of the folks itchy to apply the latest software are usually our undergrads especially those of the freshman/first year variety (aka teenagers) -- we advise them to do a lot of thing....
Click to expand...

Oh I understand that (I run an ISP network with 60,000 customers), but if even 10% delay it reduces the calls you take....giving you more time.
 
I got 24 hours

before WiFi got squirrely again. Patiently waiting to see windows 10 on some of the sleek Ultrabooks due this spring or fall.
 
Wifi performance still broken. Pinging a 2012 rMBP from my Pro..

~>ping kosame.lan
PING kosame.lan (192.168.42.4): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.42.4: icmp_seq=0 ttl=64 time=2331.795 ms
64 bytes from 192.168.42.4: icmp_seq=1 ttl=64 time=1329.135 ms
64 bytes from 192.168.42.4: icmp_seq=2 ttl=64 time=326.928 ms
64 bytes from 192.168.42.4: icmp_seq=3 ttl=64 time=2295.045 ms
64 bytes from 192.168.42.4: icmp_seq=4 ttl=64 time=1294.769 ms
64 bytes from 192.168.42.4: icmp_seq=5 ttl=64 time=294.357 ms
64 bytes from 192.168.42.4: icmp_seq=6 ttl=64 time=2362.131 ms
64 bytes from 192.168.42.4: icmp_seq=7 ttl=64 time=1361.692 ms
64 bytes from 192.168.42.4: icmp_seq=8 ttl=64 time=361.643 ms
64 bytes from 192.168.42.4: icmp_seq=9 ttl=64 time=2325.253 ms
64 bytes from 192.168.42.4: icmp_seq=10 ttl=64 time=1325.353 ms
64 bytes from 192.168.42.4: icmp_seq=11 ttl=64 time=324.845 ms
64 bytes from 192.168.42.4: icmp_seq=12 ttl=64 time=1084.431 ms
64 bytes from 192.168.42.4: icmp_seq=13 ttl=64 time=80.911 ms

it gets marginally better if I start it pinging back:

64 bytes from 192.168.42.4: icmp_seq=31 ttl=64 time=403.572 ms
64 bytes from 192.168.42.4: icmp_seq=32 ttl=64 time=403.086 ms
64 bytes from 192.168.42.4: icmp_seq=33 ttl=64 time=400.011 ms
64 bytes from 192.168.42.4: icmp_seq=34 ttl=64 time=399.992 ms
64 bytes from 192.168.42.4: icmp_seq=35 ttl=64 time=396.002 ms

.. and same problems also occur if I use the laptop, lots of delay in some interactive shells etc. I am seriously considering 10.9 downgrade now, although luckily I use my laptop mostly just when my Mac Pro is undergoing repairs.. and it will be again, soon, stupid problem child machine #2.
 
How about transmit speed.

On 5ghz to Airport Extreme my TX speed drops from 848Mbps to 195Mbps within a few seconds. I think it does this when bluetooth is enabled but i can't turn this off on my iMac.

Before Yosemite, it connected between 800-1000Mbps, same computer, same location and kept that solid high speed link.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back