[GH-ISSUE #1713] App becomes stuck at 0% (but allow zero unchecked) and volume display does not go away V4.3.3

gitea-mirror commented

2026-05-05 06:55:26 -06:00

Owner

Originally created by @cglennx on GitHub (Dec 30, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1713

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

When adjusting brightness with the F1 and F2 keys, sometimes (unpredictably), I loose control. The menu bar icon will show 0%, although I do not have the zero percent option checked, and it looks more like 1%. Finally the brightness 'big eye' with the progress bar stays open, no matter what. If I close and re-open the app, there is no change. I must restart computer.

Steps to reproduce

Not sure, but it happens when I'm adjusting the brightness. It may be when it reaches 1%, the lowest setting, but I can't always recreate it.

Expected behavior

I've described this above.

Anything else?

Environment Information (please complete the following information)

macOS version:15.2
- Mac model:MacMini M4
- MonitorControl version:4.3.3
- Monitor(s): Apple studio display
- Apple Silicon/M1 (yes or no): no

Originally created by @cglennx on GitHub (Dec 30, 2024). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1713 ### 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 When adjusting brightness with the F1 and F2 keys, sometimes (unpredictably), I loose control. The menu bar icon will show 0%, although I do not have the zero percent option checked, and it looks more like 1%. Finally the brightness 'big eye' with the progress bar stays open, no matter what. If I close and re-open the app, there is no change. I must restart computer. ### Steps to reproduce Not sure, but it happens when I'm adjusting the brightness. It may be when it reaches 1%, the lowest setting, but I can't always recreate it. ### Expected behavior I've described this above. ### Anything else? <img width="2560" alt="Screenshot 2024-12-29 at 10 21 12 PM" src="https://github.com/user-attachments/assets/adfa229b-0f90-4b83-a6ef-e148bb878eb5" /> ### Environment Information (please complete the following information) ```markdown macOS version:15.2 - Mac model:MacMini M4 - MonitorControl version:4.3.3 - Monitor(s): Apple studio display - Apple Silicon/M1 (yes or no): no ```

gitea-mirror added the

bug

Status: Abandoned

labels 2026-05-05 06:55:26 -06:00

gitea-mirror commented

2026-05-05 06:55:29 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 2, 2025):

Hmm. This is not ideal. Is there any way to reproduce this or is this totally random? Do you use any app or tool that might interfere with keyboard control? What kind of keyboard are you using?

@waydabber commented on GitHub (Jan 2, 2025): Hmm. This is not ideal. Is there any way to reproduce this or is this totally random? Do you use any app or tool that might interfere with keyboard control? What kind of keyboard are you using?

gitea-mirror commented

2026-05-05 06:55:32 -06:00

Author

Owner

@cglennx commented on GitHub (Jan 3, 2025):

I'm using a Logitech wireless keyboard (Logitech Ergo K860) and mouse (Logitech Pro Wireless). They are not a package, so each has it's own dongle. I've been trying to 'get it to do it again,' so I can chart exactly what I did. So far, 4 times it's happened over the past 3 or so weeks, but of course I did not recall exactly what I did just before.

If you can keep this open for a while, when I do move brightness to my minimum (menu bar says 0%), I'll remember what I do before and after, to see if something can be identified. Or of course I could start a new thread if you'd rather.

@cglennx commented on GitHub (Jan 3, 2025): I'm using a Logitech wireless keyboard (Logitech Ergo K860) and mouse (Logitech Pro Wireless). They are not a package, so each has it's own dongle. I've been trying to 'get it to do it again,' so I can chart exactly what I did. So far, 4 times it's happened over the past 3 or so weeks, but of course I did not recall exactly what I did just before. If you can keep this open for a while, when I do move brightness to my minimum (menu bar says 0%), I'll remember what I do before and after, to see if something can be identified. Or of course I could start a new thread if you'd rather.

gitea-mirror commented

2026-05-05 06:55:34 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 3, 2025):

It's ok, you can keep it open. If you have time to test whether the same issue happens with BetterDisplay (all MC features are free in it), that might give some additional insight.

@waydabber commented on GitHub (Jan 3, 2025): It's ok, you can keep it open. If you have time to test whether the same issue happens with BetterDisplay (all MC features are free in it), that might give some additional insight.

gitea-mirror commented

2026-05-05 06:55:36 -06:00

Author

Owner

@cglennx commented on GitHub (Jan 24, 2025):

It finally happened again. I usually turn off my computer at night, but I forgot last night. I had the brightness at minimum, so the first thing I did after moving the mouse to turn off the screen saver (one that comes with Sequoia, not a third party), I pressed F2 one tap. The screen immediately ramped up to 100%, and F1 neither lowered it nor did the brightness bar appear (it had appeared as it ramped up to 100%. I open the menu bar icon and manually slide it down, and it lowered, but as soon as I released it, it ramped up to 100%. I closed the app, and that had no effect. It stayed at 100% and F1 did not do anything.

After restarting, the brightness was at 100%, but F1 lowered it to my selected level.

@cglennx commented on GitHub (Jan 24, 2025): It finally happened again. I usually turn off my computer at night, but I forgot last night. I had the brightness at minimum, so the first thing I did after moving the mouse to turn off the screen saver (one that comes with Sequoia, not a third party), I pressed F2 one tap. The screen immediately ramped up to 100%, and F1 neither lowered it nor did the brightness bar appear (it had appeared as it ramped up to 100%. I open the menu bar icon and manually slide it down, and it lowered, but as soon as I released it, it ramped up to 100%. I closed the app, and that had no effect. It stayed at 100% and F1 did not do anything. After restarting, the brightness was at 100%, but F1 lowered it to my selected level.

gitea-mirror commented

2026-05-05 06:55:38 -06:00

Author

Owner

@cglennx commented on GitHub (Jan 30, 2025):

Two more times. Once yesterday, where the brightness went to 100% and needed a restart. And right now, it is stuck at 0%. The only thing in common across most or all is that it happens after a period of inactivity, maybe at least 2 or 3 hours of it in screen saver mode. My saver is the Message one, with the message being a single space, i.e., no visible message, just the apple logo moving about. I've used this one for years and since I started Sequoia over 2 months ago.

Edit: Whether it goes to 100% or 0% depends on which F2 or F1 is pressed first. After a period of inactivity, if I press F1, it goes down to 0%, and if I press F2, it ramps up to 100%.

@cglennx commented on GitHub (Jan 30, 2025): Two more times. Once yesterday, where the brightness went to 100% and needed a restart. And right now, it is stuck at 0%. The only thing in common across most or all is that it happens after a period of inactivity, maybe at least 2 or 3 hours of it in screen saver mode. My saver is the Message one, with the message being a single space, i.e., no visible message, just the apple logo moving about. I've used this one for years and since I started Sequoia over 2 months ago. Edit: Whether it goes to 100% or 0% depends on which F2 or F1 is pressed first. After a period of inactivity, if I press F1, it goes down to 0%, and if I press F2, it ramps up to 100%.

gitea-mirror commented

2026-05-05 06:55:39 -06:00

Author

Owner

@cglennx commented on GitHub (Feb 12, 2025):

Just now again. After 3 hours inactivity, stuck on 0% with brightness display icon stuck too.

I kept working anyway, and after about 5 minutes, the brightness bar in the middle-bottom screen disappeared, and I now have full control of brightness. Strange.

@cglennx commented on GitHub (Feb 12, 2025): Just now again. After 3 hours inactivity, stuck on 0% with brightness display icon stuck too. ***** I kept working anyway, and after about 5 minutes, the brightness bar in the middle-bottom screen disappeared, and I now have full control of brightness. Strange.

gitea-mirror commented

2026-05-05 06:55:40 -06:00

Author

Owner

@cglennx commented on GitHub (Feb 20, 2025):

Last time I'm going to comment. It is happening more frequently. I am surprised no one else has reported this. Always, it is after a period of inactivity.

@cglennx commented on GitHub (Feb 20, 2025): Last time I'm going to comment. It is happening more frequently. I am surprised no one else has reported this. Always, it is after a period of inactivity.

gitea-mirror commented

2026-05-05 06:55:42 -06:00

Author

Owner

@waydabber commented on GitHub (Feb 20, 2025):

It might be a specific issue with the config or the keyboard (or keyboard connection). The way key repeat works in MonitorControl (due to technical reasons) is that between a KeyDown and KeyUp event it assumes that the key is being constantly pressed with the key repeat interval. If there is something wrong with the keyboard, keyboard driver, connection or some other keyboard management app somehow interferes, it is possible that in some cases the KeyUp event never happens - in this case brightness runs down to 0% and after a while the app gives up waiting and assumes something happened and exits the pressed loop.

@waydabber commented on GitHub (Feb 20, 2025): It might be a specific issue with the config or the keyboard (or keyboard connection). The way key repeat works in MonitorControl (due to technical reasons) is that between a KeyDown and KeyUp event it assumes that the key is being constantly pressed with the key repeat interval. If there is something wrong with the keyboard, keyboard driver, connection or some other keyboard management app somehow interferes, it is possible that in some cases the KeyUp event never happens - in this case brightness runs down to 0% and after a while the app gives up waiting and assumes something happened and exits the pressed loop.

gitea-mirror commented

2026-05-05 06:55:43 -06:00

Author

Owner

@cglennx commented on GitHub (Feb 20, 2025):

OK. But that it only happens after a period of inactivity, usually 2+ hours, does that still fit with your explanation? I don't seem to have any other keyboard anomalies. Could changing any of the keyboard settings help?

@cglennx commented on GitHub (Feb 20, 2025): OK. But that it only happens after a period of inactivity, usually 2+ hours, does that still fit with your explanation? I don't seem to have any other keyboard anomalies. Could changing any of the keyboard settings help?

gitea-mirror commented

2026-05-05 06:55:44 -06:00

Author

Owner

@waydabber commented on GitHub (Feb 20, 2025):

Not sure why this happens exactly, this was just an idea how it could happen.

@waydabber commented on GitHub (Feb 20, 2025): Not sure why this happens exactly, this was just an idea how it could happen.

gitea-mirror commented

2026-05-05 06:55:46 -06:00

Author

Owner

@cglennx commented on GitHub (Apr 28, 2025):

I can confirm this bug is not limited to MonitorContror or BetterDisplay. The same happens with Display Buddy, and one other software that was so bad I deleted it within a minute and don't recall the name. I assume it is a MAC bug.

@cglennx commented on GitHub (Apr 28, 2025): I can confirm this bug is not limited to MonitorContror or BetterDisplay. The same happens with Display Buddy, and one other software that was so bad I deleted it within a minute and don't recall the name. I assume it is a MAC bug.

gitea-mirror commented

2026-05-05 06:55:47 -06:00

Author

Owner

@stale[bot] commented on GitHub (Apr 29, 2026):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 29, 2026): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

Rows
Columns

[GH-ISSUE #1713] App becomes stuck at 0% (but allow zero unchecked) and volume display does not go away V4.3.3 #950

Before opening the issue, have you...?

Describe the bug

Steps to reproduce

Expected behavior

Anything else?

Environment Information (please complete the following information)