Repository navigation
Fixes bluetoothd crash-looping, which shows up as Bluetooth turning itself off and on and devices failing to connect.
Fix
- The
bluetoothd/BlueToolpatches are written into the file's page cache. On macOS 26 those binaries are APFS-compressed on the sealed system volume in 64 KB chunks whose hash is checked on every pagein. When a patched page stayed in memory while a neighbouring page of the same chunk was evicted (more likely under memory pressure), the pagein failed (compressed data hash mismatch),bluetoothddied withSIGBUSand launchd restarted it over and over. Upstream BlueToolFixup works the same way and has the same problem. - The kext now hooks
vnode_pageinand evicts the chunk's patched pages before the pagein. They are re-read and re-patched the next time they are used. - New boot-arg
-ibtnoevictturns this off, for diagnosis only.
Downloads
IntelBTUnified-1.0.1-AX210.zip: AX210/AX211 firmware only (≈0.6 MB).IntelBTUnified-1.0.1-full.zip: every firmware (≈11 MB).
Status
- Tested on an Intel AX210 (
8087:0032) with macOS 26.7.3 (Tahoe) and Lilu 1.7.3: no morebluetoothdcrashes, and headphones connect. The failing pagein that used to crashbluetoothdwas reproduced before the fix and no longer fails with it. - Everything else is as in 1.0.0: the other chips and macOS 12 – 25 are untested, and the kext is unsigned. Keep the previous kext so you can roll back.
Upgrading
Replace EFI/OC/Kexts/IntelBTUnified.kext with the one from the zip and reboot. config.plist does not change. Check with kextstat | grep IntelBTUnified that version 1.0.1 is loaded.