On Apr 17, 12:00 pm, RongJun Ying <rjy...@gmail.com> wrote: > Try this: > > # ADBHOST=[you host ip address] ./adb -d devices >
This is what I tried: On the device to be debugged netstat returns this: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:5037 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5555 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:962 0.0.0.0:* # Does this mean, that the application is listening on the debug port? Which port should the device be listening for debug to be working. If it is not lsitening How to I have to start adbd to be listening on ehternet? ADBHOST=[you host ip address] ./adb kill-server ; ADBHOST=[you host ip address] ./adb -d device only returns the emulator if one is running (or nothing if none is running) How can I find out whether the problem is on the adbd side or the adb- server side? thanks for any further suggestions > ----------------------------- > Ying RongJun China > > On Fri, Apr 17, 2009 at 5:52 PM, a druid <klausf...@gmail.com> wrote: > > > Hi, > > > I wondered, whether I could use adb over ethernet instead of adb over > > USB > > > Looking at the forums I did not really understand, whether this is > > feasible, was feasible, would be easy to > > accomplish. > > > Thanks in advance for any pointer / suggestions. > > > I saw mentioning of an obsolete environment variable ADBHOST, > > but no up to date discussion about adb over ethernet > > > Does anybody know more? > > > Thanks in advance for any pointers > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
