github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #903] Macbook display is 100% when waking from sleep, external monitor maintains last settings #562

New issue

Closed

opened 2026-05-05 06:15:22 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 06:15:22 -06:00

Owner

Originally created by @jaredbm on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/903

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

Whenever I wake the macbook from sleep, the external monitor is the same as the way I left it but the macbook display is always set to 100%. Only when running this app

Steps to reproduce

set the macbook display to 80%
let it got to sleep
wake up
you'll see it's 100%

Expected behavior

The built in display is fully bright

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: Monterey
- Mac model:2019 Macbook pro 15"
- MonitorControl version: 4.0.2
- Monitor(s): built in Macbook display / 34" LG ultrawide
- Apple Silicon/M1 (yes or no): no

Originally created by @jaredbm on GitHub (Jan 21, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/903 ### 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 Whenever I wake the macbook from sleep, the external monitor is the same as the way I left it but the macbook display is always set to 100%. Only when running this app ### Steps to reproduce 1. set the macbook display to 80% 2. let it got to sleep 3. wake up 4. you'll see it's 100% ### Expected behavior The built in display is fully bright ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: Monterey - Mac model:2019 Macbook pro 15" - MonitorControl version: 4.0.2 - Monitor(s): built in Macbook display / 34" LG ultrawide - Apple Silicon/M1 (yes or no): no ```

gitea-mirror closed this issue

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

gitea-mirror commented

2026-05-05 06:15:31 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 24, 2022):

Hi there - does this happen when you turn down the brightness to 80% via the macOS built in controls as well?

@waydabber commented on GitHub (Jan 24, 2022): Hi there - does this happen when you turn down the brightness to 80% via the macOS built in controls as well?

gitea-mirror commented

2026-05-05 06:15:33 -06:00

Author

Owner

@jaredbm commented on GitHub (Jan 27, 2022):

Hello, it seems to happen if the keyboard is used to turn it down. That is consistent. It sometimes (but rarely) happens if you use the built in controls and then wake from sleep.

@jaredbm commented on GitHub (Jan 27, 2022): Hello, it seems to happen if the keyboard is used to turn it down. That is consistent. It sometimes (but rarely) happens if you use the built in controls and then wake from sleep.

gitea-mirror commented

2026-05-05 06:15:36 -06:00

Author

Owner

@waydabber commented on GitHub (Feb 1, 2022):

It seems like macOS does not register the changes made by (undocumented) API calls on this particular model. This does not seem to happen on an M1 Mac though.

@waydabber commented on GitHub (Feb 1, 2022): It seems like macOS does not register the changes made by (undocumented) API calls on this particular model. This does not seem to happen on an M1 Mac though.

gitea-mirror commented

2026-05-05 06:15:39 -06:00

Author

Owner

@cambler commented on GitHub (May 17, 2022):

I have the opposite issue, using an M1 with it's internal display as well as an external monitor. When waking from sleep, the MacBook display seems to retain it's brightness however the external display is at full blast, even though the slider in the app is at the position I set it at originally?

Really appreciate this app though. Fantastic work.

@cambler commented on GitHub (May 17, 2022): I have the opposite issue, using an M1 with it's internal display as well as an external monitor. When waking from sleep, the MacBook display seems to retain it's brightness however the external display is at full blast, even though the slider in the app is at the position I set it at originally? Really appreciate this app though. Fantastic work.

gitea-mirror commented

2026-05-05 06:15:42 -06:00

Author

Owner

@waydabber commented on GitHub (May 18, 2022):

You might have to change this setting to the highlighted one:

Some displays do reset their brightness after sleep as they forget the values set via a DDC command. This is probably a firmware issue.

@waydabber commented on GitHub (May 18, 2022): You might have to change this setting to the highlighted one: <img width="719" alt="Screen Shot 2022-05-18 at 22 56 09" src="https://user-images.githubusercontent.com/37590873/169154282-c1a40614-6398-4d92-bcad-31aac7d9ebc6.png"> Some displays do reset their brightness after sleep as they forget the values set via a DDC command. This is probably a firmware issue.

gitea-mirror commented

2026-05-05 06:15:46 -06:00

Author

Owner

@jaredbm commented on GitHub (May 18, 2022):

@waydabber The issue I have happens to the built in retina display on my Macbook, I don't know why that would be a firmware issue. And I do have that setting selected.

@jaredbm commented on GitHub (May 18, 2022): @waydabber The issue I have happens to the built in retina display on my Macbook, I don't know why that would be a firmware issue. And I do have that setting selected.

gitea-mirror commented

2026-05-05 06:15:48 -06:00

Author

Owner

@waydabber commented on GitHub (May 18, 2022):

sorry, I was responding to @cambler. His issue should be a separate one indeed but he hijacked this one. :)

@waydabber commented on GitHub (May 18, 2022): sorry, I was responding to @cambler. His issue should be a separate one indeed but he hijacked this one. :)

gitea-mirror commented

2026-05-05 06:15:51 -06:00

Author

Owner

@cambler commented on GitHub (May 19, 2022):

Thanks so much @waydabber I'll try that out. Also apologies for the hijack, was actually trying to not cloud up the threads and thought this may be related.

@cambler commented on GitHub (May 19, 2022): Thanks so much @waydabber I'll try that out. Also apologies for the hijack, was actually trying to not cloud up the threads and thought this may be related.

gitea-mirror referenced this issue

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

[PR #562] [MERGED] Fix Intel DDC Swift optimization issue #1127