Yes, that's correct. I just used Safari as an example. Thanks for the confirmation (@TP18 as well!).
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Fourth OS X 10.10.3 Yosemite Beta to Developers, Public Beta Testers
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yes, that's correct. I just used Safari as an example. Thanks for the confirmation (@TP18 as well!).
and what does that thermal check even mean?
Anyway it's like they fix one thing and break two other things, beta or no beta. A constant merry go round with Apple....
I was happy to see that Finder opened from the Dock again, but looks like bigger problems behind the scenes was everytime I open Finder I get a spinning beachball within 1-2 minutes and need to reboot
Will try resetting the plist from earlier in the thread, but not impressed from the first 30 minutes use. How some people can run these betas on their only Mac is beyond me...
Will try resetting the plist from earlier in the thread, but not impressed from the first 30 minutes use. How some people can run these betas on their only Mac is beyond me...
This isn't OS X. For me the duet display app was causing it. I told that app not to launch on start up and the issue went away. The transparency turns off the moment that app is launched.
and what does that thermal check even mean?
This is all I could find:
OSThermalNotification.c
The hostname/rename problem still exists, specifically renaming hostname after sleep to hostname (2), etc etc. I have found turning off "Wake for network access" is the work around, after reenabling with 10.10.3 Beta 4, first time it slept, hostname changed to hostname (2).
Thank you. It sucks to be affected by crippling bugs (like WiFi issues), but some people don't understand that not everybody experiences the same bugs they do. Even among WiFi issues alone, there are probably several different things that cause connectivity issues depending on your exact configuration of hardware.
And before people try to pull the whole "but Windows" card, OS X is trying to do significantly more than Windows in the realm of wireless connectivity. Handoff and Continuity aren't nearly as simple as Apple wants to make it seem like.
Thanks but this isn't an excuse for breaking basic stuff like wifi. Windows/Linux don't have the luxury of known hardware. Apples does. So it's job should be easier.
As a technology engineer I can tell you that good design means doing fancy stuff like handover/continuity should not impact the underlying transport mechanism - if it does it's a really hacky bad design. It shouldn't matter if I run walk skip hop jump on the pavement - the pavement shouldn't break.
For anyone who says this is a minority issue .. just google it... it's huge but the Apple PR machines keeps it out of the limelight. Apple stores and resellers tell me too there's nothing they can do and that they do indeed get loads of complaints - not isolated incidents.
http://www.pcworld.com/article/2836812/complaints-mount-about-yosemite-crippling-wifi.html
Me personally - the issues are with all the Macs... macbook pro 15 and imac both latest models (pre newest 2015 announcements).
Mavericks had no wifi issues.
To the person who suggested kext replacement - thanks but that's a serious hack. Not a solution for most users. I'm glad it works for you but for me I shouldn't have to, and don't want to risk breaking software coherence by hacking the kernel module.
I don't disagree with anything you said, even if I don't view it quite as harshly as you do. More specifically, I agree that if Continuity and Handoff are indeed the culprits, there's something flawed about the execution of those features.
And I am aware that WiFi issues are the cause of many complaints, but we don't know if it's the exact same underlying cause for every person affected. I can't imagine the issues would have been unresolved for this long if it were a simple fix. Doesn't excuse the fact that it's happening in the first place, but I highly doubt that Apple is twiddling its thumbs instead of trying to figure out what's going on.
Can't do a Look Up anymore without disabling my keyboard. Can't make phone calls from my Mac anymore. But Faces works better in Photos. I'd rather roll back to the last beta, thanks anyway.
Doesn't work for me either, is iPhone cellular calls actually working for anyone with this build?
Last edited:
I was happy to see that Finder opened from the Dock again, but looks like bigger problems behind the scenes was everytime I open Finder I get a spinning beachball within 1-2 minutes and need to reboot
Will try resetting the plist from earlier in the thread, but not impressed from the first 30 minutes use. How some people can run these betas on their only Mac is beyond me...
Working fine on my iMac late 2012
Yes, yes and yes... been tearing my hair today trying to figure this one out. A temporary fix is to create a test user and then sign into iCloud and FaceTime... This seems to enable iPhone cellular calls. You then log out and log back into your normal admin account. However, it then doubles up the listings of devices on iOS8 Messages settings... So... You go round in circles trying to fix one, but breaking the other.
I wasn't using Photos until today because I didn't choose to import my iPhoto library when it installed, and then couldn't find an option to import it later.
Well, I just did: option-click while clicking the Photos icon, and it asks you to import an iPhotos library. Hallelujah! Now I can start playing with Photos.
Lookup is still a blank space for me after this seed.
I'm surprised this build made the cut for the Public Beta due to the incomplete implementation of the new Look Up feature. It's completely unusable for me in this build and even has the potential to make the keyboard completely unusable until after a log out.
I'm fine with it though, since it means the Public Beta has a chance to try some of the same somewhat buggy builds that developers do. However, I will have to live without the convenient Look Up feature on my secondary machine until the next build.
Last edited:
Can you give us more details as how to do this? I don't see where to rename the storyboard.
Really, googling tells you its huge... Oh my.... You mean you found millions of people with this issue online and they somehow kept this under wrap? That's what it would mean if it was huge. I don't think so, not even Apple has that kind of money conspiracy buff.
Apple devices now interact with more/more diverse network devices than Microsoft (more devices shipped). Many of those devices are out of spec from manufacture, drifted out of spec with age, badly designed or badly configured.
Continuity/handoff deals with routing, peer to peer communication, session, protocol handover, out of band signaling, etc. A real hodge podge of modifications up and down the stack and even outside it.
So, they to change the existing codebase. It is even possible that they took this opportunity to rewrite whole of it to better use the existing hardware. The hardware underneath changes continuously.
BTW, I lose all Ethernet (something that worked reliably on every other version of Windows) connection every 1-2 days on my windows 8.1 machine (needs a reboot to make it work again) for the last 16 months (filed a bug) and MS has not issued a fix yet; guess I should whine about it... That's a severe bug on old equipment that hasn't changed in 5 years.
Yes, they should fix bugs. But, lets not go overboard about the recriminations and Apple suddenly being all lackadaisical about resolving issues. The problem is mainly that there are a lot more feature changes in the last 5 years than ever before (a good thing). Development cycles have shortened and sometimes external deadlines (hardware release of IOS devices especially) mean software is released too early.
The solution to that is restricting the number of hardware linked features in one upgrade cycle, so public betas can be done before the software's official release. Apple seemingly has instituted that in both OSX and IOS, so they are aware of the problem.
Still, the current situation is better than in the past were despite less pressures and feature upgrades, software still got released with bugs!! Bugs that took several years to fix. You can look in the archive to confirm this.
Last edited: