casasian.blogg.se

However, I did not want to unload rcd completely, as I need it to control other applications such as QuickTime. In most cases, unloading the rcd launchd job is probably the best answer, see: Remeber to turn on System Integrity Protection again!

The Music App should be able to be used again. Sudo chmod 755 /System/Applications/Music.app/Contents/MacOS/Music Remember to turn off System Integrity Protection in advance and mount your drive writeable as stated above. You can revert this change simply by giving the system the rights back to read, write, execute the Music App. Now, connecting your bluetooth headset won't start the Music app.īut you have to turn System Integrity Protection on again: Sudo chmod 0 /System/Applications/Music.app/Contents/MacOS/Music Now that the filesystem is writable, you can revoke all rights on Music to prevent it from being opened. This is non-permanent, after a reboot the changes are discarded. Open Terminal in Utilities Menu and enterĪfterwards you have to mount your drive with write access because the apple applications are read only. At first you need to disable the System Integrity Protection.īoot in recovery mode (hold ⌘ + R until apple logo appears) Since apple introduced some security mechanisms, some things have to be done in advance. You won't be able to use it afterwards, so only do this if you do not need the Music app. I did some research and found a way to disable Music. Sudo chmod 755 /System/Library/CoreServices/rcd.app/Contents/MacOS/rcdįor MacBook Pro 16" and macOS 10.15.3 all solutions did not work.

To stop rcd from even being started by any app. Sudo chmod 000 /System/Library/CoreServices/rcd.app/Contents/MacOS/rcd With -w option the change should be persistent. Your volume keys should continue working, but things like play key (or bluetooth) auto-starting iTunes should stop. This should stop rcd from being launched by OSX. Launchctl unload -w /System/Library/LaunchAgents/ To disable this behaviour (minimal loss of functionality, possibly your apple remote won't work), use the following two commands: It has hard-coded list of actions to do when it detects certain "events" - one of them being connecting to a bluetooth headset. On OSX, the "RCD" (remote control daemon) is responsible for the naughtiness.