BlueToolFixup has problems with the dw1830 board's BT

[Lorys89]

card in question dell dw1830 the bt on macos 13.4 or even 13.5 b1 does not work and does not activate, the only way to activate it is a warm restart on os monterey and restart again on macos ventura, but if I shut down and cold start macos ventura does not I will have bt and if I start monterey first and then reset nvram and start ventura I won't even have the bt.

I suppose something needs to be fixed on BlueToolFixup.
cc @dhinakg

[nguyentdat23]

Referring to an issue from #OpenIntelWireless/IntelBluetoothFirmware#435, try adding two keys into NVRAM under UUID 7C436110-AB2A-4BBB-A880-FE41995C9F82 like the picture below. I have DW1830 too, after adding these two keys and Reset NVRAM, bluetooth back to work again

[Lorys89]

Referring to an issue from #OpenIntelWireless/IntelBluetoothFirmware#435, try adding two keys into NVRAM under UUID 7C436110-AB2A-4BBB-A880-FE41995C9F82 like the picture below. I have DW1830 too, after adding these two keys and Reset NVRAM, bluetooth back to work again

that fix doesn't work for me.
it works only if I start monterey on another partition and immediately restart and start ventura but when i turn off and start cold ventura i lose the bt

[m0d16l14n1]

Referring to an issue from #OpenIntelWireless/IntelBluetoothFirmware#435, try adding two keys into NVRAM under UUID 7C436110-AB2A-4BBB-A880-FE41995C9F82 like the picture below. I have DW1830 too, after adding these two keys and Reset NVRAM, bluetooth back to work again

that fix doesn't work for me. it works only if I start monterey on another partition and immediately restart and start ventura but when i turn off and start cold ventura i lose the bt

It's won't work on 13.5 beta 1. Working on 13.4 as report in Intel thread. Which version do you have installed?

[Lorys89]

🙈 13.5 b1 Otherwise I do not work the backlighting screen

[Lorys89]

What you are doing is a temporary solution, you definitely need to intervene on the kext.

[m0d16l14n1]

What you are doing is a temporary solution, you definitely need to intervene on the kext.

All the situation with BluetoothFixup (and other stuff) is a temporary and not stable solution.

[Lorys89]

I may have found a temporary solution
using the 2 entries mentioned above in sez nvram and deactivating the 2 kexts

work to macos 13.5 b1

[Lorys89]

I the 2 strings I did not put them in sez nvram because starting partition with monterey remain imprinted, and I avoid resetting nvram

[nguyentdat23]

I may have found a temporary solution using the 2 entries mentioned above in sez nvram and deactivating the 2 kexts !)

work to macos 13.5 b1

Add two keys to NVRAM only made it work for the first time it boot, After I tried uncheck two kexts like what you did and voila bluetooth get back to work. Thanks so much

[gujiangjiang]

zxystd/BrcmPatchRAM@7f22629

Allow Bluetooth to turn on after the first power cycle fixed by @zxystd

[gujiangjiang]

@Lorys89 I delete the 2 kexts in the picture and add 2 nvram data and my bluetooth works but cant scan any bluetooth devices.

[Lorys89]

zxystd/BrcmPatchRAM@7f22629

Allow Bluetooth to turn on after the first power cycle fixed by @zxystd

fixed

with 2 kext active :)
But I do not use the 2 strings in nvram, I remain injected if I boot partition with monterey and keeps them until I reset nvram.

[nguyentdat23]

fixed

with 2 kext active :) But I do not use the 2 strings in nvram, I remain injected if I boot partition with monterey and keeps them until I reset nvram.

Would you mind sharing your built kext with commit from zxystd please ?

[Lorys89]

fixed
with 2 kext active :) But I do not use the 2 strings in nvram, I remain injected if I boot partition with monterey and keeps them until I reset nvram.

Would you mind sharing your built kext with commit from zxystd please ?

https://github.com/zxystd/BrcmPatchRAM/suites/13231677116/artifacts/720906228

[nguyentdat23]

https://github.com/zxystd/BrcmPatchRAM/suites/13231677116/artifacts/720906228

Thanks for sharing. I only checked Release section and didn't even think about checking Action section.