My Bluetooth Transport is being properly set to USB Bluetooth-Spoof.kext (2.6.6 I think - Unfortunately the kext isn't assigned a version).I am loading the following kexts (in this order) with OC 0.9.2: In 13.4, I am unable to reliably turn on BT (sometimes I can toggle the BT slider, but I don't see evidence that BT is actually on) and when I am able to toggle the BT slider, I do not see available pairing devices. In 13.3.1, I was able to turn BT on and off and I was able to pair with an external BT speaker (I didn't test BT beyond external audio). Now, bluetoothd no longer crashes and I noticed that BT firmware is loading properly again.Īfter upgrading from 13.3.1 to 13.4, Bluetooth has stopped working with my BCM94352HMB (SMBIOS MBP6,2). My hack is a Dell Latitude E6410 (NVidia) with SMBIOS Model MBP6,2.ĮDIT: On my HP Envy x360 KabyLake-R laptop (SMBIOS Model MBP15,2), I have installed a BCM94360NG and BlueTooth Transport is reported as USB in Big Sur, Monterey and Ventura (booting with OC 0.8.8 and no BlueTooth kexts).ĮDIT: The addition of bluetoothExternalDongleFailed and bluetoothInternalControllerInfo keys mentioned in this thread combined with deleting /Library/Preferences/ fixed my Ventura 13.4 BT issue. I'm booting Big Sur, Monterey and Ventura with Open Core 0.8.9 and patching with OCLP 0.6.1. Monterey / Ventura: BlueTooth Transport is PCIe Could it be that my BlueTooth Transport is detected incorrectly in Monterey and Ventura because of flawed USB port mapping? Thank you. PCIe? I've tried various combinations of enabling/disabling BluetoolFixup.kext, BlueToothSpoof.kext and BluetoothInjector.kext and in every case, my BCM94352HMB BlueTooth Transport is reported as USB in Big Sur (where my BlueTooth works perfectly) and is reported as PCIe in Monterey and Ventura where my BlueTooth does not work (I am not able to turn it on). Is someone able to explain the logic that determines whether the BlueTooth Transport is reported as USB vs. the specific Bluetooth chipset you have.If you are experiencing issues with Bluetooth on Monterey, please post here (do not create a separate issue) and make sure to include: Certain checks cause bluetoothd to take different codepaths which may or may not be supported for the specific chipset.With Beta 10, any vendor that is not Broadcom or CSR is ignored.bluetoothd now has several checks that raise issues.Specifically seen to break power cycling BCM20702 (non-PatchRAM) on legacy Macs.Even though it does not affect the transport type anymore, setting transport-encoding still has adverse effects for unknown reasons.Transport type is also dependent on SMBIOS in some cases ( ref).transport-encoding no longer works to change the transport type.Recent betas have broken the approach BlueToolFixup used to enable Bluetooth for non-native Broadcom and Intel chipsets. As detailed in #1669, Apple has been actively working on the Bluetooth stack in macOS Monterey.
0 kommentar(er)
