Timeline for What Kernel extensions should be deleted to disable bluetooth?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2022 at 5:46 | comment | added | William Isted |
For anyone on Monterey having issues with lag due to bluetooth, disabling the two com.apple.bluetooth* appears to resolve resolve the issue. Obviously with bluetooth not being functional. Note: Bluetooth preferences panel is still visible.
|
|
| Aug 6, 2019 at 3:19 | comment | added | user3.1415927 | I appreciate the detail in your comments, as well as the comparison of the two approaches. I recommend adding the information to your answer, as I found it helpful and educational, and other users may also benefit. | |
| Aug 5, 2019 at 17:48 | comment | added | Prado | Considering it is necessary to remove the kernel extensions, it depend of MacOS version. I checked it now on two systems: Catalina and El Capitan, they a different. You can see all the responsible exten for bluetooth by clicking on the apple logo on the upper left corner of the toolbar, select "About this mac" and press "System Report". Once opened, roll down to item Software -> Extensions. All kernel extensions will be listed making it easy to find the bluetooth extensions & their path/filenames. Catalina has 7, El Capitan has just 4. This is the best place to find them all. | |
| Aug 5, 2019 at 17:36 | comment | added | Prado | It is a different approach than deleting/moving the kernel extensions. Here I am disabling the bluetooth system service. The final result is no bluetooth. Once disable [by renaming] it is impossible to load it again (unless rebooting in recovery and renaming back those files). If you prefer you can also delete them. Your approach to delete the kernel extension is more agressive, you remove the driver from the kernel. Unless you need to wipe it for some reason, disabling the services is less agressive and more safe to keep system stability. | |
| Aug 5, 2019 at 16:48 | comment | added | user3.1415927 | Will this disable it to the same extent that we're moving the current extension will? | |
| Aug 5, 2019 at 16:45 | review | First posts | |||
| Aug 5, 2019 at 18:01 | |||||
| Aug 5, 2019 at 16:40 | history | answered | Prado | CC BY-SA 4.0 |