[GH-ISSUE #1194] Syncing the brightness setting of the built-in display occasionally fails #696

Closed
opened 2026-05-05 06:31:41 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @mianly on GitHub (Sep 28, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1194

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 I open the software for a period of time, when the ambient light decreases and the brightness of the built-in display decreases, the brightness of the built-in monitor displayed by the software is still the previous high brightness, and the brightness of the external display will not decrease accordingly.
I have turned on sync apple and built-in display brightness settings.
If the ambient light brightness is reduced immediately after opening the software, the brightness of the built-in display and the brightness of the external display will be reduced at the same time

Steps to reproduce

The problem reappears when I open the software for a while and then I lower the ambient light level.

Expected behavior

I would like to reduce the brightness of the built-in display when the ambient light is reduced, and the brightness of the external display is also reduced

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:13.0 Beta版(22A5352e)
- Mac model:MacBook Pro 2020
- MonitorControl version:4.1.0
- Monitor(s):AOC 24b1w1
- Apple Silicon/M1 (yes or no): no
Originally created by @mianly on GitHub (Sep 28, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1194 ### 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 I open the software for a period of time, when the ambient light decreases and the brightness of the built-in display decreases, the brightness of the built-in monitor displayed by the software is still the previous high brightness, and the brightness of the external display will not decrease accordingly. I have turned on sync apple and built-in display brightness settings. If the ambient light brightness is reduced immediately after opening the software, the brightness of the built-in display and the brightness of the external display will be reduced at the same time ### Steps to reproduce The problem reappears when I open the software for a while and then I lower the ambient light level. ### Expected behavior I would like to reduce the brightness of the built-in display when the ambient light is reduced, and the brightness of the external display is also reduced ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version:13.0 Beta版(22A5352e) - Mac model:MacBook Pro 2020 - MonitorControl version:4.1.0 - Monitor(s):AOC 24b1w1 - Apple Silicon/M1 (yes or no): no ```
gitea-mirror 2026-05-05 06:31:41 -06:00
Author
Owner

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

Well, indeed, syncing should replicate the ambient light sensor induced changes to the external display. There is an internal process that periodically checks and syncs things up, that might have some kind of issue (btw it could be rewritten to be fully event driven, that would probably be a good idea).

The following can be used for the event driven solution (BetterDisplay also uses this when needed, it's a better approach generally):

DisplayServicesRegisterForBrightnessChangeNotifications(...)
DisplayServicesUnregisterForBrightnessChangeNotifications(...)

We could tap into the ambient light sensor directly as well.

<!-- gh-comment-id:1313392975 --> @waydabber commented on GitHub (Nov 14, 2022): Well, indeed, syncing should replicate the ambient light sensor induced changes to the external display. There is an internal process that periodically checks and syncs things up, that might have some kind of issue (btw it could be rewritten to be fully event driven, that would probably be a good idea). The following can be used for the event driven solution (BetterDisplay also uses this when needed, it's a better approach generally): ``` DisplayServicesRegisterForBrightnessChangeNotifications(...) DisplayServicesUnregisterForBrightnessChangeNotifications(...) ``` We could tap into the ambient light sensor directly as well.
Author
Owner

@stale[bot] commented on GitHub (Nov 15, 2023):

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.

<!-- gh-comment-id:1813290208 --> @stale[bot] commented on GitHub (Nov 15, 2023): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#696
No description provided.