MacOS 13.3 RC (22E252) breaks unlocking with the AppleWatch by using wifi card BCM94360NG and wifi card BCM94360CS2

[anonymous-writer]

I would like to report a new problem that occurs with the latest version 13.3 RC (22E252) of Ventura.

The new macOS 13.3 RC (22E252) breaks unlocking for me with the AppleWatch. Back to macOS 13.2.1 (22D68) fixes the issue. Only on my Lenovo laptop with the BCM94360NG. With the FENVI FW-T919 I don't have the problem and unlocking still works.

The crash may also affect non-AppleWatch users after sleep if they observe this in the console. This is not a BlueToolFixup.kext problem, but it may can fix the problem. If more information is needed I am open to post this.

Crash Report: Termination Reason: Namespace LIBSYSTEM, Code 2 Application Triggered Fault

bluetoothd Crash Report.txt

[anonymous-writer]

Update to macOS 13.4 beta (22F5027f):

Without BlueToolFixup.kext same bluetooth crash as in post 1.

With BlueToolFixup.kext no crash. But unlocking with the AppleWatch still not working. Message on login screen: Bluetooth must be turned on to unlock with the Apple Watch. Go back to the black screen 20 seconds and then the AppleWatch unlocks as usual under 13.2.1.

I'll keep up to date this troubleshooting report and continue to try to solve the problem.

[anonymous-writer]

13.3.1 (22E261) unfortunately did not fix the panic. Different hardware, but I think the same problem. https://github.com/OpenIntelWireless/IntelBluetoothFirmware/issues/433

[anonymous-writer]

Would like to add more experiences.

In the meantime I changed the BCM94360NG to BCM94360CS2 by using an NGFF adapter. Card runs perfect and I also have now TX rate up 867 MBits/s. However, the unlocking problem still exist after MacOS 13.3 RC. Previously versions of OSX have no problems also with this card.

Interesting is the fact that deactivating the webcam via the USB port solves the problem. Unlocking with AppleWatch is then back to 100%. As soon as I activate it again, an unlock is no longer possible. It is also interesting that without the Webcam and without BlueToolFixup.kext there are no more bluetoothd crashes.

I'm thinking this is an USB power problem. But I don't have any other ideas at the moment to solve this problem. Maybe someone has an idea what to test.

[topiga]

Have you mapped your usb ports and controllers ?

[anonymous-writer]

Mapping and Power for usb ports is made according to the current state of knowledge, Works up to 13.2.1 without problems. SSDT-USB-S145-15IIL.zip SSDT-EC-USBX-LAPTOP.zip

I know from other Hackintosh user that they have exactly the same problems. The AppleWatch shows problems directly, because of that unlocking occurs very early.

[topiga]

Please reset the nvram twice. After that, try. If it’s not working, please boot in safe mode an tell me if it’s still there

[CobanRamo]

I have the same problem here, since 13.3 it doesn't work anymore, at least not reliably anymore. It is not not hardware dependent, it no longer works on an MSI desktop (CometLake), Lenovo (Icelake), Dell (KabyLakeR). The new build from 13.3 has significant problems with Wifi & Bluetooth.

[topiga]

Multiple questions :

• Is « DisableIOMapper » true or false ?
• Have you patched your DMAR table ?
• Is AppleVTD in your ioreg ?
• Do you have more than 16GB of RAM ?

[CobanRamo]

We have already tested this in all variations. With VT-d, DMAR Table disabled and patched, with AppleVTD. Without VT-d, original DMAR Table, without AppleVTD. I myself have different computers here, MSI, Lenovo, Dell, with different RAM sizes, etc.

All computers up to 13.2.1 have no problem with it, works without any problems. From 13.3 the problems start.

Believe me, we've been testing it for 2 weeks. Do you have an iWatch? if so, you can test it right away. It's as if the Bluetooth & Wifi chip wasn't ready to use right away, it takes up to 1-2 minutes for the devices to be ready in the login screen, you can sometimes use the ESC button to go back to the black screen and ESC again for a new unlock trigger, sometimes it works but 95% of the time it doesn't work anymore.

[anonymous-writer]

I've made some progress with unlocking AppleWatch. If I correct the address for PCI in DMAR as in the attached file, unlock works 75% without any DMAR quirks. If unlock does not work, there is now a different error message. Also attached. So the problem is partially solved but not 100%.

Thread 10 Crashed:: Dispatch queue: com.apple.root.utility-qos 0 libsystem_kernel.dylib 0x7ff8056aa1f2 __pthread_kill + 10 1 libsystem_pthread.dylib 0x7ff8056e1ee6 pthread_kill + 263 2 libsystem_c.dylib 0x7ff805608b45 abort + 123 3 bluetoothd 0x10826e5dc 0x107dee000 + 4720092 4 bluetoothd 0x1080c128a 0x107dee000 + 2962058 5 bluetoothd 0x1080c117e 0x107dee000 + 2961790 6 libdispatch.dylib 0x7ff805541033 _dispatch_client_callout + 8 7 libdispatch.dylib 0x7ff805543b65 _dispatch_continuation_pop + 463 8 libdispatch.dylib 0x7ff8055557af _dispatch_source_invoke + 2184 9 libdispatch.dylib 0x7ff805550fa2 _dispatch_root_queue_drain + 343 10 libdispatch.dylib 0x7ff805551768 _dispatch_worker_thread2 + 170 11 libsystem_pthread.dylib 0x7ff8056dec0f _pthread_wqthread + 257 12 libsystem_pthread.dylib 0x7ff8056ddbbf start_wqthread + 15

DMAR.dsl.zip

bluetoothd_Crash.txt

https://bitbucket.org/anonymous_writer/lenovo-ideapad-s145-15iil-opencore/src/master/

[anonymous-writer]

Unfortunately I could not solve the problem until now. Also macOS 13.4 RC doesn't change anything. As soon as I activate the webcam via the USB port, unlocking via the watch only works randomly. The last version where unlocking still worked was version 13.2.1. Always the same problem. bluetoothd crashes with the error message from post 1.

I also have Monterey running on the laptop. Unlocking works 100% there even with an activated webcam. The Opencore EFI folder used is exactly the same as on Ventura.

I've tried a lot to solve the problem. Now I'm running out of ideas what else to test. Maybe someone has a new idea.

[m0d16l14n1]

Hey, guys! I think you should check Ventura 13.4

[anonymous-writer]

Unfortunately doesn't change anything. With webcam activated via USB, unlocking only works according to the random principle.

Back to 13.2.1 Unlock work.

[m0d16l14n1]

Unfortunately doesn't change anything. With webcam activated via USB, unlocking only works according to the random principle.

Back to 13.2.1 Unlock work.

Hm, gotcha, thanks. Did you check that quirk? Maybe that one will help? (you need to patch DMAR with removing reserved memory regions)

[anonymous-writer]

This qurik has already been tested. No change. A separate DMAR with a different address range works best. This works for me to unlock sometimes. Removing the address range completely doesn't help at all.

Thanks for the information.

[Lorys89]

Have you solved it? Try this solution https://www.macos86.it/topic/6360-fix-bluetoothairdrop-after-wake-from-sleep/?tab=comments#comment-141461