Closed Andrej-Antipov closed 2 years ago
After 'dirty hack' the continuity works because the IOBluetooth.kext has patched in the normal installation.
But ./contitool.sh -f still aborted yet anyway - needs fix in the script.
Now full discribe. On mainboard I isolate some pins of the combo wifi+bt connector to power off internal bluetooth After that the variable bluetoothInternalControllerInfo disappears from PRAM and I manually add it value into PRAM The CAT normal Installation won't work with this because don't find a dongle is plugged in. And I used the ./contitool.sh -f command to force this issue. It worked on 10.11 - 10.13 but in 10.10 it is not work because Normal Installation in Yosemite looks that After that we see no handoff After my 'dirty hack' installation OK And handoff is ok, and the PRAM variables set OK But if the ./contitool.sh -f worked as expected it would not have to do this dirty hack with my respect
Please include the following information.
Steps done to try to fix the issue:
I used a dirty hack and made a change in the script contitool.sh in section
Silent helper funcition that determines whether patching the file is appropriate
I changed the last 'echo' = '0' to '1'
if [ "${lmpVersion}" == "6" -a "${donglePresent}" == "1" -a ! -z "${brcmKext}" -a ! -z "${patchableFileOutput}" ]; then
check ok, go ahead with the patching
And the IOBluetooth.kext patch done anyway with normal installation of CAT But it is not good.
And yet I changed the section
Verifies if a USB Bluetooth dongle is active by comparing the internal Bluetooth controller info with the active Bluetooth controller info. ...
....
return the dongle status
in the last string changed '!=' to '==' don't ask me to confirm usb dongle... but it's never mind