github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #1064] Brightness resets to 100% from time to time #633

New issue

Closed

opened 2026-05-05 06:24:39 -06:00 by gitea-mirror · 15 comments

gitea-mirror commented

2026-05-05 06:24:39 -06:00

Owner

Originally created by @ivnhysfryr on GitHub (Jun 3, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1064

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

I haven't been able to identify what triggers it. It happens from time to time, even when idle. Pressing any of the brightness buttons will bring back the previous setting and will increase or decrease brightness from this setting, meaning one has to press the opposite button to go back to the preferred setting.

MonitorControl works flawlessly on a MacBook Pro M1 with an external monitor.

Steps to reproduce

It happens randomly apparently

Expected behavior

Stay in the same brightness level always

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 12.2.1 Monterey
- Mac model: Mac mini (2018)
- MonitorControl version: latest (updated minutes ago)
- Monitor(s): HP ENVY 27"
- Apple Silicon/M1 (yes or no): no

Originally created by @ivnhysfryr on GitHub (Jun 3, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1064 ### 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 I haven't been able to identify what triggers it. It happens from time to time, even when idle. Pressing any of the brightness buttons will bring back the previous setting and will increase or decrease brightness from this setting, meaning one has to press the opposite button to go back to the preferred setting. MonitorControl works flawlessly on a MacBook Pro M1 with an external monitor. ### Steps to reproduce It happens randomly apparently ### Expected behavior Stay in the same brightness level always ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 12.2.1 Monterey - Mac model: Mac mini (2018) - MonitorControl version: latest (updated minutes ago) - Monitor(s): HP ENVY 27" - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:24:39 -06:00

closed this issue
added the
bug

Status: Abandoned
labels

gitea-mirror commented

2026-05-05 06:24:47 -06:00

Author

Owner

@waydabber commented on GitHub (Jun 3, 2022):

It might be the HP Envy 27". Some displays don't register DDC commands well and periodically reset to the OSD setting?

@waydabber commented on GitHub (Jun 3, 2022): It might be the HP Envy 27". Some displays don't register DDC commands well and periodically reset to the OSD setting?

gitea-mirror commented

2026-05-05 06:24:50 -06:00

Author

Owner

@moritzWa commented on GitHub (Jun 3, 2022):

I have the same issue. The issue is temporarily fixed when I adjust the MonitorControl setting slightly. I don't use the shortcuts but just move the slider a few mm to the left and then back to the right.

@moritzWa commented on GitHub (Jun 3, 2022): I have the same issue. The issue is temporarily fixed when I adjust the MonitorControl setting slightly. I don't use the shortcuts but just move the slider a few mm to the left and then back to the right.

gitea-mirror commented

2026-05-05 06:24:52 -06:00

Author

Owner

@moritzWa commented on GitHub (Jun 3, 2022):

- macOS version: 12.3.1 (21E258)
- Mac model: MacBook Pro (14-inch, 2021)
- MonitorControl version: latest (updated minutes ago)
- Monitor(s): lg ultrafine 27MD5KL (5k)
- Apple Silicon/M1 (yes or no): yes

@moritzWa commented on GitHub (Jun 3, 2022): ``` - macOS version: 12.3.1 (21E258) - Mac model: MacBook Pro (14-inch, 2021) - MonitorControl version: latest (updated minutes ago) - Monitor(s): lg ultrafine 27MD5KL (5k) - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror commented

2026-05-05 06:24:55 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Jun 3, 2022):

It might be the HP Envy 27". Some displays don't register DDC commands well and periodically reset to the OSD setting?

The same monitor works flawlessly with a MacBook Pro M1. I don't have hardware control enabled on either of the computers.

@ivnhysfryr commented on GitHub (Jun 3, 2022): > It might be the HP Envy 27". Some displays don't register DDC commands well and periodically reset to the OSD setting? The same monitor works flawlessly with a MacBook Pro M1. I don't have hardware control enabled on either of the computers.

gitea-mirror commented

2026-05-05 06:24:57 -06:00

Author

Owner

@waydabber commented on GitHub (Jun 3, 2022):

Well, if hardware control is not enabled then it is a software issue. Is syncing enabled?

@waydabber commented on GitHub (Jun 3, 2022): Well, if hardware control is not enabled then it is a software issue. Is syncing enabled?

gitea-mirror commented

2026-05-05 06:24:59 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Jun 3, 2022):

Well, if hardware control is not enabled then it is a software issue. Is syncing enabled?

It was, but yesterday I disabled it before reporting the bug.

@ivnhysfryr commented on GitHub (Jun 3, 2022): > Well, if hardware control is not enabled then it is a software issue. Is syncing enabled? It was, but yesterday I disabled it before reporting the bug.

gitea-mirror commented

2026-05-05 06:25:01 -06:00

Author

Owner

@waydabber commented on GitHub (Jun 14, 2022):

The issue might be related to https://github.com/MonitorControl/MonitorControl/issues/1028 ?

@waydabber commented on GitHub (Jun 14, 2022): The issue might be related to https://github.com/MonitorControl/MonitorControl/issues/1028 ?

gitea-mirror commented

2026-05-05 06:25:02 -06:00

Author

Owner

@ivanhoyosfreyre commented on GitHub (Jun 28, 2022):

The issue might be related to #1028 ?

I don't see how. None of those symptoms are present on my case.

@ivanhoyosfreyre commented on GitHub (Jun 28, 2022): > The issue might be related to #1028 ? I don't see how. None of those symptoms are present on my case.

gitea-mirror commented

2026-05-05 06:25:03 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Jul 24, 2022):

Any other clues? 🙏

@ivnhysfryr commented on GitHub (Jul 24, 2022): Any other clues? 🙏

gitea-mirror commented

2026-05-05 06:25:05 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Mar 21, 2023):

I'm still experiencing this bug everyday, still haven't figured out what causes it. Here's a video showing the behavior. When I wake up my computer, it always resets to full brightness and goes back to the desired setting with one single press of the brightness keys. Also, you can see how before switching screens, the brightness resets itself again. This happens very randomly in regards to times or actions.

https://user-images.githubusercontent.com/106789008/226714846-bf8794b9-eb20-4e1a-ac8d-31e8c9b94717.mov

@ivnhysfryr commented on GitHub (Mar 21, 2023): I'm still experiencing this bug everyday, still haven't figured out what causes it. Here's a video showing the behavior. When I wake up my computer, it always resets to full brightness and goes back to the desired setting with one single press of the brightness keys. Also, you can see how before switching screens, the brightness resets itself again. This happens very randomly in regards to times or actions. https://user-images.githubusercontent.com/106789008/226714846-bf8794b9-eb20-4e1a-ac8d-31e8c9b94717.mov

gitea-mirror commented

2026-05-05 06:25:06 -06:00

Author

Owner

@waydabber commented on GitHub (Mar 21, 2023):

Some displays simply forget the brightness set by DDC. You can change the startup settings so the app reapplies the last settings. You can also try BetterDisplay and make sure you have the startup behavior set to this:

(note the screenshot is from an early v2.x alpha, the current v1.4.x version has different looking Settings, but the contents is the same).

@waydabber commented on GitHub (Mar 21, 2023): Some displays simply forget the brightness set by DDC. You can change the startup settings so the app reapplies the last settings. You can also try BetterDisplay and make sure you have the startup behavior set to this: <img width="904" alt="Screenshot 2023-03-21 at 20 56 12" src="https://user-images.githubusercontent.com/37590873/226726350-b0428a9a-66df-4f70-a77c-ceeca140d156.png"> (note the screenshot is from an early v2.x alpha, the current v1.4.x version has different looking Settings, but the contents is the same).

gitea-mirror commented

2026-05-05 06:25:07 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Mar 22, 2023):

So, what makes me think my display isn't the issue is that I also have MonitorControl on a Macbook Pro and when connected to this same display, I've never encountered this issue.

I had the "Upon startup or wake" settings on "Assume last saved settings are valid". I changed it to "Apply last saved values to the display" and "Attempt to read display settings" but none did the trick.

I uninstalled MonitorControl and installed BetterDisplay. The issue still happens, but way less than with MonitorControl. Up until now, it only happens maybe once after a couple of seconds of logging in to my user account.

https://user-images.githubusercontent.com/106789008/227019977-5566c56c-ccd5-4f81-818d-0eb710d20900.mov

@ivnhysfryr commented on GitHub (Mar 22, 2023): So, what makes me think my display isn't the issue is that I also have MonitorControl on a Macbook Pro and when connected to this same display, I've never encountered this issue. I had the "Upon startup or wake" settings on "Assume last saved settings are valid". I changed it to "Apply last saved values to the display" and "Attempt to read display settings" but none did the trick. I uninstalled MonitorControl and installed BetterDisplay. The issue still happens, but way less than with MonitorControl. Up until now, it only happens maybe once after a couple of seconds of logging in to my user account. https://user-images.githubusercontent.com/106789008/227019977-5566c56c-ccd5-4f81-818d-0eb710d20900.mov

gitea-mirror commented

2026-05-05 06:25:09 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Mar 22, 2023):

Now I finally got a clue from the app. This appeared after I unplugged my router and the computer disconnected from wifi. After reconnecting, it happened again. I activated the setting suggested by the popup window and now I'm waiting to see if it happens again. So far so good.

@ivnhysfryr commented on GitHub (Mar 22, 2023): Now I finally got a clue from the app. This appeared after I unplugged my router and the computer disconnected from wifi. After reconnecting, it happened again. I activated the setting suggested by the popup window and now I'm waiting to see if it happens again. So far so good. ![Screenshot 2023-03-22 at 14 15 56](https://user-images.githubusercontent.com/106789008/227028138-1f20edb7-f921-498b-a3b2-1219d47a2646.jpg)

gitea-mirror commented

2026-05-05 06:25:11 -06:00

Author

Owner

@ivnhysfryr commented on GitHub (Mar 22, 2023):

And now, after activating that option, it's way worse, so I had to deactivate it.

https://user-images.githubusercontent.com/106789008/227029956-4e0522e0-88e6-4c0e-92dc-439b17686396.mov

@ivnhysfryr commented on GitHub (Mar 22, 2023): And now, after activating that option, it's way worse, so I had to deactivate it. https://user-images.githubusercontent.com/106789008/227029956-4e0522e0-88e6-4c0e-92dc-439b17686396.mov

gitea-mirror commented

2026-05-05 06:25:13 -06:00

Author

Owner

@stale[bot] commented on GitHub (Mar 22, 2024):

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 (Mar 22, 2024): 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.

gitea-mirror referenced this issue

2026-05-05 07:05:51 -06:00

[PR #633] [MERGED] Update Chinese (Traditional, Taiwan) translation #1142