[GH-ISSUE #251] Brightness not working on Asus XG35VQ #194

New issue

Closed

opened 2026-05-05 05:22:40 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:22:40 -06:00

Owner

Originally created by @vikeshhh on GitHub (Jul 9, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/251

Checklist

I have searched for existing issues
I have looked through the Monitor Troubleshooting wiki
I have updated MonitorControl to the latest version

Describe the issue
Installed Monitor Control. Sound Adjustment works fine but Brightness control stopped working. It use to work. Then suddenly stopped. Also when I adjust the brightness via the monitor only, say to 50%, when I use monitor control to increase it drops to 0.

Expected behavior
Pressing Brightness Up and Down will adjust my external Monitor (Asus XG35VQ) Brightness respectively

Screenshots

Additional context
Add any other context about the problem here.

Environment Information (please complete the following information):

macOS version: 10.15.5
MonitorControl version: 2.0.0 (Build 640)
Monitor(s): Asus XG35VQ
Mac model: MacBook Pro 13" 2019, Four Thunderbolt 3 Ports
Monitor Cable(s)/Connection(s): Displayport to Elgato Thunderbolt Dock 3

-Asus XG35VQ- <==DisplayPort==>-Elgato Thunderbolt 3 Dock- <==USB 3 thunderbolt cable==> -MacbookPro 13-

Originally created by @vikeshhh on GitHub (Jul 9, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/251 **Checklist**  - [x] I have searched for existing issues - [x] I have looked through [the Monitor Troubleshooting wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [x] I have updated MonitorControl to the latest version **Describe the issue** Installed Monitor Control. Sound Adjustment works fine but Brightness control stopped working. It use to work. Then suddenly stopped. Also when I adjust the brightness via the monitor only, say to 50%, when I use monitor control to increase it drops to 0. **Expected behavior** Pressing Brightness Up and Down will adjust my external Monitor (Asus XG35VQ) Brightness respectively **Screenshots** ![Screen Shot 2020-07-08 at 7 09 26 PM](https://user-images.githubusercontent.com/30156635/86985818-61773180-c14f-11ea-929c-6cfd4785f613.png) **Additional context** Add any other context about the problem here. **Environment Information (please complete the following information):** - macOS version: 10.15.5 - MonitorControl version: 2.0.0 (Build 640) - Monitor(s): Asus XG35VQ - Mac model: MacBook Pro 13" 2019, Four Thunderbolt 3 Ports - Monitor Cable(s)/Connection(s): Displayport to Elgato Thunderbolt Dock 3 ---------------- ----------------------------- ------------------ -Asus XG35VQ- <==DisplayPort==>-Elgato Thunderbolt 3 Dock- <==USB 3 thunderbolt cable==> -MacbookPro 13- ---------------- ------------------------------ ------------------

gitea-mirror

2026-05-05 05:22:40 -06:00

closed this issue
added the
Status: Abandoned

monitor Issue
labels

gitea-mirror commented

2026-05-05 05:22:47 -06:00

Author

Owner

@JoniVR commented on GitHub (Jul 9, 2020):

Did it stop working after upgrading MonitorControl or just randomly?

@JoniVR commented on GitHub (Jul 9, 2020): Did it stop working after upgrading MonitorControl or just randomly?

gitea-mirror commented

2026-05-05 05:22:50 -06:00

Author

Owner

@vikeshhh commented on GitHub (Jul 9, 2020):

I installed v2.0.0 Build 640 and always was on that version. Just stopped working. Volume works great though.

@vikeshhh commented on GitHub (Jul 9, 2020): I installed v2.0.0 Build 640 and always was on that version. Just stopped working. Volume works great though.

gitea-mirror commented

2026-05-05 05:22:52 -06:00

Author

Owner

@stale[bot] commented on GitHub (Aug 3, 2021):

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 3, 2021): 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.