Apple Seeds Second OS X 10.10.2 Yosemite Beta to Developers

[SmOgER]

FINALLY they improved font rendering in dark mode as well!
It's still not as good as with white theme, but it's much better than it was. I can already actually start using it rather than turning it off after 5min of trying to get used to ugly rendering.

EDIT: right click + cmd on 'trash' --> still not fixed

 

[JetLaw]

Has anyone tried this build with Vox? I confirmed an issue with the previous build but would like to know if this one works before moving back away from 10.10.1.

Thanks!

 

[ItWasNotMe]

Don't have the same coding resources as MS i think. Besides the culture at MS is different (patch Tuesday).

Apple has a Tuesday culture as well as in "It Just Works (but only on the fifth Tuesday in February)"

 

[Fuzzi]

The Chrome crash has nothing to do with problems within Yosemite, it has to do with the Chrome team failing to check it on Yosemite. APIs were deprecated. If this latest release fixes the problem for you, then either you were updated to a newer version of Chrome or the deprecated APIs were restored. Do you know?

This is not true, it was a bug in NSTouch in 10.10.2 and was not caused by the deprecated api. It affected many applications.

 

[emporiky]

Is there any difference in UI performance when translucency is turned on ?

 

[feriamsidera]

Dual Monitors Broken

The menu bar and dock no longer appear on my other screen. Seems dual monitor support at least on my 2011 model MBP has reverted to Mavericks. Hyperdock is broken as well.

 

[feriamsidera]

The menu bar and dock no longer appear on my other screen. Seems dual monitor support at least on my 2011 model MBP has reverted to Mavericks. Hyperdock is broken as well.

Yeah still not working after reboot. Worse yet the dock won't even come up when up at all on the other monitor. So if you are running dual monitors on your 2011 MBP you probably want to skip this update. Even though it seems to exhibit better ram utilization.

----------

Yeah still not working after reboot. Worse yet the dock won't even come up when up at all on the other monitor. So if you are running dual monitors on your 2011 MBP you probably want to skip this update. Even though it seems to exhibit better ram utilization.

Alright seems the option Displays have separate Spaces under Mission Control got toggled off (oddly) after update. With this toggled back on everything works again.

 

[justperry]

A user on 9to5Mac confirms 10.10.2 is still doing the blank screen after waking from sleep or rebooting. So those who saw these issues from previous 10.10.2 betas might want to skip this one as well unless Apple asks you to test it.

Yup, I have the same issue, this seed didn't resolve it.

 

[name99]

Millions of lines of code. Millions to billions of user scenarios. Various routers and configurations.

I don't like this sort of excusing Apple because it doesn't do anything to solve the problem. What's the REAL problem here?
Let's be adults. It's not that Apple is populated by idiots or wants to screw over its users or something. The problem is (IMHO) that Apple has, through a combination of accidents as much as planning, created a juggernaut that has to hit its mark around October every year.

The iPhones are expected to come out then, not least to match people's phone upgrade cycles and the holiday buying season. But there's an expectation that new iPhones mean a new version of iOS that exploits their new hardware features. And we're now seeing the ever tighter integration of OSX with iOS which put OSX on the same schedule. So a whole lot of SW ships before it's really ready.

I think the answer is that, starting with 2015, Apple need to break the connection between iOS releases and new iPhones, just like they have with OSX and new macs. Release the phones with a point update --- if the prevailing iOS is 8.2.3, release the iPhone 6S with iOS 8.2.4 or 8.3, a minor update that understands the new hardware and maybe makes minimal use of the new features, but nothing more aggressive than that. Meanwhile iOS and OSX can drop as a combined bundle WHEN THEY ARE READY AND FULLY TESTED, on whatever schedule that takes --- maybe we'll see them update full every eighteen months or so rather than the frantic pace of once a year.

Nobody else has a release schedule as tightly dependent on so many moving parts as Apple, and I think this is the year we've seen it pushed too far, to the general detriment of the brand and the user experience...

 

[JGRE]

...still a lot less variants than Windows and there are still so many glaring obvious bugs I feel that Apple just doesn't care about quality as much as they used to.

....and Windows is bug free? Really?

 

[AllergyDoc]

Working great for me so far, overall, although I needed to turn WiFi off and on to get it running at full speed.

Time Machine still seems to be mucked up. I run it over WiFi to a HD on my Extreme. It starts the backup, runs for a while, but then seems to freeze. At least the display freezes. As this moment it reports it has backed up 185.5 MB of 2.52 GB and there is 20 minutes left in the backup. It hasn't changed in 10 minutes. I can access the Time Machine backup in Finder and when I enter Time Machine, the last file I worked on is there. I think it's backing up fine, it's just not reporting accurately.

I run my rMBP in clamshell mode, hooked up to a K272HUL 2560 x 1440 monitor. I hope I'm not premature in reporting that the font rendering seems to be better. Must be my old eyes.

 

[pickaxe]

Millions of lines of code. Millions to billions of user scenarios. Various routers and configurations.

Hey, just like every enterprise product ever. Except those have 1/1000 the budget and 1/1000 the bugs.

 

[HyperZboy]

Had enough of the wifi and bluetooth problems, upgraded back to Mavericks, almost forgotten how much better it looks and it works.

I've told everyone I know running Mavericks that unless you need a particular feature, don't bother upgrading to Yosemite yet.

I still have internet and bluetooth issues that I've reported since BETA 1.

What are we on now? BETA 8 or 9? HAHA!

I don't even consider the GM as nothing but another beta.

----------

Hoping for TWO things fixed:

1) Log in screen shown on the correct display using TWO monitors

2) Safari "lag" when typing and general navigating

I reported this issue on the very first public beta and every beta since and it's as if I just completely wasted my time testing this Yosemite beta.

Apple has done NOTHING about it and it's such an easily reproduced issue.
I realize many people don't use 2 displays, but it's not like it's uncommon.
Most Pro users do.

----------

Millions of lines of code. Millions to billions of user scenarios. Various routers and configurations.

And millions of people with excuses for Apple.

----------

I completely agree. We are almost two months since the release date and I still cannot reliably connect to WIFI and I cannot use my magic mouse or keyboard because there are issues with bluetooth. There is definitely a quality control issue at Apple - they've proven this several times recently.

The issue I have is similar. Connecting my iPhone often disables Bluetooth completely, no mouse, no keyboard. Only solution is a reboot.

I've reported this since Public Beta 1 and Apple has STILL not fixed it.

 

[Magster2]

Yosemite - not so impressed!

I tried Yosemite twice and had to downgrade to Maverics (also twice) in the end....
I have a brand new 2014 MacBook Air and had some problems with 3rd party software while using Yosemite (which I then resolved) however could not resolve a massive battery drain issue (on both occasions while running erm...NOTHING) so back to Maverics it is Might skip Yosemite altogether and wait for 10.11 .....

 

[Kariya]

I don't like this sort of excusing

And millions of people with excuses for Apple.

I'm not making any excuses for Apple. The bugs suck and are annoying. But there's only so much testing you can do before you ship. That was my point.

At the end of the day no one who releases a new OS, mobile or desktop, will release something thats completely bug free. 1 yr cycle or 5 yrs it doesn't matter.

MS, Apple and Google all figure it out as they go along based on user feedback.

This is just the way the cookie crumbles.

Report all the bugs you're having to Apple. And if you need a working machine, revert to Mavericks like I did until your bugs are fixed.

 

[xgman]

just a big sigh.......... It just seems like OSX bug fixes have become an afterthought and that anyone working on this at Apple has taken a dumb pill.

----------

Millions of lines of code. Millions to billions of user scenarios. Various routers and configurations.

That were all working reasonably well in the prior OS. Maybe it's time to rethink the purpose of updating the OS to begin with.

 

[yetanotherdave]

----------

[/COLOR]

Is this legit? I'm reluctant to do this. I've gotten all the other public betas without doing this.

Worked great for me.

 

[jimpdx]

Oh my GOD I can use Chrome again! Thank you ghost of Steve Jobs!

