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

Do not report controller error on device disconnected #5044

Merged
merged 1 commit into from
Jul 5, 2024

Conversation

rom1v
Copy link
Collaborator

@rom1v rom1v commented Jul 1, 2024

A device disconnection (when the adb connection is closed) makes the read() on the "receiver" socket fail.

Since commit 063a833, this is reported as an error. As a consequence, scrcpy fails with:

ERROR: Controller error

instead of:

WARN: Device disconnected

To fix the issue, report a device disconnection in that case.

@rom1v rom1v changed the title Do not report controller error on device dsconnected Jul 5, 2024
A device disconnection (when the adb connection is closed) makes the
read() on the "receiver" socket fail.

Since commit 063a833, this is reported
as an error. As a consequence, scrcpy fails with:

    ERROR: Controller error

instead of:

    WARN: Device disconnected

To fix the issue, report a device disconnection in that case.

PR #5044 <#5044>
@rom1v rom1v merged commit b419eef into dev Jul 5, 2024
@rom1v rom1v mentioned this pull request Jul 17, 2024
FreedomBen pushed a commit to FreedomBen/scrcpy that referenced this pull request Aug 2, 2024
A device disconnection (when the adb connection is closed) makes the
read() on the "receiver" socket fail.

Since commit 063a833, this is reported
as an error. As a consequence, scrcpy fails with:

    ERROR: Controller error

instead of:

    WARN: Device disconnected

To fix the issue, report a device disconnection in that case.

PR Genymobile#5044 <Genymobile#5044>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant