github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #46] Keep MonitorControl from asking for Accessibility Features everytime #43

New issue

Closed

opened 2026-05-05 04:50:15 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 04:50:15 -06:00

Owner

Originally created by @carlosfilhoadm on GitHub (Aug 16, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/46

Originally assigned to: @the0neyouseek on GitHub.

First of all, thank you so much for this app. I looked for something like this for a long time!
Since I had no idea about DDC/CI, all options that I could find involved installing virtual sound devices and things like that.
They did solve the problem, but were more complex to install or weren't free.

I use it to control sound volume of my external monitor connected through DisplayPort, and the native volume keys on Apple's wireless keyboard work fine with the app, so there's no need to grant Accessibility Features to it. But it keeps asking for granting every single time it's launched.

Is there another way to stop these requests?

Originally created by @carlosfilhoadm on GitHub (Aug 16, 2018). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/46 Originally assigned to: @the0neyouseek on GitHub. First of all, thank you so much for this app. I looked for something like this for a long time! Since I had no idea about DDC/CI, all options that I could find involved installing virtual sound devices and things like that. They did solve the problem, but were more complex to install or weren't free. I use it to control sound volume of my external monitor connected through DisplayPort, and the native volume keys on Apple's wireless keyboard work fine with the app, so there's no need to grant Accessibility Features to it. But it keeps asking for granting every single time it's launched. Is there another way to stop these requests?

gitea-mirror

2026-05-05 04:50:15 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 04:50:25 -06:00

Author

Owner

@vogtmh commented on GitHub (Sep 15, 2018):

I had the same hickup when first installing MonitorControl and solved it:

go into Settings --> Security --> Privacy --> Accessibility
Remove MonitorControl from there (click on it and use the Minus Symbol, NOT deselect)
Restart your Mac
Start MonitorControl and confirm the use of accessibility
Restart again (just to be sure)

Now everything should be fine :-)

@vogtmh commented on GitHub (Sep 15, 2018): I had the same hickup when first installing MonitorControl and solved it: 1. go into Settings --> Security --> Privacy --> Accessibility 2. Remove MonitorControl from there (click on it and use the Minus Symbol, NOT deselect) 3. Restart your Mac 4. Start MonitorControl and confirm the use of accessibility 5. Restart again (just to be sure) Now everything should be fine :-)

gitea-mirror commented

2026-05-05 04:50:29 -06:00

Author

Owner

@carlosfilhoadm commented on GitHub (Nov 26, 2018):

Thank you, but it didn't work.

I'll try your version (ScreenVolume2).

@carlosfilhoadm commented on GitHub (Nov 26, 2018): Thank you, but it didn't work. I'll try your version (ScreenVolume2).

gitea-mirror commented

2026-05-05 04:50:31 -06:00

Author

Owner

@the0neyouseek commented on GitHub (Jan 10, 2019):

Hi @carlosfilhoadm sorry for the delay responding.

Accessibility features are required for the app to be able to listen to key input all the time.

Even though, the app should only be prompting you once to enable this, I'll fix this soon.

@the0neyouseek commented on GitHub (Jan 10, 2019): Hi @carlosfilhoadm sorry for the delay responding. Accessibility features are required for the app to be able to listen to key input all the time. Even though, the app should only be prompting you once to enable this, I'll fix this soon.

gitea-mirror commented

2026-05-05 04:50:34 -06:00

Author

Owner

@JoniVR commented on GitHub (May 8, 2019):

You definitely need to make sure you remove all versions in your accessibility settings. Otherwise it won't work and will keep asking every time.

I'm going to close this issue for now as I think this issue has definitely been fixed in 1.5.0 if it wasn't a setup specific issue to begin with. I just tested it and it works fine for me so. But if you do keep running into it, feel free to reopen this :)

@JoniVR commented on GitHub (May 8, 2019): You definitely need to make sure you remove all versions in your accessibility settings. Otherwise it won't work and will keep asking every time. I'm going to close this issue for now as I think this issue has definitely been fixed in 1.5.0 if it wasn't a setup specific issue to begin with. I just tested it and it works fine for me so. But if you do keep running into it, feel free to reopen this :)

gitea-mirror commented

2026-05-05 04:50:39 -06:00

Author

Owner

@carlosfilhoadm commented on GitHub (May 18, 2019):

Hi, thank you for responding and sorry for taking so much time to write my own response.

Eventually I just added the app to the list of Accessibility Features in order to stop all the constant prompts.

Currently I use a common PC wireless keyboard (with a USB dongle).

The issue now is that after updating to v1.5.2 the brightness and volume keys (along with the on-screen notifications) stopped working. They worked normally in v1.3.0.

@carlosfilhoadm commented on GitHub (May 18, 2019): Hi, thank you for responding and sorry for taking so much time to write my own response. Eventually I just added the app to the list of Accessibility Features in order to stop all the constant prompts. Currently I use a common PC wireless keyboard (with a USB dongle). The issue now is that after updating to v1.5.2 the brightness and volume keys (along with the on-screen notifications) stopped working. They worked normally in v1.3.0.