In the directory where adb is located... Make sure it's executable: chmod +x adb
Then ADBHOST=192.168.0.202 ./adb kill-server ADBHOST=192.168.0.202 ./adb logcat You shouldn't need sudo. Make sure you're in the directory where adb is located and put the './' in front of adb so that it doesn't need to be in your PATH. Jim On Fri, Aug 7, 2009 at 8:54 PM, tom<tomabr...@gmail.com> wrote: > im a total newbie to android, so... > > sudo ADBHOST=192.168.0.202 adb kill-server >>> command not found // executed in the same dir where adb resides.... > and now? > > > On Fri, Aug 7, 2009 at 8:02 PM, Jim Ancona <j...@anconafamily.com> wrote: >> >> try: >> >> ADBHOST=192.168.0.202 adb kill-server >> ADBHOST=192.168.0.202 adb shell/logcat/etc >> >> Jim >> >> On Fri, Aug 7, 2009 at 7:58 PM, tom<tomabr...@gmail.com> wrote: >> > hi, >> > >> > i followed: >> > >> > http://wiki.openmoko.org/wiki/USB_Networking#Ubuntu_9.04_-_the_Jaunty_Jackalope_--_udev >> > >> > to set the network parameters. after replugging it into the usb, the >> > connection get auto-esabllished and i can ping the 202-ip. but the >> > adb-tool >> > from the android-sdk still says "no device". bump. >> > help >> > thx >> > >> > >> > _______________________________________________ >> > android-freerunner mailing list >> > android-freerunner@android.koolu.org >> > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org >> > >> > >> _______________________________________________ >> android-freerunner mailing list >> android-freerunner@android.koolu.org >> http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > > > _______________________________________________ > android-freerunner mailing list > android-freerunner@android.koolu.org > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > > _______________________________________________ android-freerunner mailing list android-freerunner@android.koolu.org http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
