Help with Handoff on cMP 5,1?

[Turbo Tony]

OK, so I got the upgrade bug as soon as I bought my cMP 5,1 8 core. I bought the upgraded Wifi/Bluetooth card recommended on here and my system sees it. Both the Wifi and Bluetooth work fine but I can't seem to get Handoff/Continuity to work.

The System Profiler shows the new card as being Handoff compatible.
Handoff is turned on on both my Mac and my iPhone X.
Both devices have Bluetooth turned on.
Both devices have Wifi turned on and connected to the same network.
I tried signing out of iCloud on both devices and back in (boy, that was a horrible experience on the phone - I had to add all the card in my wallet back).​

I can't think of anything else to try. The Bluetooth menu on the Mac shows the iPhone isn't connected to the Mac, but I can connect it by selecting it. Strangely, it doesn't say 'Connect' like all my other devices do. Instead, it says 'Connect to Network'. I'm assuming that's so it can be used as a hotspot?

Does anyone have any ideas so I can move on to my next upgrade?

 

[bookemdano]

What OS? High Sierra?

You need a piece of software called Continuity Activation Tool. There's also a big thread here all about Continuity/Handoff stuff (you might want to read it backwards since the most applicable stuff is near the end of the thread):

https://forums.macrumors.com/thread...on-mac-pro-2010-keep-updating.1748061/page-39

 

[Turbo Tony]

Oops Sorry, I should have mentioned that. Yes, I'm using High Sierra.

I tried the Continuity Activation Tool and it didn't run because it said it was already running. I can see the option in my System Preferences.
[doublepost=1528750032][/doublepost]I just re-read the instruction on the other thread and I disabled SIP to rerun the CAT. I got the same message saying that Continuity was already active. I ran the diagnostics and got this:

--- OS X Continuity Activation Tool 2.3 ---

by sysfloat

original by dokterdok




--- Initiating system compatiblity check ---


--- Hardware/OS checks ---

Verifying Continuity status... OK. OS X reports Continuity as active

Verifying Mac model reference... OK. Known compatible Mac Model detected: MacPro5,1

Verifying Mac board-id... OK. Short board id detected: Mac-F221BEC8

Verifying OS X version... Warning: This tool wasn't tested with OS X versions higher than 10.10. Detected OS version: 10.13.5

Verifying Wi-Fi hardware... WARNING. An unknown/untested AirPort card using the 'BrcmNIC' kext is active. This tool can't fix this.

Verifying AWDL status... OK. An AWDL interface is up, Wi-Fi is ready for Continuity

Verifying Bluetooth hardware... OK. The internal Bluetooth card is active

Verifying Bluetooth version... WARNING. New Bluetooth version detected (LMP Version 8), compatibility with this tool is unconfirmed

Verifying Bluetooth features... OK. Bluetooth features are Continuity compliant

Verifying Bluetooth firmware... OK. Bluetooth firmware version: v158 c4806

Verifying Login Item... OK. Login item for Auto Continuity Check is not set.


--- Modifications check ---

Verifying OS kext protection... OK. Kext developer mode is not active. This tool can fix this.

Verifying kexts readability... OK. Wi-Fi and Bluetooth kexts were found and could be read

Verifying Wi-Fi whitelist status... OK. Your board-id is not yet whitelisted. This tool can fix this.

Verifying BT4 dongles compatibility... OK. Compatibility with BT4 USB dongles is not enabled, this tool can fix this if a dongle is plugged in

Verifying old Wi-Fi kext presence... OK. Legacy Brcm4331 Wi-Fi driver is present. This tool can fix this.

Verifying legacy Wi-Fi card patch... OK. The legacy Wi-Fi patch is not present. This tool can fix this.

--- Modifications check ---


Press any key to go back to the main menu...
​

Does anyone have any idea what to do next?

 

[bookemdano]

I haven't kept up with CAT. I seem to remember for Sierra there being a beta version you had to download that wasn't the main one linked on the site. That could have changed in the interim, however.

Anyway, if you take a look in the thread I linked there is a post on the last page where one of the users here provided a terminal command to run that apparently accomplishes the same thing. I haven't tested it myself but might be worth a try. SIP needs to be disabled (just as with CAT). Give that a try and see if it works after a reboot.

 

[crjackson2134]

In a Terminal window, past the following command:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

 

[Turbo Tony]

It worked! Thanks so much!

It took two restarts of the Mac and iPhone until it eventually got the picture, but it's working!

Thank you!

 

[haralds]

In a Terminal window, past the following command:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

This is the quickest way.
With CAT you do have to turn of SIP and run it despite its assurances it is not needed.

Continuity generally works, but the BLE range with the case is pretty poor. So it is spotty.

 

[RetroDan]

In a Terminal window, past the following command:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

THIS. This fixed months of issues and Time Machining due to lost Bluetooth functionality. Do this, reboot, and rejoice if you are on a 2009->2010 Mac Pro.

 

[lingwow]

In a Terminal window, past the following command:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

