Let tools that drive emulators over gRPC find Simlock's emulators #1042

The problem

Tools that show and drive an Android emulator through its gRPC endpoint (argent, Android Studio's Running Devices) find an emulator through the discovery file it writes under avd/running/. Simlock starts its emulators without a gRPC port, so no discovery file exists. Such a tool sees a leased emulator on Simlock's adb server but cannot take a screenshot or send input; argent fails with "emulator not found among running emulators ... check avd/running/*.ini". adb-only control still works.

Who runs into this

Coding agents on one Mac that lease emulators from Simlock and drive them with argent for app QA. Each agent gets an emulator, but none of them can see its screen or tap it through argent, so Android QA falls back to raw adb.

What you would like to happen

An operator-only setting that starts Simlock's emulators with their gRPC endpoint on, so the emulator writes its discovery file. Off by default, so nothing changes for anyone who doesn't set it.

Anything else

We carry a local patch today and opened #1041 with one way to do it (android.emulator.grpc, port = console port + 3000, with a token). With the setting on, Android Studio also lists Simlock's emulators, which ADR 0001 otherwise keeps out of its sight; that is the operator's choice.