Also after typing in terminal that and reboot I have no Debug menu in Disk Utility.In terminal type this:
defaults write com.apple.DiskUtility DUDebugMenuEnabled -bool true
then in disk utility in the Debug menu item click Show every partition
Also after typing in terminal that and reboot I have no Debug menu in Disk Utility.In terminal type this:
defaults write com.apple.DiskUtility DUDebugMenuEnabled -bool true
then in disk utility in the Debug menu item click Show every partition
I had filed a bug with Apple that sounds somewhat involved with what you were seeing. Basically, I'm still on iOS 8.3 on my iPhone and Mac OS X 10.9.5 on my "daily driver" MacBook Pro, but many clients are on 10.10 and upgrading to 10.11. What I'd find is that when I'd log on to their machines--to an admin account I had previously created and had configured my AppleID--and perform the update, invariably I'd get my AppleID booted out on all the rest of my devices. Apple closed the bug once saying they couldn't repro, but i re-opened it and it stayed open and they have suggested several times (over several updates) the problem is fixed. They still have not reported on the bug more recently. But it would seem that the activation of the newer AppleID security features is playing havoc on previously created login tokens. So I don't find that 10.11.5 causing you these issues surprising, clearly they're doing some voodoo on the backend to try to chase down/fix what is likely now at least a "known" issue.But then I saw in the iMessage settings of my phone that I was logged out with my Apple ID. It was only activated with my phone number.
I feel really blessed as I've never had a problem with any of my Mac's. However, I started buying Mac's 3 years ago, and I see people posting problems with computers as old as 2009. 1st, I cannot believe these computers are still running. That is a testament to Apple hardware quality.I feel the same way. Unless these few actually did get a lemon of a Mac.
I feel really blessed as I've never had a problem with any of my Mac's. However, I started buying Mac's 3 years ago, and I see people posting problems with computers as old as 2009. 1st, I cannot believe these computers are still running. That is a testament to Apple hardware quality.
Second, I have some theories as to why they are having problems.
The obvious one, that they have old hardware and it's showing it's age.
The less obvious one , that fewer beta testers have the same model of computer , so that it's more likely that bug unique to their hardware will not be caught.
Finally, they have a unique mix of hardware and software that is just the right combination for the bug to appear.
We should clone my Macs that have not had any problem and distribute them amongs the Apple user community. That would solve everyone's problems.
Makes sense, as all the versions after Snow Leopard have stopped at the .5 release and only get minor security and bug fix updates after that. Timing is just a bit different this year with 10.11.5 releasing prior to WWDC.It seems there won't be another beta like 10.11.6 again. They now even removed the link to the 10.11.5 delta update from their "secret" websites what always had the links to every developer beta update and the other one to all public betas back to the first one of 10.11.0 in them. Now there is only the combo update for the final 10.11.5 in both + a separate link to the firmware update as always and most of the usual other stuff.
They now even removed the link to the 10.11.5 delta update from their "secret" websites
The Safari betas for older OS X versions are still in there.
I hear you & had been trying to pair them myself ages ago & saw what you see. Initially it seems like they will pair but then don't. I still think its due to protocol support and you won't be able to make it work unless Apple changes the behaviour.iPhone should be discoverable, for example, to mirror the screen, to use iPhone as controller, and in numerous other apps, such as Infuse https://itunes.apple.com/app/id577130046, which has Bluetooth sharing to iOS devices. The problem is, iPhone isn’t discoverable:
After a day....
- WiFi bug hasn't resurfaced ... yet ... hopefully never ... It's Back
- Battery life is less ... monitor says it is Safari
- Safari beach ball has taken a vacation ... so far
- It now gets much warmer when watching streaming video
Will post more as I find it...
Update: Added video item
Update 2: Wifi bug is back. Have to turn off / turn on Wifi this morning to get it to recognize from sleep.
[doublepost=1463903748][/doublepost]
I had that WIFI issue a lot on Yosemite, then El Cap was much better but it still occurred once in a while.
Bought a Ubiquiti Unifi AC Pro, never had that issue again.