-
-
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
MOD + up/down shortcut not working for Galaxy S20 #2503
Comments
This happens to me as well, but I am on Xiaomi Redmi K40, Android 12 |
Did you test with either Super or Alt? Or with other supported Some of them might be intercepted by the computer system. |
I tried with the By the way I am on windows, so for the first question I am using the left Alt key, I hope I answer the question |
Does this work:
? |
Yes, the adb shell command works, tested with volume down as well, both change the volume |
Please run scrcpy in verbose mode ( Please post the whole console output (as text). |
|
OK, so it looks lile it's correctly requested from the client to the server. According to your previous test, I guess that this also works:
? Is there anyrhing relevant in adb logcat when you press this shortcut from scrcpy? |
Could you please try with this version: #3190 (comment) |
This does work the same, it raised the volume #3190 doesn't solve it, still can't raise volume using shortcut key |
@rom1v for me this issue happens when the music application in the background, while still opens the application, i can change the volume using shortcut keys just fine. |
When I connect my Samsung Galaxy S20, I cannot control the volume of the phone using the MOD + up/down shortcut. I was able to do it with my previous phones (which were the S7 and Moto G7 Power), but can't seem to work it with the S20. I am able to use other shortcuts, such as MOD + R to rotate screen and MOD + O to turn off device screen.
Is anyone else having this problem with an S20? Am I doing something wrong?
Please let me know.
Thanks.
The text was updated successfully, but these errors were encountered: