TimBav

Can you copy/paste the files involved, instead of posting screenshots? I don't want to have to type your files out again manually because that's error-prone. I presume by 'network cable'...

I've just encountered this again. Renamed files are still showing up in two places: 1. as an old version of the file under the old name - as an untracked...

With a trivial test-rig: ``` fun main() { for (dadb in Dadb.list()) { println("$dadb ${dadb.shell("date")}") } } ``` This patch seems to allow me to access remote TCP devices connected...

Adding the following in the same place makes emulators work, but I still get the 'multiple devices attached' if I also plug in my phone... ``` if (name.contains("emulator-")) { val...

Maybe it's not 'connecting' to the device once adb has selected it, so the host:features is dropped because it's still waiting for a connect?

I dug into adb's source code and found what looks like the proper fix, replacing all the foregoing: ``` diff --git a/dadb/src/main/kotlin/dadb/adbserver/AdbServer.kt b/dadb/src/main/kotlin/dadb/adbserver/AdbServer.kt index a481f13..0d5d301 100644 --- a/dadb/src/main/kotlin/dadb/adbserver/AdbServer.kt +++ b/dadb/src/main/kotlin/dadb/adbserver/AdbServer.kt...

While the 'host-serial' change works, there's also a 'host-transport-id' in adb's source which might be better. The advantage and disadvantage of serial numbers vs transport_ids is that transport_ids are new...

You probably had more than one emulator or device attached at a time, or your emulator wasn't called emulator-5554, or perhaps no adb available: * I get the same basic...

If you can arrange to run your remote adb server with the -a flag, you can connect to that adb remotely, but you'll have to be careful about which device...