[GH-ISSUE #548] 100% isnt 100% reset default #416

New issue

Closed

opened 2026-05-05 05:57:58 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:57:58 -06:00

Owner

Originally created by @fboulegue on GitHub (Sep 1, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/548

Originally assigned to: @waydabber on GitHub.

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

Hey I did install the software turned the screen down and back to 100% but its not full light up (huawai MateView) anyway to reset it to default?

Steps to reproduce

turn down screen light turn back on

Expected behavior

should go back to 100%

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:
- Mac model:
- MonitorControl version:
- Monitor(s):
- Apple Silicon/M1 (yes or no): no

Originally created by @fboulegue on GitHub (Sep 1, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/548 Originally assigned to: @waydabber on GitHub. ### 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 Hey I did install the software turned the screen down and back to 100% but its not full light up (huawai MateView) anyway to reset it to default? ### Steps to reproduce turn down screen light turn back on ### Expected behavior should go back to 100% ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: - Mac model: - MonitorControl version: - Monitor(s): - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 05:57:58 -06:00

closed this issue
added the
done

monitor Issue
labels

gitea-mirror commented

2026-05-05 05:58:05 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 1, 2021):

The display should report the maximum brightness level it supports. Almost universally all displays do support a max. level of 100 but there might be some exceptions to this. If the display has a max brightness of 100 and the display can't report this properly via DDC then the app assumes 100 as maximum brightness which might cause an issue if the maximum level is in fact 127 for example. If this is the case, then some of the brightness range is lost. There is an upcoming change planned where the max brightness level can be manually changed for misbehaving displays to fix this issue: https://github.com/MonitorControl/MonitorControl/issues/310

Alternatively there might be a case when maximum brightness level is indeed 100 but for some reason the display reports a lower value (for example 80). The result is the same. This issue can be resolved by changing the DDC read polling mode to None in the advanced section of Display settings under Preferences and restarting the app (you'll need to enable Show advanced settings... in Preferences/General)

If your question is about an immediate fix and the above don't help, then you can obviously use your display's own controls to increase brightness to 100% again. :)

Hope this helps. Let me know if I can be of any more help.

@waydabber commented on GitHub (Sep 1, 2021): The display should report the maximum brightness level it supports. Almost universally all displays do support a max. level of 100 but there might be some exceptions to this. If the display has a max brightness of 100 and the display can't report this properly via DDC then the app assumes 100 as maximum brightness which might cause an issue if the maximum level is in fact 127 for example. If this is the case, then some of the brightness range is lost. There is an upcoming change planned where the max brightness level can be manually changed for misbehaving displays to fix this issue: https://github.com/MonitorControl/MonitorControl/issues/310 Alternatively there might be a case when maximum brightness level is indeed 100 but for some reason the display reports a lower value (for example 80). The result is the same. This issue can be resolved by changing the `DDC read polling mode` to `None` in the advanced section of Display settings under Preferences and restarting the app (you'll need to enable `Show advanced settings...` in Preferences/General) <img width="803" alt="Screen Shot 2021-09-01 at 5 10 07" src="https://user-images.githubusercontent.com/37590873/131605511-91d62197-7ecb-4530-ab5e-87c6418c3fb4.png"> If your question is about an immediate fix and the above don't help, then you can obviously use your display's own controls to increase brightness to 100% again. :) Hope this helps. Let me know if I can be of any more help.

gitea-mirror commented

2026-05-05 05:58:08 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 1, 2021):

I'll close this issue since the core problem will be solved in #310. But please feel free to comment anyway or let me know if you need any further help with this! Thank you!

@waydabber commented on GitHub (Sep 1, 2021): I'll close this issue since the core problem will be solved in #310. But please feel free to comment anyway or let me know if you need any further help with this! Thank you!