0

I've got an early 2011 MBP with an upgraded AirPort card. I know that one has to jump through kext- and Terminal-based hoops to enable Continuity, but I also know that Continuity Activation Tool does the entire process at the press of a button. The one problem is that whenever I install a software update or reinstall Yosemite, it undoes the Continuity-enabling process.

My question: Is there a way to make the Continuity-enabling process automatically run after every update/reinstall?

Improve this question
4
  • Looking at the GitHub, it's basically a packaged script. You could create a launch agent to run it at login, but I presume you need to restart after running the tool?
    – Sera H
    Commented Dec 27, 2014 at 9:40
  • Yeah, it requires a restart to start working.
    – user24601
    Commented Dec 27, 2014 at 15:41
  • 1
    Then I guess you'd have to write a script that checks at boot for the changes effected by the tool and, if they aren't found, runs the tool and reboots.
    – Sera H
    Commented Dec 27, 2014 at 20:46
  • I know that one of Continuity Activator's features runs a check, but I don't really know how to write scripts like that...
    – user24601
    Commented Dec 28, 2014 at 1:40

1 Answer 1

Reset to default
2

Continuity Activation Tool author here.

Writing an additional script and tweaking CAT's script would be necessary as the tools' activation feature isn't currently designed to run automatically and silently. Stuart H's suggestion points you in the right direction IMO.

Functionality I'd include in a boot time script:

  1. Detect if one of the IOBluetoothFamily.kext or IO80211Family.kext drivers, located in /System/Library/Extensions/, pass code signature validation (with Apple's codesign command line utility). If one or both of them do, they likely have been updated/replaced by an OS X update and need to be re-patched: the script can proceed.

  2. Rename any KextsBackupBeforePatch and KextsBackupAfterPatch folders in the user dir to avoid any "overwrite files" prompt during the activation.

  3. Run contitool.sh -a with admin privileges to activate Continuity from the command line. Catch and log CAT's output in a file: in case of failure you may want to know what happened.

Additionally, I'd modify the rebootPrompt() function of contitool.sh to restart the system automatically. You could also add a popup asking or warning the user about the reboot on top of that, e.g. through Apple Script (osascript command line utility).

Last but not least: Apple may release an OS X update anytime that breaks the methods used by this tool to activate Continuity. So far this hasn't been the case - but risks of issues with your system are increased if you automate the activation right after an OS X update.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .