-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
Unable to use --no-display --turn-screen-off at the same time #2426
Comments
Indeed, the controller is not started if there is no display: Lines 346 to 357 in ab12b6c
The reason was that initially controls could only be initiated by input events (captured by the window). This might be changed now. |
Will I be able to run an adb command from another terminal to turn the screen off? That is without disturbing the v4l2 stream. If I can, please let me know of the command. |
Unfortunately, in the current state, no. |
Alright. Looking forward for the fix! Thanks. |
Out of curiosity, what is the use case? If your device screen is off and you pass |
Well, there's this game called Mortal Kombat mobile and in the game, you can recieve extra coins by logging in every hour and completing a few tasks. I want to automate it so that I can run it through the night. Obviously I don't want the phone display to be on all the time. Since I'll be running the controlling program headlessly on an rpi, I don't want a window. With the screen off, I am able to sent inputs using the |
I just realised that the backlight is still on on my non amoled device while using |
Fixed on
Scrcpy just request the device to change the "power mode", how the action is done is device-dependent. |
Great! |
Environment
Describe the bug
I'm trying to stream the video to a v4l2 loopback device. Everything seems to work fine except when using the options
--no-display
--turn-screen-off
at the same. There is no windowed display as expected, however the phone screen does not get turned off.On using the options one at a time everything works as expected.
I've tried it with another device (PANASONIC ELUGA Turbo (Android 5.1)). Still the same issue persists.
The text was updated successfully, but these errors were encountered: