mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #17] Display settings resets after sleep #16
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#16
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 @nekrasovdmitriy on GitHub (Feb 20, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/17
Originally assigned to: @the0neyouseek on GitHub.
All application setting are set to zero after waking up from sleep, but displays keep last setting.
@the0neyouseek commented on GitHub (Feb 20, 2018):
Hi @nekrasovdmitriy,
Thanks for the report, can you tell me which settings are reset exactly ? The ones in the app preferences ? The value of the contrast/brightness/volume levels of displays ? Both ?
@nekrasovdmitriy commented on GitHub (Feb 20, 2018):
The value of the contrast/brightness/volume levels of displays.
@the0neyouseek commented on GitHub (Feb 25, 2018):
Hi @nekrasovdmitriy,
I think I've track down this bug to the fact that your monitor may not support to read
ddctlcommand values.Does this also happen when you first launch the app or only after waking from sleep ?
If it's this, what I'll do is test if the monitor support read command and if not, set the slider value to the last value saved.
Though, it has a kind of drawback, meaning that if you manually change brightness, contrast or volume on your display when the app isn't launched, the sliders will not reflect these changes, and have the wrong values.
@funbben commented on GitHub (Mar 1, 2018):
I have the same behavior, when first launching the app, all sliders are set to 0%
(My monitor is a iiyama B2791QSU-B1)
@falcn commented on GitHub (Mar 4, 2018):
P2715Q does not support ddc read, so yeah, everything is at zero after waking up from sleep. It makes sense to set sliders to last used values instead.
@falcn commented on GitHub (Apr 2, 2018):
1.3.0 become worse in that regard. After waking app, sliders are laggy, and do nothing. App has to be restarted to restore its function.
@falcn commented on GitHub (Apr 26, 2018):
Any chance to get it fixed in the next release? I have to restart MonitorControl every time I wake up my macbook, otherwise it hogs CPU and not responding to input. Looks like it gets stuck in the ddcctl read loop (Dell P2715Q does not support ddc read)
@the0neyouseek commented on GitHub (May 23, 2019):
Is this still an issue for you @falcn ?
@JoniVR commented on GitHub (Aug 19, 2019):
This is most probably due to your display not being able to read the values using ddc.
I have the same issue, currently the app already falls back to last known values though and when #97 gets merged and released you'll be able to disable polling altogether so you don't get the CPU hog.
Going to consider this closed due to inactivity and partial fix should already be there.
Feel free to reopen if I missed something here.