Turns out tcptunnel isn't necessary, because adb has the H option that lets me specify the IP where the server runs. However, tcptunnel gives me this: build_tunnel: connect(): Connection refused If I kill this server and open th tcpforwarded and do it again, it doesn't try to create a new server. When I run adb devices in the VM without the tcp forward it tries to start a new server. 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. I did it with tcptunnel by doing the following. But instead I can just forward the 5037 TCP port from the VM to the 5037 TCP port of the host machine. If I want to run a client inside my virtual machine I must have a server running on it. The Android device (my emulator in this case) runs a daemon and my adb script in Sdk/platform-tools is a client. Unable to connect to 192.168.232.2:5554: Connection timed outĪccording to Android Tutorial on ADB, my computer keeps a server running on port 5037. Unable to connect to 192.168.232.2:5555: Connection timed out I also see that the IP address in the emulated phone system settings is 192.168.232.2 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 didn't even specify which device should restart and connect at 5555. I know in Android Studio everything works out of the box but I need to it in this way

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'm trying to use adb over 'wifi' for my emulated device.

How to i generate adb in android studio