github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #623] Make F14/F15 enabled by default #449

New issue

Closed

opened 2026-05-05 06:01:22 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:01:22 -06:00

Owner

Originally created by @skyynet on GitHub (Sep 26, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/623

Originally assigned to: @waydabber on GitHub.

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

After upgrading from 3.0.0 to 3.1.0 I experienced brightness control no longer working. After enabling the F14/F15 keys it can be done by those AND the dedicated keys. Using LG monitor & Logitech MX Keys keyboard.

Steps to reproduce

click brightness down/up

Expected behavior

brightness de-/increase

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 11.6
- Mac model: MacBook Pro (13-inch, 2016, 4 Thunderbolt 3 ports)
- MonitorControl version: 3.1.0
- Monitor(s): LG 34UC99
- Apple Silicon/M1 (yes or no): no

Originally created by @skyynet on GitHub (Sep 26, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/623 Originally assigned to: @waydabber on GitHub. ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug After upgrading from 3.0.0 to 3.1.0 I experienced brightness control no longer working. After enabling the F14/F15 keys it can be done by those AND the dedicated keys. Using LG monitor & Logitech MX Keys keyboard. ### Steps to reproduce click brightness down/up ### Expected behavior brightness de-/increase ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 11.6 - Mac model: MacBook Pro (13-inch, 2016, 4 Thunderbolt 3 ports) - MonitorControl version: 3.1.0 - Monitor(s): LG 34UC99 - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:01:22 -06:00

closed this issue
added the
enhancement

done
labels

gitea-mirror commented

2026-05-05 06:01:30 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 26, 2021):

If I understand this correctly, you're saying that the default brightness keys weren't working at all before you toggled the F14/F15 setting, and after enabling it, both options worked (as intended)?

@JoniVR commented on GitHub (Sep 26, 2021): If I understand this correctly, you're saying that the default brightness keys weren't working at all before you toggled the F14/F15 setting, and after enabling it, both options worked (as intended)?

gitea-mirror commented

2026-05-05 06:01:33 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 26, 2021):

If this is the case, then the MX Keys might possibly be mapping brightness to F14/F15 keycodes instead of regular brightness keycodes would be my first guess. Defaulting the setting to enabled and adding a note to it might be enough to "resolve" the issue in that case.

@JoniVR commented on GitHub (Sep 26, 2021): If this is the case, then the MX Keys might possibly be mapping brightness to F14/F15 keycodes instead of regular brightness keycodes would be my first guess. Defaulting the setting to enabled and adding a note to it might be enough to "resolve" the issue in that case.

gitea-mirror commented

2026-05-05 06:01:35 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 26, 2021):

In 4.0.0 I reversed how this setting works, F14/F15 is enabled by default.

@waydabber commented on GitHub (Sep 26, 2021): In 4.0.0 I reversed how this setting works, F14/F15 is enabled by default.

gitea-mirror commented

2026-05-05 06:01:37 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 26, 2021):

We should not be waiting for 4.0.0 if this is an issue in 3.1.0

@JoniVR commented on GitHub (Sep 26, 2021): We should not be waiting for 4.0.0 if this is an issue in 3.1.0

gitea-mirror commented

2026-05-05 06:01:38 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 26, 2021):

In general I think we should move away from monster releases, a lot of features can be done separately in v3.x.x releases and make little sense in a bigger release imo. I'll create a fix for 3.1.1

@JoniVR commented on GitHub (Sep 26, 2021): In general I think we should move away from monster releases, a lot of features can be done separately in v3.x.x releases and make little sense in a bigger release imo. I'll create a fix for 3.1.1

gitea-mirror commented

2026-05-05 06:01:40 -06:00

Author

Owner

@skyynet commented on GitHub (Sep 27, 2021):

If I understand this correctly, you're saying that the default brightness keys weren't working at all before you toggled the F14/F15 setting, and after enabling it, both options worked (as intended)?

Yes, that's true. As there was no F14/F15 mapping in 3.0.0 and it worked for me there, I assume something changed. Since the F14/F15 keys are pretty hard to access by mistake and I'm not aware of any software using it by default, enabling them by default sounds like a good workaround to me. Then Monitor Control works instantly for the user.

@skyynet commented on GitHub (Sep 27, 2021): > If I understand this correctly, you're saying that the default brightness keys weren't working at all before you toggled the F14/F15 setting, and after enabling it, both options worked (as intended)? Yes, that's true. As there was no F14/F15 mapping in 3.0.0 and it worked for me there, I assume something changed. Since the F14/F15 keys are pretty hard to access by mistake and I'm not aware of any software using it by default, enabling them by default sounds like a good workaround to me. Then Monitor Control works instantly for the user.