This doesn't seem to be working for me.. I first used the CAT tool, the official release and that put me into a boot loop. Then I tried the BETA release, avoided boot loop but still no handoff or continuity. Then I used the CAT to delete whatever changes it made, at least I think I did that right. Then I tried the code you pasted above in terminal, and still no luck. I am just using a cheap dongle I got on Amazon. I don't even have the option to enable handoff in preferences, but it's odd because some of the features are working. I get calls on the mac, sms messages.. But the enable handoff option isn't visible, and I have no air drop or continuity. Any ideas? Could I have messed up the repositories with trying CAT 2 different times?

 

[RetroDan]

This doesn't seem to be working for me.. I first used the CAT tool, the official release and that put me into a boot loop. Then I tried the BETA release, avoided boot loop but still no handoff or continuity. Then I used the CAT to delete whatever changes it made, at least I think I did that right. Then I tried the code you pasted above in terminal, and still no luck. I am just using a cheap dongle I got on Amazon. I don't even have the option to enable handoff in preferences, but it's odd because some of the features are working. I get calls on the mac, sms messages.. But the enable handoff option isn't visible, and I have no air drop or continuity. Any ideas? Could I have messed up the repositories with trying CAT 2 different times?

So...you're saying that you uninstalled the CAT mod, and you're having problems getting the mod you uninstalled to work? I think I know what your problem is...

You need to use the terminal code with the mod installed, mate...

 

[bookemdano]

Yeah I think the terminal command alone only works if you put in the OEM Airport/BT4 cards. Third-party stuff still needs extra sauce that CAT does, AFAIK.

 

[haralds]

This doesn't seem to be working for me.. I first used the CAT tool, the official release and that put me into a boot loop. Then I tried the BETA release, avoided boot loop but still no handoff or continuity. Then I used the CAT to delete whatever changes it made, at least I think I did that right. Then I tried the code you pasted above in terminal, and still no luck. I am just using a cheap dongle I got on Amazon. I don't even have the option to enable handoff in preferences, but it's odd because some of the features are working. I get calls on the mac, sms messages.. But the enable handoff option isn't visible, and I have no air drop or continuity. Any ideas? Could I have messed up the repositories with trying CAT 2 different times?

I found I had to disable Sip, apply it, then reenable it.

 

[JeDiGM]

Anyone try this with Mojave yet? Still working?

 

[bookemdano]

Worked fine for me on Mojave just disabling SIP and then using the terminal command in post #5. No need for the CAT tool.

 

[h9826790]

Anyone try this with Mojave yet? Still working?

It's working.

 

[PianoPro]

With a BT dongle you must still use CAT? Is that correct? I tried just the terminal command and it doesn't produce the handoff option in the System Preferences General pane.

 

[h9826790]

With a BT dongle you must still use CAT? Is that correct? I tried just the terminal command and it doesn't produce the handoff option in the System Preferences General pane.

Depends on the dongle, but AFAIK, almost any BT dongle that made from factory need CAT. Only those “man made for Mac” dongle may has the correct broadcom chip inside and only need the terminal command to activate Handoff on cMP.

 

[PianoPro]

Depends on the dongle, but AFAIK, almost any BT dongle that made from factory need CAT. Only those “man made for Mac” dongle may has the correct boardcom chip inside and only need the terminal command to activate Handoff on cMP.

I use the Asus BT-400 which is a Broadcom chip. Chipset: 20702A3 Firmware Version: v14 c4096
As I said I tried the terminal command and read back the Plist and the motherboard compatibility did get set to true - as desired. But there's no option to enable handoff in the General Preference Pane. So I'm guessing something else needs to be done - and that's probably what CAT does.

 

[nickbatz]

Mac Pro 5,1 12 x 3.46GHz, Mojave 10.14.1

Will this card work for Continuity, Handoff, Airdrop? The seller says yes, but I don't want to have to return it to China if it doesn't work.

(It has the BCM94360 chipset.)

TIA

 

[macnu]

In a Terminal window, past the following command:

sudo /usr/libexec/PlistBuddy -c "Set:Mac-F221BEC8:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"

Thanks !! It worked perfectly for me, now besides airdrop I have continuity camera and unlock with apple watch

 

[h9826790]

Mac Pro 5,1 12 x 3.46GHz, Mojave 10.14.1

Will this card work for Continuity, Handoff, Airdrop? The seller says yes, but I don't want to have to return it to China if it doesn't work.

(It has the BCM94360 chipset.)

TIA

It will only work if you know how to connect the USB connector. It looks like that's the standard connector, and only good for Hackintosh.

 

[Boomish69]

I got the "Apple Broadcom Bcm94360cd WiFi Card 802.11ac 2.4/5ghz 1.7gbps Bluetooth H4g0" card from Ebay and have it installed bluetooth and wifi are working but I can't seem to enable Airdrop or Continuity. It's connected to the USB , I had to wire up a custom lead so I know it didn't work before I did this. Now Bluetooth works a treat just not Airdrop etc.

