You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: