To connect to the Android Emulator running on a Mac from a Windowsvirtual machine, use the following steps:
Start the emulator on the Mac.
Kill the
adb
server on the Mac:Note that the emulator is listening on 2 TCP ports on the loopbacknetwork interface:
The odd-numbered port is the one used to connect to
adb
. See alsohttps://developer.android.com/tools/devices/emulator.html#emulatornetworking.Option 1: Use
nc
to forward inbound TCP packets received externally on port 5555 (orany other port you like) to the odd-numbered port on the loopbackinterface (127.0.0.1 5555 in this example), and to forward theoutbound packets back the other way:As long as the
nc
commands stay running in a Terminal window, thepackets will be forwarded as expected. You can type Control-C inthe Terminal window to quit thenc
commands once you're doneusing the emulator.(Option 1 is usually easier than Option 2, especially if System Preferences > Security & Privacy > Firewall is switched on.)
Option 2: Use
pfctl
to redirect TCP packets from port5555
(or any other port youlike) on theShared Networking interface tothe odd-numbered port on the loopback interface (127.0.0.1:5555
in this example):This command sets up port forwarding using the
pf packet filter
system service. The line breaks are important. Be sure to keep themintact when copy-pasting. You will also need to adjust theinterface name from vmnet8 if you're using Parallels.vmnet8
isthe name of the special NAT device for the Shared Networkingmode in VMWare Fusion. The appropriate network interface inParallels is likelyvnic0.Connect to the emulator from the Windows machine:
Replace 'ip-address-of-the-mac' with the IP address of the Mac, for example as listed by
ifconfig vmnet8 grep 'inet '
. If needed, replace5555
with the other port you like from step 4. (Note: one way to get command-line access toadb
is via Tools > Android > Android Adb Command Prompt in Visual Studio.)
Alternate technique using ssh
If you have enabled Remote Login on the Mac, then you can use ssh
port forwarding to connect to the emulator.
Emulators are the best way to run Android apps on PC. Emulators have become fashionable. This is not surprising since they are easy to get and they offer you the means of benefiting directly. Android emulators allow the users to run and test Android apps on the PC rather than on the phone. This is the Android Software Development Kit License Agreement 1. Introduction 1.1 The Android Software Development Kit (referred to in the License Agreement as the 'SDK' and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement.
Install an SSH client on Windows. One option is to installGit for Windows. The
ssh
command will then be available in the Git Bash command prompt.Follow steps 1-3 from above to start the emulator, kill the
adb
server on the Mac, and identify the emulator ports.Run
ssh
on Windows to set up two-way port forwarding between alocal port on Windows (localhost:15555
in this example) and theodd-numbered emulator port on the Mac's loopback interface(127.0.0.1:5555
in this example):Asus xonar dgx review. Replace
mac-username
with your Mac username as listed bywhoami
. Replaceip-address-of-the-mac
with the IP address ofthe Mac.Connect to the emulator using the local port on Windows:
(Note: one easy way to get command-line access to
adb
is viaTools > Android > Android Adb Command Prompt in Visual Studio.)
A small caution: if you use port 5555
for the local port, adb
willthink that the emulator is running locally on Windows. This doesn'tcause any trouble in Visual Studio, but in Visual Studio for Mac itcauses the app to exit immediately after launch.
Alternate technique using adb -H
is not yet supported
In theory, another approach would be to use adb
's built-in capabilityto connect to an adb
server running on a remote machine (see forexample https://stackoverflow.com/a/18551325).But the Xamarin.Android IDE extensions do not currently provide a wayto configure that option. Portraiture crack for mac.
Contact information
This document discusses the current behavior as of March, 2016. Thetechnique described in this document is not part of the stable testingsuite for Xamarin, so it could break in the future.
If you notice that the technique no longer works, or if you notice anyother mistakes in the document, feel free to add to the discussion onthe following forum thread:http://forums.xamarin.com/discussion/33702/android-emulator-from-host-device-inside-windows-vm.Thanks!