Port 5555 is only used for local transports to emulator instances, not real devices.
Iirc, the adbd daemon running on a device is listening on local port 5037. On Fri, Dec 18, 2009 at 4:26 AM, Hamilton Vera <hamilton.lis...@gmail.com>wrote: > Greetings everyone. > > I am trying to deploy android 1.6 in an iMX51 based device. Almost > everything is running ok. > > I am also trying to use adb over ethernet, unfortunately it is not > working, it looks like adbd is not binding to port 5555. I saw the > same problem here in the list: > > http://www.mail-archive.com/android-porting@googlegroups.com/msg07198.html > > Here is what I got from a netstat (I am using a serial cable to > connect to the device): > > # netstat > > 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 192.168.0.113:667 192.168.0.199:2049 > ESTABLISHED << NFS > > > I would appreciate any help, I am googling a lot about this but no answer > yet. > > > > -- > Hamilton Vera > int Administrator (char Network[],char ComputationalSystems[]) > http://hvera.wordpress.com > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
