josh anderson

Hi MaLd0n, I have another question regarding Bluetooth stability. I’m currently using a BCM94352Z and the Bluetooth experience is very poor. This is what macOS reports: Controller: Address: 18:4F:32:F4:4C:52 State: On Chipset: THIRD_PARTY_DONGLE Firmware Version: v8718 c5876 Transport: UART The main problem is real-world usage: I have to stay within ~1 meter or devices disconnect Frequent audio cuts and instability Very unreliable with AirPods and headsets It’s basically unusable for daily use. Because of this, I’m considering switching to Intel AX210. In your experience: How stable is Bluetooth on AX210 in macOS Tahoe? Is it good enough for daily use (headphones, audio, etc.)? What is the best setup for AX210 on Tahoe (kexts, config, etc.)? My goal is stable WiFi + Bluetooth without using OCLP. Thanks.

Hi MaLd0n, I’m looking for a WiFi/Bluetooth card recommendation for macOS Tahoe (26). My priorities are: Maximum stability on Tahoe No OCLP or root patches (I want full SIP and SecureBoot enabled) Best possible Bluetooth performance for daily use I don’t care about AirDrop, Continuity or any Apple ecosystem features. From what I’ve researched, AirportItlwm doesn’t work on Tahoe and only itlwm + HeliPort is usable (GitHub), so I’m considering Intel cards like AX210. In your experience: Which card is currently the most stable on Tahoe without OCLP? Is AX210 still the best option, or is there something better now? Which setup gives the most stable Bluetooth for daily usage? Thanks.

Hi, I have a technical question regarding Intel AX210 compatibility on modern macOS versions. I’m currently using a BCM94352Z, but it has become increasingly unstable on macOS Sequoia, and I’m planning to upgrade to macOS Tahoe. Because of this, I’m considering switching to an Intel AX210 for better long-term stability. I’d like to clarify a few points: Is the Intel AX210 fully functional on macOS Tahoe (26) using AirportItlwm? Is the boot argument -ibtcompatbeta strictly required for Bluetooth on Tahoe? How stable is Bluetooth with IntelBluetoothFirmware in daily use? Between AirportItlwm and itlwm + HeliPort, which setup is currently more reliable on Tahoe? Are there any major limitations (e.g., AirDrop, Handoff, Continuity features) when using AX210 on these newer macOS versions? My main goal is achieving stable and consistent WiFi + Bluetooth performance for daily usage. Thanks in advance.

Someone? help!

HP Pavilion 14 AL001LA – Intel i5-6200U – Sequoia Test Update macOS Version: Sequoia (not Monterey) Graphics: Intel HD 520 (Kaby Lake simulation applied, 00001B59) HDMI / DisplayPort Tests: IORegistryExplorer shows: AppleIntelFramebuffer@0 → connector type: 02 00 00 00, display pipe: 00 00 00 00 AppleIntelFramebuffer@1 → connector type: 08 00 00 00, display pipe: ff ff 00 00 AppleIntelFramebuffer@2 → connector type: 04 00 00 00, display pipe: ff ff 00 00 Manual framebuffer patches applied (pipe / bus / type / flags) following Dortania / WEG guide: framebuffer-patch-enable: 01000000 framebuffer-con1-enable: 01000000 framebuffer-con1-index: 01000000 framebuffer-con1-busid: 01000000 framebuffer-con1-pipe: 01000000 framebuffer-con1-type: 08000000 framebuffer-con1-flags: 00000000 framebuffer-con2-enable: 01000000 framebuffer-con2-index: 02000000 framebuffer-con2-busid: 02000000 framebuffer-con2-pipe: 02000000 framebuffer-con2-type: 04000000 framebuffer-con2-flags: 00000000 Result: HDMI still shows pipe ff ff 00 00; no signal on monitor. LSPCON / HDMI 2.0 compatibility not verified; likely required if using HDMI 2.0. Suggested next step: Confirm if this laptop uses LSPCON for HDMI 2.0. If yes, try: enable-lspcon-support: 01000000 framebuffer-con1-has-lspcon: 01000000 framebuffer-con1-preferred-lspcon-mode: 01000000 Bluetooth Status (Sequoia): Chipset: Third-Party Dongle (BCM20702A0) Driver: AppleUSBXHCISPTLP Address: 18:4F:32:F4:4C:52 Firmware: v8718 c5876 Maximum range: <3 meters Connected devices: AirPods Pro 2, TG-184 headphones Transport: UART Manufacturer ID: 0x004C (Apple) USB Devices: USB 3.0 Bus – PCI IDs: 0x9d2f / 0x0021 / Vendor: 0x8086 Bluetooth Adapter BCM20702A0 – Vendor 0x0a5c / Product 0x6417 – Integrated – Max 12 Mb/s HP Wide Vision HD Camera – Vendor 0x04f2 / Product 0xb56d – Integrated – Max 480 Mb/s USB Receiver – Vendor/Product 0x1919 – Max 12 Mb/s Notes / Observations: macOS Sequoia requires Kaby Lake spoofing for proper graphics support. HDMI channel assignment fails even after applying patches; likely due to HD 520 + Kaby Lake framebuffer layout mismatch. Bluetooth works but has very limited range (<3 meters), much worse than on Ventura. AirPods disconnect quickly, AirDrop partially works. Wi-Fi restored successfully via OCLP + BCM94352Z patch. All USB devices are detected and powered correctly. Questions for the community: Does anyone know if HP Pavilion 14 AL001LA uses LSPCON for HDMI 2.0 output? Any suggestions to fix HDMI pipe assignment on Sequoia? Is there a recommended fix for the extremely limited Bluetooth range in Sequoia? Thanks for the reply. I checked my framebuffer connectors in IORegistryExplorer. My connectors appear as: Framebuffer@0 → eDP → connector-type <02000000> → pipe <00000000> Framebuffer@1 → HDMI → connector-type <00080000> → pipe Framebuffer@2 → DP → connector-type <00040000> → pipe Internal display works correctly but HDMI does not output signal. It looks like HDMI and DP connectors are not getting a valid pipe assignment. Is this likely a framebuffer layout mismatch for Skylake HD520 on macOS Sequoia? Help me mald0n. i use this pc for my school and work 😭

Thanks for the reply. I checked my framebuffer connectors in IORegistryExplorer. My connectors appear as: Framebuffer@0 → eDP → connector-type <02000000> → pipe <00000000> Framebuffer@1 → HDMI → connector-type <00080000> → pipe Framebuffer@2 → DP → connector-type <00040000> → pipe Internal display works correctly but HDMI does not output signal. It looks like HDMI and DP connectors are not getting a valid pipe assignment. Is this likely a framebuffer layout mismatch for Skylake HD520 on macOS Sequoia?

Hi! As I mentioned in a previous post about macOS Tahoe, I said in my last message that I had created an EFI for macOS Sequoia and would use OCLP to restore Wi-Fi (since my BCM94352z chipset is the only limiting factor for macOS Sequoia, and thanks to OCLP it's fixed). The problem is that now I don't have HDMI working, and I need it because I use a second monitor and a TV. I study and work with my Hackintosh and enjoy streaming occasionally, but with this problem, I haven't been able to use the other monitors. The root patch with OCLP was successful, and I have Wi-Fi, but when I modify anything in my EFI, I lose Wi-Fi immediately and have to patch again and reset NVRAM in OpenCore Booter. I've tried different bootargs and adding the FRAMEBUFFER PATCHES to NVRAM, but I still haven't been able to enable HDMI. Another problem I have is that before, with macOS Ventura, Bluetooth had a much better range of up to 10 meters. (AirPods Pro 2) but now it's ridiculously worse. After taking two steps away from my laptop, the Bluetooth becomes unreliable, and on the third step, the AirPods disconnect. AirDrop only works partially; I can receive from my iPhone to my laptop, but when I send, no devices appear (which I desperately need, and the AirPods too). If anyone else has this problem, please help! I need to be productive again. Thanks!

I created an EFI for macOS Sequoia using the BCM94352Z Wi-Fi/Bluetooth card. I also prepared a USB drive with all the required resources (OCLP installer, kexts, and tutorials) to apply the root patch after installation. Before proceeding with the installation, I wanted to share my EFI and IOREG files so someone with more experience could review them and tell me if everything looks correct or if there is anything I should fix or improve. For now, I plan to stay on macOS Sequoia and wait at least 6 months before considering an update to macOS Tahoe. I am currently downloading macOS Sequoia 15.7.4 (24G517). Any advice or feedback would be greatly appreciated. EFI + IOREG: https://drive.google.com/drive/folders/1ogQ21ClR87YahY-3rF1ze-K2HycTk6Tn

Hello, im in macOS ventura an i want to update to the newest version of macos, but i my unic limitation is this that is only support natively in macos ventura an - can i install macos tahoe with this card? what configurations i will need? and, if i not can install tahoe, how i will install sequoia with this card?

What WiFi card do you recommend for my laptop with an NGFF M.2 Key A/E slot to have native WiFi and Bluetooth support in macOS Sequoia and Tahoe, including full Continuity (AirDrop, Handoff, AirPlay, etc.)? If there is no fully compatible card for my port type, would you recommend using an adapter instead? Please recommend me the best option, MaLd0n 🙏

I have a question regarding the BCM94352Z on macOS Sequoia. Since official support was removed after Ventura, I understand that OCLP root patches are commonly used to restore WiFi functionality. However, I would like to know if it is possible to use AppleBCMWLANCompanion.kext with VT-d enabled in order to avoid applying root patches. Is there a way to inject the proper Device ID and use AppleBCMWLANCompanion.kext (with AirportBrcmFixup if needed) so that WiFi works without relying on root patches? The goal is to keep the system as close to stock as possible and simplify future updates. Has anyone successfully achieved this configuration on Sequoia? Any clarification or guidance would be greatly appreciated. Thank you.

Hello, I’m planning to upgrade from macOS Ventura to macOS Sequoia and I would like to know if the BCM94352Z (DW1560) can be fully enabled with working WiFi, Bluetooth, and Continuity features (AirDrop, Handoff, AirPlay, etc.) in a stable way. Is it currently possible to achieve full functionality on Sequoia? If so, could someone explain the required kexts, patches, and configuration (OpenCore settings, spoofing if needed, etc.)? Any guidance or detailed explanation would be greatly appreciated. Thank you in advance.

Hi MaLd0n, I just wanted to sincerely thank you for your help. Your EFI worked perfectly — macOS boots without issues and WiFi and Bluetooth are 100% working. No more IOKit daemon stall, no pxsx problem anymore. I was really stuck for days, and your clean EFI made all the difference. I truly appreciate the time and effort you put into this. I also want to be honest and say that I’m just a 15-year-old student doing Hackintosh on my own laptop. As soon as I’m able to get some money, I promise I will make a donation to Olarila to support your work and the community. I’m very happy with the result. If you recommend any post-install steps or tweaks, I’d really appreciate your advice. If anything else is needed from my side, I’ll gladly reply in the thread. Thank you again for everything ❤️ Best regards.

https://drive.google.com/file/d/1VCwDgdErdYMj_njX5Z2dSXVmmMtwHOfU/view?usp=sharing, https://drive.google.com/file/d/1nvayc3wPIL1WVx85OGrQCdGY4E0a9ocB/view?usp=sharing, https://drive.google.com/file/d/1qNa7Bom09n0kUFAjb-hj-ZJiVVg6ytct/view?usp=sharing Hi MaLd0n, thanks for your reply. I’m attaching: - My EFI folder - An IOREG captured WITHOUT Broadcom kexts loaded Unfortunately, I cannot provide an IOREG with Broadcom enabled because the system never reaches the desktop. As soon as AirportBrcmFixup.kext (even alone) is loaded, the boot stalls at: IOKit daemon stall (60s): "pxsx" So the IOREG I’m providing is from a successful boot without any Broadcom kexts. Please let me know if this is sufficient to analyze the PCI / PXSX issue on this HP Pavilion. Thanks in advance for your time.

Hi MaLd0n, thanks for the reply. Just to clarify, I’m already using BlueToolFixup.kext, BrcmFirmwareData.kext and BrcmPatchRAM3.kext, with the correct loading order, as detailed in my post. I’ve also tested fresh downloads from official Acidanthera releases. The issue is not Bluetooth-related. The system stalls with “IOKit daemon stall (60s) ‘pxsx’” even when only AirportBrcmFixup.kext is loaded, with no BT kexts at all. Without any Broadcom kexts, the system boots perfectly. This points to a PXSX / PCI bridge initialization issue on this HP Pavilion when Broadcom kexts are present, rather than missing or misconfigured Bluetooth kexts. If you’ve seen a similar pxsx stall on HP hardware or have insight into a PCI/ACPI-level workaround, I’d really appreciate your input. Thanks.