This is the output of adb devices inside a docker container (a windows server image - also the host is win 10)
PS C:\> adb devices
List of devices attached
PS C:\>
I need to create CI for a Xamarin project, all is done except the part where I need to install the app on the phone via adb....until now I found no solution to use adb from inside a win docker contaienr (for linux there is the option to --privileged -v /dev/bus/usb:/dev/bus/usb, but switching to Linux is not an option( due to company decisions))
ADB can connect to the device over WiFi and from a networking aspect Docker shouldn't cause any problems for this as long as the network of the Docker Host machine can send traffic to the network of the Android device (if they are the same network, then the answer is definitely yes).
First make sure that the Docker Host machine can reach your device over the WiFi network. A test like pinging the IP of your Android device from the Docker Host machine would work. After that, initiate the ADB over WiFi using the ADB on your Docker Host machine (not the one in your container).
adb tcpip 5555
Once that is done, open a terminal in the container and connect to the Android device using the ADB inside the container.
adb connect <ip-address-of-android-device>
adb devices
Usually, when a new connection is established from an "un-trusted" machine, the device requests the user to confirm the connection and so "trust" the machine. An adbkey is created under %userProfile%/.android on the machine which the device uses to establish a trust every time the connection is made after the first time it happens so that the user doesn't need to confirm the connection every time. Copy or volume bind the adbkey into the <container_userProfile_directory>/.android so device doesn't request from the user to confirm the connection every time.
Until android 5 or 6 you need a driver for adb. Most brands give it free to download on their website.
And if you haven't done it yet, you should enable Adb-Debugging via USB in the developer options on the phone.
For adb you'll have to open the TCP port in the Dockerfile with EXPOSE 5037 (default).
I have a running mock-server (jamesdbloom/mockserver) container in my docker, with published ports: 1080:1080. I would like to connect to this container from my android app, of course USB connected to my PC. I've googled about this, and i found that adb can help me, but i have no idea how can my app communicate with my mock-server.
I've set up my android studio terminal path, so i can use the adb commands, i see my attached device, and i see there is a socket for the adb server on port 5037.
I set out to see if I can configure my development environment such that I can run adb commands from my dev box in the office network on an Android device that is connected to the USB port of my laptop which is in the same LAN (or connected via VPN). I specifically wanted the adb server to be running on the dev box and communicating to the adb daemon on my device over the network. I didn't want to connect the adb client that runs on the dev box to the adb server running on my laptop which the adb tool allows via its -H option and I didn't want to use the adb connect or adb tcpip commands. Basically, I just wanted to relay the adb communication that happens over the USB cable to happen over the network (SSH tunnel).
As a proof of concept, I managed to build a prototype using a third party solution that would allow me to share USB over network but now I want to see if I can build the same solution using port forwarding and some coding. However, my technical knowledge of USB drivers, OS kernels, and how the USB communication works (on Linux and Mac) is very basic so I am hoping to find some answers from the community.
Question: Where in the USB stack do I need to start creating hooks so I can forward all data communication of a certain USB port to a different process running in the same OS?
Proposal: If I can find the port numbers that the USB drivers on each machine communicate to the process in the kernels that then forwards the data to the application, I can use port forwarding on each machine to re-route the communication to a daemon process running on each machine that then wraps the data in TCP/IP and transfers over the network. The image below depicts this scenario:
The adb server that runs on the client machine will need to be configured to route its communication to a port on the client machine that an damon emulator process listens. This daemon process will then have to transmit the data over the network to another daemon process running on the server machine that hosts the Android device via a USB port. The latter daemon process listening to the same port that the client machine send out TCP/IP data will then read the data, transforms it to adb protocol, and sends the data to the USB device. The parts of this solution that I am trying to learn more about is how to write a daemon process that acts as a USB device emulator. Any help or recommendations for further reading is appreciated.
I found a very easy fix to this problem. I was able to get this working by running the commands below.
On my remote development machine: ($remote_host)
adb kill-server
On my laptop:
adb kill-server
adb start-server
ssh -N -R 5307:localhost:5307 $remote_host
And, finally on my remote development:
adb start-server
I was then able to run adb devices on my remote machine (using an SSH tunnel) and see the SN of the device that is connected to my laptop.
Good day,
I've been using a VMWare android machine and installing .apks on it but after my computer was unexpectedly shut down and tried to re-install a package I've been having the following problem:
$ adb -s 192.168.1.2 install 'myapp.apk'
error: device not found
- waiting for device -
However I was able to connect the VM using adb connect 192.168.1.2 which is the ip currently assigned on the android, (seen it on ctrl+f1 netcfg) and then shows:
connected to 192.168.1.2:5555
$ adb devices
List of devices attached
emulator-5554 offline
192.168.1.2:5555 device
so it appears to be online.
Troubleshooting steps taken before posting:
$adb kill/start-server
Reconfigured the VM Network (I have it bridged and Internet connection works fine).
-Suspending/Shutting down and Restarting VM.
-Restarting Internet connection (Router/PC connections)
Kindly assist with situation or post links of another issue related to mine that I probably did not find (sorry for that..)
Thanks!
Edit: I'm using Fedora as OS, Eclipse for developing
When using an ADB tcp target, the device name specified in the -s parameter must include not only the IP address but the port as well, for example:
adb -s 192.168.1.2:5555 install 'myapp.apk'
(As the android emulator actually talks over TCP behind it's "emulator-####" name, one can test this by connecting to an emulator at the loopback address using the control port plus one, ie, "emulator-5554" can also be reached as a vanilla tcp target via adb connect 127.0.0.1:5555 and then you can install on it with adb -s 127:0.0.1:5555 install whatever)
Is it possible to write the code/compile Android application on one machine and debug it remotely on the emulator launched on another? I'm sick and tired of the emulator constantly eating half of my laptop's CPU.
I haven't previously tried (or even noticed) the adb connect command that cmb mentioned, but I can confirm that forwarding the TCP ports yourself — such as over SSH — works fine.
The emulator listens on two TCP ports per instance: 5554 for the telnet interface and 5555 for control communication with tools like DDMS. So you could probably get away with only forwarding port 5555 (though I've only tried it so far with both). Each subsequent emulator takes the next available even+odd port number tuple (up to around 5580, I think).
For reference, I did the following steps on my local machine:
ssh -NL 5554:localhost:5554 -L 5555:localhost:5555 myuser#remote-server
killall adb; adb devices
I believe the emulator tries to notify a local adb server at startup; hence the need to restart adb in order for it to probe the local 5554+ ports.
Note that the localhost in the ssh command refers to the local interface of the remote machine.
adb devices showed a new emulator — emulator-5554 — and I could use it as if it were running on my local machine.
I realize this question is really old, but I solved the problem slightly differently, and it took me a while to figure out this trivial solution.
I usually use a Windows7 PC or laptop (depending on where I'm working) as my front-end because I like the GUI, however I prefer to do all of my edit/compile/debug on a headless Ubuntu server because of all the command-line power it provides. My goal is to make each windows system as much of a thin-client as possible without any extra services (such as sshd) or firewall holes.
So here is the senario:
System-A: Windows7 system with android emulator running
System-B: Ubuntu server with SDK installed
The problem as described earlier is that the emulator on System-A binds to localhost, not the external ethernet interface, so adb on the System-B cannot access the emulator on System-A. All you need to do is set up remote port forwarding in PuTTY for your SSH connection to System-B. The trick is to check the "Remote" radio button when you create the two tunnels so that the tunnel direction is reversed (tunneling from the server you are logging into to the client you are logging in from).
Finally, connect with adb to "localhost" on System-B after establishing the SSH connection:
System-B$ adb connect localhost
connected to localhost:5555
System-B$ adb devices
List of devices attached
localhost:5555 device
Now you can download images/debug as normal, and it is a trivial matter to switch to a different Windows system if you want to take your laptop out and get some coffee.
In addition, by also tunneling port 5037 in the same manner you can actually forward your adb server connection so that you can connect a real android device over USB on System-A, and download images to it from System-B. In order for this to work, you need to make sure that the adb server is running on System-A, and not running on System-B before starting your SSH session:
First, start the adb server on System-A (command prompt)
C:\> adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\> adb devices
List of devices attached
3435F6E6035B00EC device
Next, kill the adb server on System-B
System-B$ adb kill-server
Finally, restart your ssh session to System-B and verify
System-B$ adb devices
List of devices attached
3435F6E6035B00EC device
Here is how I solved it on Windows. I pretty much followed Christopher's lead, but I can't edit, so a new answer will have to do.
The problem I had was that ADB as well as the emulator was just listening on 127.0.0.1, not 0.0.0.0, for me. Otherwise I would have used TCPMon. I guess this is either different on Windows, or has changed with the latest versions of the SDK. (You can check with netstat -ban.)
I installed WinSSHD on the machine that runs the emulator. (I believe it should work with freeSSHd as well, but I couldn't get a login working there.)
I opened port 22 (TCP) in the Windows Firewall. (WinSSHD might be able to do that for you.)
I created a virtual account in the WinSSHD GUI.
I created a new PuTTY connection from the development machine to the emulator machine and made sure I could connect.
Then I set up tunnelling in PuTTY: Connection -> SSH -> Tunnels
Source port: 5554
Destination: localhost:5554
Type: Local/Auto
Source port: 5555
Destination: localhost:5555
Type: Local/Auto
(Connect and keep PuTTY open, to maintain the tunnel.)
Now I fired up the emulator on the remote machine and made sure that ADB is not running there.
I restarted ADB on the development machine (adb kill-server, then adb start-server).
adb devices and the remote emulator showed up as emulator-5554 device. I could now deploy and run my app straight from Eclipse/ADT, where the emulator showed up under Virtual Devices as if it was a local emulator.
I found an easy way to do this if your two machines are in the same private network and therefore do not need to use SSH encryption (which is the common case). This may help as an SSH tunnel can be quite long and difficult to install. For example, installing an SSH daemon under Cygwin / Windows for the first time may lead to give up (well, I gave up).
Under Windows, what follows requires having Cygwin installed with the package httptunnel. This must work under Linux / httptunnel as well but I didn't try.
Run the emulator on one of the machines (let's say its host name is HostEmulator)
Start Eclipse on the other machine (let's call it HostEclipse)
Open a Cygwin terminal on each machine, and then,
On HostEmulator, enter the following cygwin commands:
hts -F localhost:5554 10000
hts -F localhost:5555 10001
hts means Http Tunnel Server.
These two commands create two half-bridge that listen to the ports 10001 and 10001 and that redirect the I/O of these ports to the local ports 5554 and 5555, which are the ports used by the emulator (actually, the first lauched emulator - if you are several of them running they will use higher port numbers as seen in other replies of this page).
On HostEclipse, enter these ones:
htc -F 5554 HostEmulator:10000
htc -F 5555 HostEmulator:10001
htc means Http Tunnel Client.
These commands create the missing half-bridges. They listen to the local ports 5554 and 5555 and redirects the I/O of these ports to the half-bridges we have created on HostEmulator just before.
Then, still on HostEclipse, enter these three commands:
adb kill-server
adb start-server
adb devices
This restarts adb as it doesn't detect the remote emulator otherwise. It must be doing some scanning at startup. And then it lists the devices (the available emulators) just for checking.
And there you go.
You can work with your remote emulator as if it was local.
You have to keep the Cygwin terminals open on both machine otherwise you would kill the half bridges you created.
I used the port 10000 and 10001 for the machine/machine exchanges here, but of course you can use other ports as long as they are not already in use.
None of the proposed solutions worked for me.
I've started from Emirikol's solution and refined it, as with the new Android API > 21 the emulator was appearing offline and I had to go to Genymotion settings and leave Android SDK path empty.
And from command line:
netsh interface portproxy add v4tov4 listenport=5555 connectport=5555 connectaddress=<emulatorIP>
netsh interface portproxy add v4tov4 listenport=5554 connectport=5554 connectaddress=<emulatorIP>
source:http://www.sarpex.co.uk/index.php/2016/10/02/connect-genymotion-emulator-remotely/
Disclaimer, I'm the author.
When you run adb, it starts a server copy of itself if one isn't already running.
You can start that copy yourself on the machine with the device and since sdk 4.3 you can give it the -a option to tell that server to listen for remote machines. Do that with the following command which doesn't exit:
adb -a -P 5037 server nodaemon
On the machine you want to use the device from, set ADB_SERVER_SOCKET to tcp:xxxx:5037 in an environment variable (or give the same value to each adb invocation with the -L option), where xxxx is the IP address or hostname of the machine with the devices, and 5037 matches the port you gave the in the command above.
We use this to give access to about 100 emulators spread over 3 machines to a machine running end to end tests in parallel, and to developers wanting to share real devices remotely.
You can forward ports to and from the emulator with adb forward and adb reverse, and they'll appear on the machine with the devices (not the machine you're running 'adb forward' from).
My solution for windows + AndroVM (which requires a host-only adapter) when my ssh service failed to start. so it doesn't require any additional software.
adb connect <Andro VM IP>
adp tcpip 555
On cmd prompt run as admin:
netsh interface portproxy add v4tov4 listenport=5555 listenaddress=<host ip> connectport=5555 connectaddress=<Andro VM IP>
open TCP port 5555 in windows firewall.
Then, from the second PC run:
adb connect <host ip>
This post contains many answers but step by step instructions are missing.
So this answer will explain how to connect 2 computers to run projects of one computer on the emulators of another computer.
Requirements before going further:
Firewall should be off in both the PCs.
Both PCs must be connected in the same network.
Notes:
Computer running Android Studio is mentioned as "PC_AS"
Computer running Emulator is mentioned as "PC_EM"
Step 1:
On the computer running Android Studio, open a terminal window and run following command.
ssh -NL 5554:localhost:5554 -L 5555:localhost:5555 dhaval#192.168.0.104
Above command will forward 5554 and 5555 ports of PC_AS to the same ports on PC_EM. So the emulators running on PC_EM can be detected on the PC_AS.
dhaval#192.168.0.104 is the address of the PC_EM. Format of the address is username#local_ip_address
Once you run above command, the terminal window will not show anything if the command is executed successfully. It will look like nothing is going on but the process is running there.
| 💡 Note: Do not close this terminal until you want to stop remote debugging.
Step 2:
Now open another terminal window on PC_AS and run following commands one by one.
killall adb;adb devices
This command will stop the adb and stop the server.
adb start-server
This command will start the adb server.
adb devices
This command will list down all the connected adb devices.
Once you run above commands, you will see that emulators of PC_EM are now detected in the PC_AS. Now you can run the projects on those emulators and debug remotely.
| 💡 Note: While doing the above process, emulators can show a dialog to trust the incoming request.
Android emulators by default listens on local port 5555, so one way to connect to a remote emulator is by using a port forwarding tool to forward all LAN packets to local 5555 port.
One such excellent tool is Trivial Port Forward
Here is the command:
trivial_portforward.exe 1234 127.0.0.1 5555
Here 1234 is the port number where the development computer will connect. 127.0.0.1 is loopback address and 5555 is the emulator’s port.
For more detailed example, see my blog post.
This is how I made it work from host macOS with emulator to macOS client.
A: One line command
On host of emulator
socat tcp-l:5560 tcp:localhost:5559
On client
adb connect <IP>:5560
B: With a tunnel
on host with Emulator
host$ adb kill-server
host$ adb -a nodaemon server
on client with Android Studio
client$ adb kill-server
client$ ssh -L 5037:localhost:5037 <host-IP>
open second shell on client with Android Studio
client$ adb kill-server # I observe first it kills client adb
client$ adb kill-server # then it kills server adb, do it maybe once more
client$ adb devices # show devices on server now
Now I see host emulator in Android Studio as well
I don't have a second machine with the SDK to hand, but I note that the emulator's listen ports (default 5554, 5555) are listening on 0.0.0.0, i.e. reachable from remote machines, and that adb --help shows a connect <host>:<port> command. I assume that would make it show up in adb devices so adb commands work on it. For Eclipse, try "Run / Run Configurations..." and set the Target to Manual. That gives you a "device chooser" which I'm guessing would include a remote emulator if adb is connected to it. Worth a try.