[ enhancement ] prompt to turn off built-in Bluetooth at launch

[EricPSmith]

Hi folks,

Excited about getting Continuity, and particularly new AirDrop, working on my MacBook Pro late 2011. This tool looks amazing, and promises to make it really easy!

Bought GMYLE Bluetooth 4.0 LE dongle, launched CAT 2.0.0, selected Activate Continuity, and plugged in dongle at prompt. Script stayed put at prompt, without detecting dongle, and fan gradually spun up.

Reading other threads eventually revealed that built-in Bluetooth needs to be turned off before running CAT. Would be really helpful to check whether built-in Bluetooth is on at start of script and, if needed, prompt user to turn that off before proceeding.

Many Thanks!

Eric

[dokterdok]

Hi @EricPSmith,

Thanks for the suggestion and sharing a workaround, there indeed seems to be a dongle detection issue on some Macs. Ideally users shouldn't have to do extra manual steps so I'm looking for a software fix first.

Could you -or anyone who is experiencing this issue and reading this- please help me identify the cause? As I have not yet experienced this on the Macs I've tested CAT 2.0 with, it would help me identify a solution faster.

• Were there any Bluetooth devices paired and in use when the prompt was displayed? e.g.: keyboard, mouse, iPhone, ...
• I've uploaded a beta version of CAT 2.0.1 which includes a potential fix - could you please give it a shot and report back? Please note that I haven't codesigned it yet so you might get a warning or error when launching it (solution here).

[EricPSmith]

Hi dokterdok,

I can confirm that two Apple devices, a keyboard and a trackpad, were paired / connected via Bluetooth when the dongle failed to be detected by CAT, and I had been using those devices to launch CAT and submit commands. In retrospect, it would have made more sense for me to switch to the built-in keyboard and trackpad before starting, since CAT is presumably designed to disable / remove support for the built-in Bluetooth anyway.

At this point, I now have Continuity up and running on my MacBook Pro (details in a separate post here), and cannot reproduce the conditions where this detection issue occurred without undoing it all, which I am reluctant to do.

I must say that I am incredibly pleased to have Continuity, and particularly AirDrop, working on my (slightly) older MacBook Pro. Thank you so much for making this so easy for the rest of us.

Eric