I'm trying to use adb over 'wifi' for my emulated device. I'm emulating a device on my computer and wanted to use Android Studio to send an APK to it but through the network sockets, not through emulated USB. I know in Android Studio everything works out of the box but I need to it in this way
I'm following this tutorial: https://developer.android.com/studio/command-line/adb.html#wireless
I start it with
~/Android/Sdk/emulator$ ./emulator -avd Pixel_XL_API_27
Then I see that USB debugging is on. I then do
./adb tcpip 5555 restarting in TCP mode port: 5555
Note that .
/adb tcpip 5555 is arbitrary. I didn't even specify which device should restart and connect at 5555. What if I had 2 emulators running?
I should unplug now for a normal USB device, but then I go to developer options in my emulated phone and disable USB debugging.
I also see that the IP address in the emulated phone system settings is
then I end up with:
./adb connect 192.168.232.2 unable to connect to 192.168.232.2:5555: Connection timed out
I also done this:
./adb devices List of devices attached emulator-5554 device ./adb connect 192.168.232.2:5554 unable to connect to 192.168.232.2:5554: Connection timed out
According to Android Tutorial on ADB, my computer keeps a server running on port 5037. The Android device (my emulator in this case) runs a daemon and my adb script in Sdk/platform-tools is a client. If I want to run a client inside my virtual machine I must have a server running on it. But instead I can just forward the 5037 TCP port from the VM to the 5037 TCP port of the host machine. I did it with tcptunnel by doing the following:
./tcptunnel --local-port=5037 --remote-host=192.168.122.1 --remote-port=5037 --stay-alive
then if I run adb on my VM, it's going to connect to the adb daemon on my host machine which is going to talk with the adb server of my emulator. When I run
adb devices in the VM without the tcp forward it tries to start a new server. If I kill this server and open th tcpforwarded and do it again, it doesn't try to create a new server. This is a good signal. However, tcptunnel gives me this:
build_tunnel: connect(): Connection refused
Something is blocking the connection
Turns out tcptunnel isn't necessary, because
adb has the
H option that lets me specify the IP where the server runs. However I don't know if it's possible in Android Studio to specify it. Anyways:
./adb -H 192.168.122.1 devices List of devices attached * cannot start server on remote host error: cannot connect to daemon at tcp:192.168.122.1:5037: Connection refused