Repository navigation
Replies: 5 comments
|
Can you please extend this with detailed configuration description and all versions (macOS, BetterDisplay etc) involved? Also, please give some additional details like Apple Preset used, is brightness upscaling in effect (direct or software?), etc. These details may make the issue report a bit more actionable. Thank you! |
|
Thanks for the reply. Here are the additional configuration details. System
BetterDisplay
Built-in display
External displayI also have one external display connected:
So the setup is one MacBook built-in XDR display plus one external LS27F61x display, with the external display configured as the main display. Brightness upscalingBrightness upscaling is not in effect. In the BetterDisplay UI:
The BetterDisplay preferences also contain:
For completeness, the preferences currently contain these brightness-related values for the built-in display:
I am including these only as potentially useful diagnostic information. I do not assume that the Behavior / reproductionThe issue affects the MacBook's built-in XDR display. While BetterDisplay was running, I observed the built-in display brightness being pushed to 100%. In one observed case, BetterDisplay had not been responding to CLI brightness commands, and the application was then explicitly opened with:
After BetterDisplay was opened, the built-in display brightness jumped to 100%. The CLI command immediately before this was intended only to control the external LS27F61x display, not the built-in display:
The external display was successfully set to 50%, but opening BetterDisplay itself coincided with the built-in display brightness jumping to 100%. I have since stopped using BetterDisplay for brightness control because of this behavior. Please let me know if there are any other specific settings, or configuration values that would help narrow this down. |
|
Just commenting to say that I'm experiencing this as well and it's a little annoying. |
|
An other reason why the brightness may be pushed up/down on opening is this known macOS 27 Control Center issue (this is fixed in the latest v5.11 internal pre-release, try upgrading to that version by enabling internal pre-releases under Settings > Application > Updates): |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Issue
The brightness of my MacBook Pro's built-in Liquid Retina XDR display
suddenly became stuck at 100% while BetterDisplay was running.
Whenever I manually lowered the brightness, it immediately jumped back
to 100%.
Investigation
While the issue was occurring, I monitored the following macOS log:
I found that brightness assertions with a value of
1.0were beinggenerated continuously at approximately 12 Hz, or about 720 times
per minute.
Example:
BetterDisplay A/B test
I then quit BetterDisplay:
Immediately after BetterDisplay exited:
The observed behavior stopped after BetterDisplay was quit, suggesting
that BetterDisplay may be involved in the repeated brightness changes.
Trigger
The exact trigger is currently unknown.
BetterDisplay had been running normally for approximately 4 days and
13 hours before the problem suddenly started.
Therefore, this does not appear to happen immediately after launching
BetterDisplay, and I have not yet been able to reproduce the trigger
intentionally.
Display setup
The external Samsung display did not exhibit the same 100% brightness
behavior.
Additional information
I checked BetterDisplay's configuration after the issue occurred.
The built-in display showed a hardware brightness value of
1.0,while the external display retained normal lower brightness values.
However, the configuration file was modified after the brightness loop
had already started, so I believe the
1.0value was a consequence ofthe issue rather than the original trigger.
Please let me know if BetterDisplay diagnostic logs, configuration
files, macOS logs, or any additional testing would be useful.
All reactions