I've disabled SIP and run the terminal command twice with a reboot but it still shows as not supported..

Anyone got an idea's on what else to try?

This is what system report shows..
Bluetooth Low Energy Supported: Yes
Handoff Supported: No
Instant Hot Spot Supported: No
Manufacturer: Broadcom
Transport: USB
Chipset: 20702B0
Firmware Version: v150 c9316
Bluetooth Power: On
Discoverable: On
Connectable: Yes
Auto Seek Pointing: On
Remote wake: Off
Vendor ID: 0x05AC
Product ID: 0x828B
HCI Version: 4.0 (0x6)
HCI Revision: 0x2464
LMP Version: 4.0 (0x6)
LMP Subversion: 0x4196
Device Type (Major): Computer
Device Type (Complete): Mac Desktop
Composite Class Of Device: 0x380104
Device Class (Major): 0x01
Device Class (Minor): 0x01
Service Class: 0x1C0
Auto Seek Keyboard: On

 

[tommy chen]

802.11ac, BT 4.0 and Continuity & Handoff are working on Mac Pro 2010 (Keep Updating)

If you run macOS 10.14+ Restart Mac Pro Hold down Command-R to reboot into Recovery Mode. Click Utilities. Select Terminal Type csrutil disable Press Return or Enter on your keyboard. Restart Mac Pro Open Terminal and run this: sudo /usr/libexec/PlistBuddy -c...

forums.macrumors.com

 

[Boomish69]

802.11ac, BT 4.0 and Continuity & Handoff are working on Mac Pro 2010 (Keep Updating)

If you run macOS 10.14+ Restart Mac Pro Hold down Command-R to reboot into Recovery Mode. Click Utilities. Select Terminal Type csrutil disable Press Return or Enter on your keyboard. Restart Mac Pro Open Terminal and run this: sudo /usr/libexec/PlistBuddy -c...

forums.macrumors.com

Thanks Indiox, dunno how I missed all these pages..
I did the new terminal commands still doesn't work , ploughing through the rest of the pages for more fixes to try

 

[tommy chen]

i use this methode (maybe the sama) for HS and mojave working

For those interested in fixing this problem by themselves, the solution is quite simple really, 
although people prone to clumsy errors should probably refrain from trying this, as failure to follow the instructions to the letter might cripple your Mac.

First of all, you should be certain that you have an up-to-date backup of your High Sierra disk 
and that you know how to use it in case something goes wrong. If you don't know how to restore from a backup,
don't read any further.
Secondly, you should disable SIP, at least for the time being. 
Boot your Mac from the High Sierra Recovery Partition. Once booted, 
go to the Tools menu and open Terminal. Then, in Terminal, enter
csrutil disable
Reboot your Mac normally.

Next you need to find out your computer board id. 
It's different for every particular Mac model. For instance, 
my Mac board id is "Mac-F221BEC8" because it's a Mac Pro 5,1 of 2010. 
If it had been a Mac Pro 5,1 of 2012, its board id would be different. 
If you don't know yours, Google your specific model until you find 
two or three corroborating testimonies that what you find is, indeed, your computer board id.

So, repeating the explanation above that I posted 29 days ago, do the following:

Using TextEdit or a similar tool, open /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist 

You should see a list of board ids. 
Find the relevant entry for your model. 
Once found, you should see that it has one subelement called "ContinuitySupport". 
Presumably, it has the boolean value "false"; that should be changed to "true". Save the file.

Study this command (it's one single line):
sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F221BEC8\0\0\0\0\0\0\0\0/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360

Notice that "F221BEC8\0\0\0\0\0\0\0\0" is the "short" board-id (excluding the "Mac-" part) 
of the Mac Pro 5,1 of 2010, followed by eight nulls, making up the 16 bytes used by the current "long" board ids. 
Now, edit the above line (for instance, using TextEdit) so that, instead of "F221BEC8\0\0\0\0\0\0\0\0" 
you paste whatever board id your computer has. 
If it is eight bytes long, remember to add the eight nulls.
Now, double check that your modified line is the correct equivalent of the instruction above for your computer.

Open Terminal. Select your previously edited instruction of step 2 and drag it to your Terminal window. 
Press Enter. You'll be prompted to enter your administrative password. Do it.

Now you only need to delete the kext cache:
Enter this in Terminal:
cd /System/Library/Extensions/
sudo touch .
Boot your computer.

Instant Hotspot, Handoff, Universal Clipboard and Apple Watch Unlock should work. 
If they don't, your BT/Wi-Fi card might not be compatible with the hardware identified by the AirPortBrcm4360.kext.
If there isn't a particular kext for your card, you may be out of luck.

Another explanation for the above procedure not to work might be that there's something wrong 
in your Apple ID data on your devices and/or in the relevant choices you make as to 
how Continuity/Handoff should work.

Lastly, chances are you might have done something wrong in following the above procedure. 
Repeat it slowly, just in case.