There are no tricks, the adb "talking to a device through ethernet" thing has only been used in experimental setups so there was never a need to make it work with emulators as well. Supporting this will require non trivial changes to the adb sources. Have a look at system/core/adb/transport_local.c for details.
On Fri, Apr 17, 2009 at 5:24 PM, a druid <[email protected]> wrote: > > Hi, > > I'm having following small problem problem adb can connect to a real > device via ethernet and it can also connect to > emulators. > > However it seems, that I cannot connect to both devices at the same > time. > > So if I want to uplaod SW to the emulator I make > adb kill-server > adb install -r <appname> # starts server and installs application > > Then to install it on the real device I make > adb kill-server > ADBHOST=<devices_ipaddress> adb install -r <application> > > This is OK, > > However I don't know how to open one adb shell to the device > and one adb shell to the emulated device. > > > Are there any tricks? > > It seems, that the adb server (not the adb daemon) is currently unable > to work on ethernet devices and on emulators at the same time. > > This would be no problem if adb could be told to which adb server to > communicate. > > Thanks in advance for any suggestions > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
