You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Hope it helps other guys and developers
The text was updated successfully, but these errors were encountered:
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.
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
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:
Hope it helps other guys and developers
The text was updated successfully, but these errors were encountered: