BluetoolFixup: Add another patch to skip Internal Bluetooth Controller NVRAM checking. #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
From Ventura 13.4(maybe), Apple adds two NVRAM check:
bluetoothInternalControllerInfo: which stores the internal Bluetooth controller(always real mac)'s mac address.bluetoothExternalDongleFailed: which to indicates that the bluetoothd had failure initialization with external bluetooth Dongle(Stupid design).original code:
after patched:
these two section are created by bluetoothd self, but if the user clean/reset NVRAM, then the bluetoothd will not treat the device as external Dongle at all, so it is foreseeable that Bluetooth will not be able to be used.
Here I make a patch to skip these two conditions, and seems working so well.