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

Low framerate after screen was physically disconnected #3840

Closed
2 tasks done
benitofettuccine opened this issue Mar 20, 2023 · 3 comments
Closed
2 tasks done

Low framerate after screen was physically disconnected #3840

benitofettuccine opened this issue Mar 20, 2023 · 3 comments

Comments

@benitofettuccine
Copy link

  • I have read the FAQ.
  • I have searched in existing issues.

Environment

  • OS: W10 64-bit
  • scrcpy version: 2.0 64-bit
  • installation method: straight from the zip file
  • device model: Pixel 4A
  • Android version: 13 (TQ1A.230205.002)

I had received water damage on my Pixel 4A which prevented me from using the screen but I was still able to use it perfectly fine with scrcpy (only wired). I took it in to a shop for an exact diagnosis of whatever damages could have occurred and they disconnected the screen from the motherboard but reassembled my device afterwards (so there is no image output). Now when I connect to scrcpy my framerate is excruciatingly slow, but still technically usable.

How could disconnecting the LCD panel affect framerate through the renderer? Is there a fix for this?

@rom1v
Copy link
Collaborator

rom1v commented Mar 20, 2023

Disconnected or broken screen causes vsync rendering issues. Often, it could be avoided by:

scrcpy --turn-screen-off

@rom1v
Copy link
Collaborator

rom1v commented Mar 20, 2023

#1285 (comment)

@benitofettuccine
Copy link
Author

Thank you.

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

2 participants