Bug 16882 - Ability to specify remote ADB server address, which will be used for ADB connection and debug.
Summary: Ability to specify remote ADB server address, which will be used for ADB conn...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.8.x
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-12-18 13:51 UTC by Jon Goldberger [MSFT]
Modified: 2016-05-10 16:57 UTC (History)
8 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Comment 1 Jon Goldberger [MSFT] 2013-12-18 13:55:39 UTC
We have following development configuration: OS X + Visual Studio on Win8
via Parallels VM. Android emulators launched inside VM are very slow (even
with HAX installed and running) and emulators in OS X (with HAX) are
obviously fast. Because of that we had used port-forwarded ADB (from OS X
to Win8) and we had ability to debug OS X-based emulators from Visual
Studio until you released new version of Visual Studio plugin (with panel)

Port forwarding is not good idea in general, because ADB itself can work
remotely without any other software, but it needs some additional command
line arguments. It would be great if you make it possible to add these
arguments somehow.

How does it work:

1. ADB server by default opens forwarded ports on only, but it's
possible to make it open on * interface. Just start server with the
following command:
adb -a -P 5037 fork-server server
-a — makes ADB open all ports on all interfaces
fork-server and server need because only that way it will take -a into
account (I found it digging ADB source code here
2. Client needs only to add -H <server address> option to all commands and
that's all! Port will be open on <server address>, so debugger needs to
connect to <server address>:<forwarded port> instead of
localhost:<forwarded port>

It's doesn't seem to be a big deal to make only option in visual studio
plugin with remote server ip address.

Thank you!
I'm on stable channel (4.10.1), it was update where Visual Studio Android toolbar

All I need - is ability to specify remote ADB server address, which will be
used for ADB connection and debug.
Comment 2 dean.ellis 2014-01-02 08:06:53 UTC

I remote debug from visual studio to a genymotion emulator running on my Mac all the time. You can just attach to the emulator via adb over wifi.

adb connect <ip>:<port>

in my case

adb connect 

you just need to get the IP address of the emulator via the Settings->Network menu in the emulator itself, it will probably be a NAT address, but it should be accessible from the Windows VM.
Comment 3 outring 2014-01-24 00:15:37 UTC
Unfortunately Genymotion uses Virtualbox, which can't be ran simultaneously with Parallels Desktop where Windows is.
Scenario as Xamarin.iOS has would be great — IDE on one machine and virtual testing device is on another, besides adb supports it out of the box.
Comment 4 Joaquin Jares 2015-09-16 09:26:46 UTC
This is supported out of the box in adb, as dean specified in comment #2. We do have the procedure documented here: https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/android-player-with-visual-studio-in-vm/. I'm not sure what else we need to do for this. Marking as Resolved->Answered just for confirmation. Please verify if no further action is needed or reopen if it is.