I can't give props to Steve on this one but yes same - I can finally go back to Chrome! Using Safari the past week has been killing me. Missed all my extensions

 

[cgc]

....and Windows is bug free? Really?

No, but Windows has a legitimate problem to deal with regarding the multitude of combinations of parts (e.g. motherboards, CPUs, memory, GPUs, NICs, etc.) it must support so I would expect bugs in Windows more than in Macs. Windows is far from bug free, I prefer OSX, but I find the lack of quality control a little disconcerting as of late.

 

[MarcusCarpenter]

And then there's his quirky problem that goes back to Beta 1...

The Feedback Assistant program actually disables my internet. In order to send feedback, I have to lose my internet connection during the collection process, then re-start my router to send it!

This is INSANE! This never happened in Mavericks. None of these problems did.

----------



Is this legit? I'm reluctant to do this. I've gotten all the other public betas without doing this.

Yeah totally I'm using it fine, it's all the seed configuration utility does, it can easily be removed under AppStore in preferences

 

[Michael Goff]

....and Windows is bug free? Really?

No, but recently it has had fewer bugs than OSX.

 

[tywebb13]

We know that many of you are anxious to try the developer beta versions of OS X, the only way to legally do so it to be a registered developer of Apple software.

We do not allow for any discussion about specific steps that need to be taken to run the software without a proper license.

Thank you for your cooperation!

Sorry i mean:

blagh blagh blagh (command deleted by tywebb13 for reasons explained below)

Works perfectly

Clever to gain access to developer betas without being a developer - until the day you get one that ruins your system.

Not to mention that it is against macrumors forum rules to reveal this to the public via macrumors forums.

Now I have no doubt that MarcusCarpenter is capable of fixing his system if he uses this and it ruins his system. But to put it in this forum for all to see (many of whom would not have a clue how to fix it if things go awry) is just going to result in disaster.

There is a reason apple release this to developers first.

If downvoting were possible, I'd upvote MarcusCarpenter for cleverness and neutralise it by downvoting for being very unwise.

So a WARNING:

If you are a registered developer, you already have legitimate access to the developer betas. If you are not a developer, you DON'T have legitimate access and it is safer to just ignore MarcusCarpenter's instructions.

And I don't mean to be rude to MarcusCarpenter, but we already know you are clever, so no need to prove this. But prove you can also be WISE and delete these instructions in your posts.

 

[MarcusCarpenter]

Clever to gain access to developer betas without being a developer - until the day you get one that ruins your system.

Not to mention that it is against macrumors forum rules to reveal this to the public via macrumors forums.

Now I have no doubt that MarcusCarpenter is capable of fixing his system if he uses this and it ruins his system. But to put it in this forum for all to see (many of whom would not have a clue how to fix it if things go awry) is just going to result in disaster.

There is a reason apple release this to developers first.

If downvoting were possible, I'd upvote MarcusCarpenter for cleverness and neutralise it by downvoting for being very unwise.

So a WARNING:

If you are a registered developer, you already have legitimate access to the developer betas. If you are not a developer, you DON'T have legitimate access and it is safer to just ignore MarcusCarpenter's instructions.

And I don't mean to be rude to MarcusCarpenter, but we already know you are clever, so no need to prove this. But prove you can also be WISE and delete these instructions in your posts.

Actually I have a full Mac and iOS developer license
I already told you that command is exactly what the seed utility does straight from the Dev centre, this command is also in the apple developer forums

 

[tywebb13]

Actually I have a full Mac and iOS developer license

I don't doubt your developer status.

I already told you that command is exactly what the seed utility does straight from the Dev centre

Yes. I know you did.

this command is also in the apple developer forums

And that is where it should stay.

Putting it in macrumors forums basically gives everybody access to the developer betas. This is against macrumors rules.

We do not allow for any discussion about specific steps that need to be taken to run the software without a proper license.

It is also unwise to do so because many people reading it will just run the command without considering the consequences and might not have the skills to fix a computer system corrupted by a buggy beta.

 

[AllergyDoc]

This update includes Safari 8.0.2