-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Lack of input on --display 2/DeX mode #1288
Comments
Réf: #1177 (comment) @peanutwolf Since the scrcpy/server/src/main/java/com/genymobile/scrcpy/wrappers/InputManager.java Lines 50 to 60 in eb8f7a1
I think that scrcpy/server/src/main/java/com/genymobile/scrcpy/Device.java Lines 118 to 123 in eb8f7a1
What do you think? Also, when not supported, I'm not sure we should disable "power mode": scrcpy/server/src/main/java/com/genymobile/scrcpy/Controller.java Lines 115 to 119 in eb8f7a1
|
@rom1v if My guess that we should attempt to call
I couldn't clearly understand how it works. Without scrcpy you connect some kind of touch screen to DeX? |
@peanutwolf What about something like 0e27256? |
Yes, correct |
OK, so to summarize: input events on secondary displays may not work before Android 10. However, they were not disabled explicitly in your case, this is fixed by 94a7f1a. |
So, I've just downloaded latest stable release, paste'd scrcpy and scrcpy-server from dev branch (as posted in another issue), and wanted to test it with my DeX, so basically hook my S8+ to the docking station and share input of my notebook to the desktop mode of my phone. Dumpsys shows 3 displays: 0 - internal, 2 - desktop mode (DeX), 10 - marked as HDMI output (shown only when hooked to docking station, has mHasContent=false).
Choosing --display 0 without any problems. When I write --display 2 and try to give any input, I get "CANNOT ASSOCIATE A DISPLAY ID TO THE INPUT EVENT". --display 10 shows nothing, as expected.
The text was updated successfully, but these errors were encountered: