Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken Powerstate #925

Open
NiekGoossens opened this issue Jan 7, 2025 · 0 comments
Open

Broken Powerstate #925

NiekGoossens opened this issue Jan 7, 2025 · 0 comments

Comments

@NiekGoossens
Copy link

Turning my monitor on/off through the shortcut in twinkletray worked fine in v15.5 and before however since updating this feature has stopped working on my second monitor (my other monitor does still work).
Using the legacy DDC/CI detection method also does not make a difference, neither does changing any other setting as far as i can tell.

Import settings ive tested:
Powerstate Signal
Turn off display action
Legacy DDC/CI

Monitor model: LC27G73TQSRXEN
The problem might be the way this monitor reports its maximum value for the powerstate.
As can be seen in the images below the maximum accepted value reported for this in ControlMyMonitor seems to be 1.
controlMyMonitor
While in the twinkletray report this seems to be 100.
tt-report-1736260647320.txt

Manually changing this value to 4 in ControlMyMonitor does disable the monitor just like it did in previous versions of twinkletray.
If there's any checks for the max powerstate value in the code this might be causing the problem, if this cannot be easily fixed in a way that would not cause problems for other monitors maybe adding a feature to force send VCP values could fix this.

Pressing the power off button also does change the state shown in the ui to turn on, however as said before does not change the actual powerstate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant