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
Disable brightness controls for systems using external displays #173
Comments
Some external displays may actually support brightness controls; we should check if brightness control is supported on any enabled displays before disabling stuff. |
https://en.wikipedia.org/wiki/Display_Data_Channel#DDC/CI
I wonder if it is a long-standing myth amongst computer users and developers that external displays do not support bi-directional communication and OS-sourced commands? Most of my searching has come up with people saying, "External displays don't support this." But if the above is true, in fact most displays now support this; it is the OS that simply doesn't make use of it! |
Coming back to this: The tool: ddccontrol Short explanation: how to change brightness To add support for new models: This tool works but I'm unsure if they are actively developing it. Anyhow, I could change the brightness easily first time I opened it with a generic profile. There is also ddcutil but I still need to understand it. |
To change brightness with ddcuitil from cli:
In my case:
Extra info:
|
Related to elementary/wingpanel-indicator-power#41 |
As per elementary/wingpanel-indicator-power#163
on 5.1.7
The brightness control settings are irrelevant for systems using only external displays. Suggest that both the display brightness slider and the "automatically adjust brightness" button be dimmed out/disabled when only external displays are detected, to avoid the appearance of hardware control capacity that does not exist.
This is similar, eg, to behavior that disables software control of bluetooth when no bluetooth device is connected.
The text was updated successfully, but these errors were encountered: