mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #307] AOC Q24P2Q over HDMI is detected, but does not work #242
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#242
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KronP on GitHub (Oct 13, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/307
Checklist
Describe the issue
Adjusting brightness or volume sliders in MonitorControl to an AOC Q24P2Q does not change brightness or volume on the monitor.
Note: ddcctl does not work either, but ClickMonitorDDC on Windows (in Bootcamp) works.
Expected behavior
Brightness should change.
Screenshots
Additional context
The monitor is detected as a Q24P2W1 instead of a Q24P2Q. Mac OSX settings does also detect it as a Q23P2W1
Environment Information (please complete the following information):
@apryjom commented on GitHub (Nov 6, 2020):
I've got exactly the same monitor. Connected to Mac Mini Late 2012. Detected exactly the same as Q24P2W1. Currently working in 1920x1080. Looking for cable mini Display Port (Thunderbolt) <-> Display Port. Hope that will be able to run in native monitor resolution.
@besanur commented on GitHub (May 8, 2021):
Same issue on MacBook Pro (15-inch, 2018) running Mac OS 11.3.1. I have two of Q27P2Q them and they are detected as Q27P2W.
@waydabber commented on GitHub (Aug 21, 2021):
Hi, can you please confirm if this problem is still valid in light of the new v3.0.0 version?
I also want to let you know that if ddctl does not work as well then the issue probably lies with the macOS implementation of i2c display communication (which DDC uses) so we might not be able to do anything about it unfortunatelly. :(
@waydabber commented on GitHub (Aug 25, 2021):
I'll close this issue for now but please feel free to comment if there is anything we can do. If the issue persists, we can reopen this issue! Thank you!
@KronP commented on GitHub (Aug 25, 2021):
Hi, I have tried it now. It still does not work for me (still running MacOS Mojave and the same monitor).
Version 3.0.0-rc1.
@waydabber commented on GitHub (Aug 26, 2021):
Hi @KronP, if I understand correctly, the display should work with DDC (as it works in Windows) but for whatever reason ddcctl and ddc.swift (which is originally based on ddcctl and is used by MonitorControl) seems to be incompatible with it.
You might want to try Lunar from @alin23 and see if it works as it contains a different ddc implementation.
@KronP commented on GitHub (Aug 26, 2021):
Hi! That's correct.
Thank you for the suggestion. Lunar version 4 is not compatible with Mojave so I tried version 3 (I don't know if that one also uses the other implementation), but it did not work either.
@alin23 commented on GitHub (Aug 26, 2021):
@waydabber @KronP
Unfortunately Lunar is only compatible with macOS 10.15+ so it won't work on Mojave.
But I think the problem here is not the software. It could be one of the AOC features that block brightness adjustment when it is enabled. Try the following:
Disable ClearVision
Set HDR Mode to Off
Set Bright Frame to Off
Set DCB Mode to Off
Set Game Mode and LowBlue Mode to Off
If MonitorControl starts working after all of the above, you can proceed enabling them one by one while also checking MonitorControl in between to find which feature blocks DDC commands.
@KronP commented on GitHub (Aug 26, 2021):
Thank you! I checked that all of those options where already disabled (and tried again, just to be sure). To verify again, I booted into Windows in Bootcamp, and using the same settings and same HDMI-cable, the brightness controls in ClickMonitorDDC on Windows works.
@alin23 commented on GitHub (Aug 26, 2021):
I missed the Bootcamp part, my message would not be necessary if I had noticed that.
Then I guess it must be a macOS problem. All I can recommend is to upgrade to Big Sur if possible. Maybe there's some GPU driver update in the latest macOS that will fix this.
There's no guarantee that it will fix your issue though, it's just the only thing left to do.