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
Is there a workaround for controlling brightness as well (via redshift -b)? It's the only thing missing. I find that late at night, the screen is too bright unless at the temperature is set incredibly low (~1900K), which makes things too red. Unfortunately, setting redshift's brightness manually seems to conflict with redshift-scheduler--it would set the brightness but reset after a while (perhaps in a minute or so, which I guess is because of redshift-scheduler's gradual change per minute).
The text was updated successfully, but these errors were encountered:
It seems like when redshift is called like this redshift -O <temperature>, the brightness would get reset.
We would either need support for controller the brightness (within rules).. Or a way to read the current brightness (somehow) and call it like this: redshift -O <temperature> -b <brightness>.
I think that being able to adjust the brightness automatically could be convenient though.
Another thing I'm wondering is.. Maybe we have the same problem with gamma (redshift -g ..)
Is there a workaround for controlling brightness as well (via
redshift -b
)? It's the only thing missing. I find that late at night, the screen is too bright unless at the temperature is set incredibly low (~1900K), which makes things too red. Unfortunately, setting redshift's brightness manually seems to conflict with redshift-scheduler--it would set the brightness but reset after a while (perhaps in a minute or so, which I guess is because of redshift-scheduler's gradual change per minute).The text was updated successfully, but these errors were encountered: