Android emulators on Windows hosts

Let a Windows device host list and start its Android emulators. The device hub ran the Android SDK's avdmanager and sdkmanager through their Unix launchers, which Windows cannot run, so the panel only knew the emulators by name and starting one failed straight away. The fix called those tools directly, on this machine and on SSH hosts alike.

Branch: GitHubfix/windows-android-sdk-launchers
PR: None…
Status: Superseded
Reason: Upstream's device toolchain update supersedes this branch. pingdotgg/t3code@ecfb734
Notes: Addressed upstream issue #13260.

Comments

This fork

Device

[apple-utils] Failed to run `xcrun simctl list devices --json`:

Android Emulators

Original

Device

[apple-utils] Failed to run `xcrun simctl list devices --json`: [android-utils] Failed to run `avdmanager list avd`:

Android Emulators

The virtual devices on my Windows desktop, in a mock Device panel. Start any of them: this fork boots it, compressed from about a minute and a half to a moment; the original fails at once, because the hub could not run avdmanager to find a free emulator port. The replica stops short of streaming the screen.