Hi
@CaseySJ,
I recently updated my PC to macOS Ventura, and I want to share my experience as a success story, but with some recent problems.
A bit background; I had problems with the Bluetooth (BCM94360CS2 with PCIe adapter) since updating to Monterey and practically Bluetooth was useless. I'm using Ethernet to connect to the Internet so Wi-Fi and Bluetooth was turned off most of the time, except when I needed. Bluetooth problems were basically that the Magic Keyboard couldn't wake the PC. Most of the time, after the wake, Bluetooth processes were going crazy until they were disabled, and enabled again. (I wrote about these in January and February.) Another "problem" was that I didn't really listened to the recommending against buying Samsung 870 EVO Plus M.2 NVMe, and the boot time increased with each OC + macOS update, from 40 seconds to well over 2 minutes. This was annoying to say the least.
Solutions: I came to my senses and bought WD SN850 M.2 NVMe SSD. Instead of using HackinDROM app to update the current OC config, I started from a good base, 0.8.6 EFI + Config, the one you shared in this thread. Unfortunately & fortunately this was an Intel WiFi config. So I had to research this thread, and some other forums on the Internet to understand which ones I definitely need, and which ones I should try if there is any problem. So I created a Broadcom version of that Config (just check/uncheck of kexts and drivers, basically). I did a complete fresh install on the new SSD. I didn't installed the Broadcom card before the installation process is done, and the machine works as expected after that I installed the Broadcom. The result is that Broadcom BCM94360CS2 works flawlessly with ALL continuity features working (including Contiunity Camera, Contiunity Markup/Sketch, AirPlay, AirDrop, Handoff, Universal Clipboard, SMS, Phone etc., the ones I could test. Unfortunately I don't have an iPad to test the Sidecar, nor i have an Apple Watch to test the Unlock feature, though I believe these will work as well.).
There is one "trick" or "flaw" to wake process though. When I press a key on Magic Keyboard, hardware immediately wakes but it takes 30 seconds for the display to be enabled. This also happens only after the monitor tries to go idle because there is no signal is coming. If I press a key at this point, in 1-2 seconds the display turns on. I can totally live with that. I think this is normal? (It wakes from the sleep without the need to connect the keyboard to USB. I'm totally fine with 30 seconds waiting.)
Now to problems... So i have the "new" setup since some days and especially today somehow problems started to arise:
1) I have a USB-C webcam (Logitech Streamcam) and even though FaceTime can show the camera everytime, Logitech G Hub doesn't and i need to hotplug the usb-c cable, and after that it works as expected. I'm not sure if this is related with Thunderbolt, although it's not a TB device, it's using the TB/USB-C ports.
2)
EDIT: I just thought about doing a Cold Start (turning of the PSU, then disconnecting the power cable and reconnecting, turning on PSU, then boot) and it starts to function like expected. I hope this was a temporary hicup, but looks like the problem is solved by itself (Magic Keyboard + Trackpad works with BIOS, OC, Windows and macOS). Magic Keyboard and Magic Trackpad was working the last days from boot/BIOS, to Windows login, and to macOS login. This evening somehow it stopped working, i tried many times but no avail the devices are not recognized/usable in BIOS + boot. Also the bluetooth stopped working with Windows 10 but it works as expected in macOS after I login. To be able to login and boot into BIOS, I must use the USB cable with the magic keyboard. This is very annoying, I have no idea why it was working and now it doesn't? This is my biggest problem with the setup right now, and I'm dedicated to solve it. I don't think this is anyway related to OpenCore, kexts or anything macOS related as the BCM94360CS2 bluetooth stopped working in Windows 10 as well and magic keyboard was working over bluetooth before OpenCore even loaded (so even if I get any other keyboard or Magic Keyboard 2, i suppose that problem will continue. I think it's related with the BCM card + adapter somehow). Do you have any idea how to solve this? I will try CMOS reset tomorrow, i can only think of this as a solution, I looked all the BIOS settings but either I overlooked at something or there is nothing to see (BIOS is not in fast-boot).
When I started to write this message in the morning there were no USB-C or Bluetooth problems, and I was planning to write this message as a success story and I was planning to share the modified 0.8.6 config + EFI (for Broadcom + AMD GPU), and I will do this just as an example for other people but first I want to solve this Bluetooth on boot problem.
(I'm really sorry for the huge wall of text, I just wanted to be as clear as possible. It goes without saying that I'm in awe of your service to this community, replying thousands of messages almost daily for the last 4 years. Thank you, you are the reason many people jumped into this experiment, me including.)