mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #492] Didn't work for my AOC U27N3C & intel chip MacBook pro through usb-c cable #390
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#390
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 @Roderick-Stinson on GitHub (Jul 31, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/492
Checklist
Describe the issue


I'm using AOC U27N3C and MacBook pro-15
'2018which is not M1 chip. At first, I install this app and it worked perfectly. Suddenly, it doesn't work at all. The scroll bars were gray. I can drag them, but nothing changed. I couldn't change both brightness and volume. I tried to use a thunderbolt wire and I also installed ddcctl. They both didn't work.
Expected behavior
I wish I can control brightness and volume of my monitor with this app.
Screenshots


Additional context
Add any other context about the problem here.
Environment Information (please complete the following information):
@JoniVR commented on GitHub (Aug 2, 2021):
Can you try v2.1.0? There's an issue with 2.2.0 at the moment.
@Roderick-Stinson commented on GitHub (Aug 3, 2021):
thanks for your advice. I tried to use V2.1.0, but nothing changed. I'm pretty sure that the first time I download this app. It worked perfectly. No idea why it doesn't work now
@JoniVR commented on GitHub (Aug 3, 2021):
Make sure to check your monitor settings if OSD is somehow disabled, some monitors have the ability to disable it and it seems to happen from time to time. Otherwise I'd recommend checking out the troubleshooting wiki