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
When I start scrcpy with the --turn-screen-off command line option, or if I use ctrl-o keyboard shortcut, once running to keep the mirroring working while turning the screen off, then any subsequent screen brightness change is no more taken in account until I reboot.
No matter what I do after:
Changing brightness manually
Turning off and on adaptive brightness
The screen brightness will remain what it was before the scrcpy session. And this, until I reboot which eventually restores the mechanism.
If I run scrcpy without passing the command line option or issuing the ctrl-o keyboard shortcut, everything is fine from brightness adjustment point of view...
I didn't notice this initially, or at least didn't make the link as clear as it is now.
This is on Samsung S9 running /e/ (basically the same as LineageOS) based on Oreo , but a friend of mine running LineageOS on a Samsung S7 do not face the same issue...
The text was updated successfully, but these errors were encountered:
Some ROMs have bugs with screen power state. I even disabled the possibility to turn back the screen on via a shortcut due to similar problems: 8c8649c
Unfortunately, I think there's nothing scrcpy can do.
When I start
scrcpy
with the--turn-screen-off
command line option, or if I usectrl-o
keyboard shortcut, once running to keep the mirroring working while turning the screen off, then any subsequent screen brightness change is no more taken in account until I reboot.No matter what I do after:
The screen brightness will remain what it was before the
scrcpy
session. And this, until I reboot which eventually restores the mechanism.If I run
scrcpy
without passing the command line option or issuing thectrl-o
keyboard shortcut, everything is fine from brightness adjustment point of view...I didn't notice this initially, or at least didn't make the link as clear as it is now.
This is on Samsung S9 running /e/ (basically the same as LineageOS) based on Oreo , but a friend of mine running LineageOS on a Samsung S7 do not face the same issue...
The text was updated successfully, but these errors were encountered: