StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>A few more details would help:</p> <ul> <li>What is the IP address of the VM? </li> <li>Is it using NAT, bridged networking, or what?</li> <li>Do you really need to run the 2nd emulator inside a VM - this complicates networking.</li> </ul> <p><strong>UPDATE: Multiple emulators on 1 machine (no VM)</strong> You can launch another emulator from the command-line, using /emulator -avd . You'll need to create a second AVD for this to work. I use Linux, so can't give the exact details for Windows.</p> <p><strong>UPDATE: Communication between main machine and VM with android emulator</strong> I believe the emulator only listens on 127.0.0.1 for server sockets, so remote machines can't connect in - this is certainly the case for the debug sockets it uses. However, you can set up port forwarding using a similar method discussed in <a href="https://stackoverflow.com/questions/1754162/remote-debugging-with-android-emulator">Remote debugging with Android emulator</a></p> <p>It's good that you're using bridged networking, as NAT would stop the VM getting inbound connections, so the emulator would have no hope.</p> <p><strong>UPDATE #2: Port forwarding</strong> You can set up port forwarding between sockets on the local machine and on the emulator, using <a href="http://developer.android.com/guide/developing/tools/adb.html#forwardports" rel="nofollow noreferrer">adb forward</a>. It might also be worth looking at <a href="https://stackoverflow.com/questions/4044479/comunication-between-android-emulators">Communication between Android Emulators</a>, there appears to be an undocumented emulator switch -shared-net-id that could help.</p> <p>Hope this helps</p> <p>Phil Lello</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload