[GH-ISSUE #1414] Brightness and Popup issue #798

New issue

Closed

opened 2026-05-05 06:43:18 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:43:18 -06:00

Owner

Originally created by @abejeyapratap on GitHub (Aug 10, 2023).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1414

Before opening the issue, have you...?

Searched for existing issues
Read through the Monitor-Troubleshooting Wiki
Updated MonitorControl to the latest version (if applicable)

Describe the issue

I really like this app, but having two minor issues:

Every time my laptop goes to sleep and then wakes up, my monitors are at full brightness (instead of last saved brightness)
a) I tried the following settings: "Apply last saved values to the display" and "Assume last saved settings are valid". Both don't resolve this issue.
Occasionally, when trying to adjust brightness (specifically after wake up), I get a pop-up telling me to close other apps that manage brightness (like f.lux). However, I don't have any other apps that adjust brightness.

Expected behavior

When laptop wakes up, monitors should be at last saved brightness
Should not get the pop-up

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: Ventura 113.5
- Mac model: MacBook Pro (13-inch, 2020)
- MonitorControl version: v4.1.0
- Monitor(s): 2 of Planar PLL2210W
- Monitor Cable(s)/Connection(s): same for both monitors
    - MacBook Pro -> Mokin docking station -> HDMI-DVI cable -> Planar PLL2210W
- Apple Silicon/M1 (yes or no): no

Originally created by @abejeyapratap on GitHub (Aug 10, 2023). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1414 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Read through [the Monitor-Troubleshooting Wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the issue I really like this app, but having two minor issues: 1. Every time my laptop goes to sleep and then wakes up, my monitors are at full brightness (instead of last saved brightness) a) I tried the following settings: "Apply last saved values to the display" and "Assume last saved settings are valid". Both don't resolve this issue. 3. Occasionally, when trying to adjust brightness (specifically after wake up), I get a pop-up telling me to close other apps that manage brightness (like f.lux). However, I don't have any other apps that adjust brightness. ### Expected behavior 1. When laptop wakes up, monitors should be at last saved brightness 2. Should not get the pop-up ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: Ventura 113.5 - Mac model: MacBook Pro (13-inch, 2020) - MonitorControl version: v4.1.0 - Monitor(s): 2 of Planar PLL2210W - Monitor Cable(s)/Connection(s): same for both monitors - MacBook Pro -> Mokin docking station -> HDMI-DVI cable -> Planar PLL2210W - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:43:18 -06:00

closed this issue
added the
bug

Status: Abandoned
labels

gitea-mirror commented

2026-05-05 06:43:22 -06:00

Author

Owner

@IntegerOverlord commented on GitHub (Aug 14, 2023):

I have a very similar problem, but when my computer wakes up it goes to a minimum brightness (not full) and takes 30-40 seconds to recover to the last saved brightness

@IntegerOverlord commented on GitHub (Aug 14, 2023): I have a very similar problem, but when my computer wakes up it goes to a minimum brightness (not full) and takes 30-40 seconds to recover to the last saved brightness

gitea-mirror commented

2026-05-05 06:43:24 -06:00

Author

Owner

@stale[bot] commented on GitHub (Aug 15, 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 (Aug 15, 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.