Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Running El Capitan. I have a spare partition where I test major MAS OS upgrades prior applying them on my production environment. I will update to Sierra and higher up see if that helps but doubt it.

SIP is not disabled but to my understanding there is no need for CAT for that card so not sure why disable SIP. I might be wrong.

There are lots of small variation for these cards. If you can't make it work straight away, better disable SIP and run CAT.
 
Last edited:
  • Like
Reactions: polanskiman

polanskiman

macrumors regular
Feb 12, 2010
176
45
There are lots of small variation for this card. If you can't make it work straight away, better disable SIP and run CAT.

That is interesting I didn't know there were different variants of this model. I will try the above.
 

crjackson2134

macrumors 601
Mar 6, 2013
4,847
1,957
Charlotte, NC
There are lots of small variation for these cards. If you can't make it work straight away, better disable SIP and run CAT.

Is there a current card I can use to eliminate the need for CAT or terminal commands to activate? I have a AC/BT4 card already working with handoff etc... It would be nice to work OOTB.
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I am quite sure in the newer OS, it's not about the card anymore, but the cMP itself is not on the white list. Therefore, no matter which card you use, there should be no OOTB Handoff support.
 
Last edited:
  • Like
Reactions: crjackson2134

polanskiman

macrumors regular
Feb 12, 2010
176
45
I am quite sure in the newer OS, it's not about the card anymore, but the cMP itself is not on the white list. Therefore, no matter which card you use, there should be no OOTB Handoff support Handoff.

What wifi card do you have exactly and what OS version are you on? I see in your signature you have BT4.2.
 

Squuiid

macrumors 68000
Oct 31, 2006
1,877
1,713
I am quite sure in the newer OS, it's not about the card anymore, but the cMP itself is not on the white list. Therefore, no matter which card you use, there should be no OOTB Handoff support Handoff.
Exactly. With the BT 4.2 cards it’s just a question of adding the cMP to the plist whitelist and that’s it. (Which is exactly what the terminal command does.)
 
  • Like
Reactions: h9826790

crjackson2134

macrumors 601
Mar 6, 2013
4,847
1,957
Charlotte, NC
Exactly. With the BT 4.2 cards it’s just a question of adding the cMP to the plist whitelist and that’s it. (Which is exactly what the terminal command does.)

Yes, it’s been that way for a while, but I thought (hoped) perhaps something had changed. I read too much into that post, so I had to ask.
 

bookemdano

macrumors 68000
Jul 29, 2011
1,514
846
I wish there were a similar plist (or is there?) to enable true WiFi calling on the cMP (without your phone needing to be nearby). To my knowledge it's only ever been possible using Clover to emulate a nMP.
 
  • Like
Reactions: eksu

crjackson2134

macrumors 601
Mar 6, 2013
4,847
1,957
Charlotte, NC
I wish there were a similar plist (or is there?) to enable true WiFi calling on the cMP (without your phone needing to be nearby). To my knowledge it's only ever been possible using Clover to emulate a nMP.

I don’t use it, but I thought you could already do that with FaceTime Audio only calls. I guess that’s not how it works then?
 

bookemdano

macrumors 68000
Jul 29, 2011
1,514
846
I don’t use it, but I thought you could already do that with FaceTime Audio only calls. I guess that’s not how it works then?

To clarify: I'm talking about a feature offered by the primary US cell carriers (AT&T calls it NumberSync) whereby other Apple devices (Apple Watch, iPads, 2012+ Macs) are allowed/able to use their WiFi connection to make and receive phone calls without your phone being anywhere nearby. On the Mac, it gets enabled via the FaceTime app but it's different than FaceTime Audio in that you can answer any call that comes in to your cell phone number (not just other Apple users).

Apple enabled it for all 2012+ Macs except for the 2012 Mac Pro. Isn't that lovely.
 

Squuiid

macrumors 68000
Oct 31, 2006
1,877
1,713
To clarify: I'm talking about a feature offered by the primary US cell carriers (AT&T calls it NumberSync) whereby other Apple devices (Apple Watch, iPads, 2012+ Macs) are allowed/able to use their WiFi connection to make and receive phone calls without your phone being anywhere nearby. On the Mac, it gets enabled via the FaceTime app but it's different than FaceTime Audio in that you can answer any call that comes in to your cell phone number (not just other Apple users).

Apple enabled it for all 2012+ Macs except for the 2012 Mac Pro. Isn't that lovely.
This feature works fine with a BT 4.2 card in a cMP. Just run the terminal command to add the cMP to the whitelist and that's it.

From my Mac Pro's FaceTime preferences:
upload_2018-9-7_23-30-17.png


UPDATE: Sorry, I misread your post. You said "without devices being anywhere nearby".
My bad.
 

bookemdano

macrumors 68000
Jul 29, 2011
1,514
846
This feature works fine with a BT 4.2 card in a cMP. Just run the terminal command to add the cMP to the whitelist and that's it.

From my Mac Pro's FaceTime preferences:
View attachment 780192

UPDATE: Sorry, I misread your post. You said "without devices being anywhere nearby".
My bad.

Yeah, thanks anyway. I'm guessing there hasn't been much effort to try to get it enabled because the underlying technology is only widely available on US cellular networks. Not a big deal.
 

polanskiman

macrumors regular
Feb 12, 2010
176
45
There are lots of small variation for these cards. If you can't make it work straight away, better disable SIP and run CAT.
That didn't work. Disabled SIP and run CAT. CAT complained. BT still not recognized. I am starting to think that card is partially dead. I also ordered another adaptor as I don't like the one I bought. The small JS connector prevents the card from being properly positioned in the adaptor and remains at an angle.
 

mattspace

macrumors 68040
Jun 5, 2013
3,344
2,975
Australia
haha, just did the boot to recovery, SIP disable, reboot to normal user account, run command, iCloud Logout, reboot to recovery, SIP enable, reboot to user account, iCloud Login - and within seconds I had the Safari Continuity tab show up on my dock. Happy result.
 
  • Like
Reactions: Squuiid

Dan Streaman

macrumors newbie
Aug 17, 2018
18
7
That didn't work. Disabled SIP and run CAT. CAT complained. BT still not recognized. I am starting to think that card is partially dead.

Very unlikely. More likely a D+/D- wiring problem or a card adapter problem.
Mi adapted BCM94331CD on a cMP 5.1 was recognized immediately (both WiFi and BT working), without any need to disable SIP.
The only problem I have now is very low BT signal, especially with Bluetooth MIDI instruments.
 
Last edited:

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
Continuity & Handoff are working for me in the release version of Mojave. I have an updated wifi card with bluetooth, but I haven't installed CAT or did anything else.
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Continuity & Handoff are working for me in the release version of Mojave. I have an updated wifi card with bluetooth, but I haven't installed CAT or did anything else.

If it's an update from the previous OS, the patch seems will carry on.

All my HDMIAudio, Handoff, NativeScreenBrightness... continue working after upgrade from 10.13.6 to 10.14.
 

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
Unlike MisterAndrew's system, my High Sierra was patched by CAT.

Just want to share how I make Handoff work properly on my cMP after upgrade from 10.13.6 to 10.14.0 (official release).

I upgrade from HS which ran CAT before. So, the system was patched.

And if I run CAT again (after upgrade to Mojave), it will say all functions are already activated. However, it’s not really 100% working (from Mac to iDevice work, but not the other way around).

Then I check the SystemParameters.plist inside IOBluetooth.framework, which indicated that Mac-F221BEC8 ContinuitySupport is false. Most likely the OS update reverted this argument.

Therefore, I set the argument to true by

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

and reboot.

Then, wait for a few minutes. Handoff work in both direction again now.

Handoff.jpg
 
Last edited:
  • Like
Reactions: crjackson2134
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.