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

Mismatch number of devices returned from goadb #31

Open
ltpquang opened this issue Nov 23, 2020 · 1 comment · May be fixed by #32
Open

Mismatch number of devices returned from goadb #31

ltpquang opened this issue Nov 23, 2020 · 1 comment · May be fixed by #32

Comments

@ltpquang
Copy link
Contributor

ltpquang commented Nov 23, 2020

I have 4 devices plugged in, and can successfully retrieve with adb CLI

cpu12454@cpu12454-B360M-AORUS-Gaming-3:~$ adb devices -l
List of devices attached
330055a244c72319       device usb:1-5 product:a5xeltexx model:SM_A510F device:a5xelte transport_id:2
3300b0e061f593e9       device usb:1-1 product:on7xeltedd model:SM_G610F device:on7xelte transport_id:1
52004c98eea95419       device usb:1-2 product:j7y17ltedx model:SM_J730G device:j7y17lte transport_id:3
c9acd3c9               device usb:1-6 product:j6primeltedd model:SM_J610F device:j6primelte transport_id:4

But goadb only return 3 of them:

Nov 23 18:40:15 cpu12454-B360M-AORUS-Gaming-3 device-manager[2040320]: {"Serial":"330055a244c72319","Product":"a5xeltexx","Model":"SM_A510F","DeviceInfo":"a5xelte","Usb":"1-5"}
Nov 23 18:40:15 cpu12454-B360M-AORUS-Gaming-3 device-manager[2040320]: {"Serial":"3300b0e061f593e9","Product":"on7xeltedd","Model":"SM_G610F","DeviceInfo":"on7xelte","Usb":"1-1"}
Nov 23 18:40:15 cpu12454-B360M-AORUS-Gaming-3 device-manager[2040320]: {"Serial":"52004c98eea95419","Product":"j7y17","Model":"","DeviceInfo":"","Usb":"1-2"}

I have 2 machines, each has 4 devices plugged in. Both of them have the same problem. It seems that they are ignoring the last device returned from adb.

Any idea how to resolve this problem?

@ltpquang
Copy link
Contributor Author

It seems that the full message is trimmed to fixed in 255 bytes length

330055a244c72319       device usb:338964480X product:a5xeltexx model:SM_A510F device:a5xelte transport_id:16
3300b0e061f593e9       device usb:338960384X product:on7xeltedd model:SM_G610F device:on7xelte transport_id:17
52004c98eea95419       device usb:3

@ltpquang ltpquang linked a pull request Nov 24, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant