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

Devices listing bug #48

Open
0xbadb0d00 opened this issue Mar 22, 2021 · 3 comments
Open

Devices listing bug #48

0xbadb0d00 opened this issue Mar 22, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@0xbadb0d00
Copy link

Hello,
sometimes Dexcalibur shows Devices ID with a simple "*".

This means that it doesn't correct recognized the device, simply because it launched the adb devices listing command, that returned a string like "* daemon started successfully *" and it get the first character as a correct Device ID.

To let it works with a workaround, I modified that piece of code to call device listing two times, in this way:
AdbWrapper3 js

Hope it helps other guys and developers

@0xbadb0d00 0xbadb0d00 added the bug Something isn't working label Mar 22, 2021
@FrenchYeti
Copy link
Owner

Hey, thank you :)

@FrenchYeti
Copy link
Owner

Commonly, this case happens when user runs "adb" commands from terminal and from dexcalibur. Since Dexcalibur come with own ADB binary, when dexcalibur executes ADB command, it must restart daemon.

@0xbadb0d00
Copy link
Author

Commonly, this case happens when user runs "adb" commands from terminal and from dexcalibur. Since Dexcalibur come with own ADB binary, when dexcalibur executes ADB command, it must restart daemon.

The strange behaviour is that before this happen Dexcaliur correctly launched the "adb kill" command, and so, I am expecting that id already restarted it's correct server, but anyway it tries to restart adb server also when you launch the device listing command

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants