-
All replies
-
Helpful answers
-
Apr 19, 2015 1:56 AM in response to cte0110by Stephen Jones2,I agree. The supplemental update makes no difference to the issue. As I had been using betas I also tried the combo update, which seemed to be better for a while but the same problems are back as before. The Console messages about:
19/04/2015 09:52:30.531 com.apple.preference.universalaccess.remoteservice[5857]: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
is still present.
A string of these are seen whenever I enter the trackpad settings in Accessibility Preferences but it does cure the issue (for a short while)
I hear 10.10.4 is for "Stability Improvements". Hope this is one of them.
-
Apr 21, 2015 8:14 AM in response to Paul2perthby Paul2perth,I have painfully reverted back to OSX 10.10.2 and all working again. It can stay that way until I see proof Apple are fixing their bugs!
-
Apr 23, 2015 7:05 PM in response to tdawgmdby Whatzup,I have been having the same problem and have tried every solutions suggested by people. It is very frustrating. The QA from Apple is definitely trending down significiantly. Very annoying!
-
Apr 28, 2015 11:38 PM in response to tdawgmdby yogiblair,Just a (hopefully) positive update....
I've installed the first public beta of 10.10.4 and so far this has solved the bluetooth connection issues.... (fingers and everything else crossed)
With Macbook Pro Retina 13 in clamshell mode, the Bose Sound mini now playing flawlessly and the mouse and keyboard are both solidly connected with no drop outs or stuttering mouse movements...
I'll post back after a full day of testing should there be any degradation to the connection..
-
Apr 29, 2015 8:00 AM in response to yogiblairby Whatzup,@yogiblair Thanks for the update! I hope it is not going to be a long wait before 10.10.4 is released.
-
Apr 29, 2015 8:54 AM in response to Whatzupby yogiblair,So that is a full day and no problems at all with bluetooth.... connecting and disconnecting smoothly and operating perfectly
Looks like 10.10.4 contains the fix, at least for my setup. Hopefully the final release of this version post beta won't break whatever has been done in the first public beta
-
May 1, 2015 8:47 AM in response to tdawgmdby Corrode,10.10.4 has solved my issues as well. Wish I wouldn't have wasted so much time on the phone with Applecare. No one from Apple wants to admit it's a software issue with 10.10.3.
-
May 6, 2015 9:03 AM in response to Corrodeby Headygoodness,I am having this problem on my mid 2010 macbook pro as well, after the upgrade to 10.10.3. No bluetooth after wake. Now with 10.10.4 beta (14E11f), after wake bluetooth is simply disabled and won't enable.
So it's not fixed for my setup! How annoying is this!!!
-
May 6, 2015 10:50 AM in response to Headygoodnessby Headygoodness,I'll add to my previous post.. 2nd time I tried doing a wake bluetooth is still enabled but the bluetooth mouse and keyboard just won't respond or connect.. same as 10.10.3
Seems to me this would be a pretty important thing to be fixing, yes?
-
May 6, 2015 11:00 AM in response to Headygoodnessby Headygoodness,Okay this just worked for me as a fix, in case someone else is in the same boat.
Open a terminal and run:
sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransportsudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransportThen, I had to click on the bluetooth icon again and enable it, and my peripherals connected again.
-
May 6, 2015 7:23 PM in response to Headygoodnessby Whatzup,I confirm this temporary fix works. THANK YOU!!!
It still needs to be done every time my MBP wakes up. This is very inconvenient. I hope 10.10.4 will fix that permanently.
-
May 6, 2015 10:26 PM in response to Whatzupby Headygoodness,Well, the 10.10.4 beta doesn't fix it for me... maybe the final release version will.
Anyways after my last post, I found this script that some fellow made which installs and configures a process called "sleepwatcher" to automatically run those commands upon wake. This is working for me automatically now.
Here's the github address:
https://gist.github.com/Tyilo/c92684d277acb62272b5
In case you're not a unix person, step by step here:
open a terminal window and run 'nano sleepwatch.sh'
copy the script from that github page and paste it into the terminal window.
Save the file in nano by selecting the terminal window and hitting control-O and enter.
Exit nano by pressing control-X.
run 'sudo chmod 777 sleepwatch.sh'
run './sleepwatch.sh'
now it should be working.
Cheers
-
May 7, 2015 2:23 AM in response to Headygoodnessby Paul2perth,I guess I'll stick with OS X 10.10.2 until I hear this has been fixed from multiple people. My iMac is running beautifully at the mo.
Thanks guys
-
Jun 9, 2015 6:11 AM in response to tdawgmdby sean-campuslabs,Headygoodness's fix worked for me. Thanks!
-
Jun 10, 2015 11:34 AM in response to Headygoodnessby FolsomRider,10.10.4 beta user here and the pairing broke with the 10.10.4 beta. I've just updated today to the most recent public beta update, 14E33b, and still unable to pair. I tried the terminal commands suggested, but still no success pairing.