Skip to content
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

the mouse click becomes unresponsive in the secure screen #5637

Closed
yuyiqilin opened this issue Dec 8, 2024 · 5 comments
Closed

the mouse click becomes unresponsive in the secure screen #5637

yuyiqilin opened this issue Dec 8, 2024 · 5 comments

Comments

@yuyiqilin
Copy link

OS: Windows 11
Scrcpy version: 3.0.2
Installation method: Windows release

Sorry, I’ve found other bugs. Has the mouse click algorithm changed in version 3.0.2? There are two places where it’s not working as smoothly. One is that when I enable the pointer_location display, I can’t see the trace of the mouse movement. The other is on the payment screen of the app (the screen is black), where the mouse click becomes unresponsive (tested on Android 10, no bugs, but there’s a problem on Android 14). This bug exists whether the video thread is enabled or not. I tested version 2.7, and there was no such bugs.

@cactysman
Copy link

I can confirm doing things like entering the screen lock pattern has worked fine on the v2 branch and stopped working in v3. I've done that all the time and for now I'm using v2 for that.

@yuyiqilin
Copy link
Author

I can confirm doing things like entering the screen lock pattern has worked fine on the v2 branch and stopped working in v3. I've done that all the time and for now I'm using v2 for that.

So v3 does have some problems when it comes to dealing with the secure screen.

@rom1v
Copy link
Collaborator

rom1v commented Dec 8, 2024

Probably fixed by #5614.

@rom1v
Copy link
Collaborator

rom1v commented Dec 11, 2024

Could you please confirm this is fixed by scrcpy 3.1?

@yuyiqilin
Copy link
Author

Could you please confirm this is fixed by scrcpy 3.1?

Yes,it worked well now.

@rom1v rom1v closed this as completed Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants