[GH-ISSUE #1288] Brightness control are not working on my Samsung LF32TU87 (Hardware dimming) #738

Closed
opened 2026-05-05 06:36:25 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @gagarine on GitHub (Jan 15, 2023).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1288

Before opening the issue, have you...?

Describe the issue

Brightness control are not working on my Samsung LF32TU87.

Software dimming does works but not hardware dimming.

Expected behavior

Brightness control change the brightness hardware value of my Samsung LF32TU87.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 13.1 (22C65)
- Mac model: M1 Macbook Air
- MonitorControl version:4.1.0
- Monitor(s): Samsung LF32TU87
- Monitor Cable(s)/Connection(s): USB-C DisplayPort
- Apple Silicon/M1 (yes or no): Yes
Originally created by @gagarine on GitHub (Jan 15, 2023). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1288 ### 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 Brightness control are not working on my Samsung LF32TU87. Software dimming does works but not hardware dimming. ### Expected behavior Brightness control change the brightness hardware value of my Samsung LF32TU87. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 13.1 (22C65) - Mac model: M1 Macbook Air - MonitorControl version:4.1.0 - Monitor(s): Samsung LF32TU87 - Monitor Cable(s)/Connection(s): USB-C DisplayPort - Apple Silicon/M1 (yes or no): Yes ```
Author
Owner

@gagarine commented on GitHub (Jan 15, 2023):

Their is another issue for this monitor https://github.com/MonitorControl/MonitorControl/issues/1042 but no one mentionnes a problem with hardware dimming. Actually it seams to works for peoples (but perhaps it was only the software dimming without realizing it didn't works)

<!-- gh-comment-id:1383162752 --> @gagarine commented on GitHub (Jan 15, 2023): Their is another issue for this monitor https://github.com/MonitorControl/MonitorControl/issues/1042 but no one mentionnes a problem with hardware dimming. Actually it seams to works for peoples (but perhaps it was only the software dimming without realizing it didn't works)
Author
Owner

@gagarine commented on GitHub (Jan 18, 2023):

The problem is not with monitorcontrol. It's because brightness control is disable with "eco mode" is on. Disabling the eco mode solve the problem.

<!-- gh-comment-id:1387121230 --> @gagarine commented on GitHub (Jan 18, 2023): The problem is not with monitorcontrol. It's because brightness control is disable with "eco mode" is on. Disabling the eco mode solve the problem.
Author
Owner

@willxie commented on GitHub (Feb 10, 2023):

I have the same monitor with M1 MBP16" and the same issue. Disabling "Eco Saving Plus" mode unlocks OSD brightness settings. However, monitorcontrol cannot adjust the brightness for this monitor still. The brightness bar would show up but noop to the screen and real settings. @gagarine Could you share more on how you fixed this?

<!-- gh-comment-id:1425026524 --> @willxie commented on GitHub (Feb 10, 2023): I have the same monitor with M1 MBP16" and the same issue. Disabling "Eco Saving Plus" mode unlocks OSD brightness settings. However, monitorcontrol cannot adjust the brightness for this monitor still. The brightness bar would show up but noop to the screen and real settings. @gagarine Could you share more on how you fixed this?
Author
Owner

@gagarine commented on GitHub (Feb 12, 2023):

It works for a moment... and then it failed again. I need to investigate to understand what's the problem.

<!-- gh-comment-id:1427095120 --> @gagarine commented on GitHub (Feb 12, 2023): It works for a moment... and then it failed again. I need to investigate to understand what's the problem.
Author
Owner

@waydabber commented on GitHub (Feb 16, 2023):

I'll move this to discussions as it is a valid, but display specific issue which cannot be solved by changing how MonitorControl works.

<!-- gh-comment-id:1433847070 --> @waydabber commented on GitHub (Feb 16, 2023): I'll move this to discussions as it is a valid, but display specific issue which cannot be solved by changing how MonitorControl works.
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#738
No description provided.