I've found that using adb kill-server usually fixes this error. Jim
On Tue, Mar 3, 2009 at 12:05 PM, Crane, Matthew <[email protected]> wrote: > I've had some problems, possibly from switching between u-boot and network > interfaces on the same usb port, where I just get a "device not found" > message from adb but can still ping the ip. This is on a bit older knoppix > version. If I reboot the both phone and computer it comes back ok with the > usb networking and adb can talk. Don't know what the problem really is. > > Matt > ________________________________ > From: [email protected] > [mailto:[email protected]] On Behalf Of podila > aditya > Sent: Tuesday, March 03, 2009 3:41 AM > To: [email protected] > Subject: [android-freerunner] ADB > > hi Android, > > I have certain problem when i try to ADB to the Device. > 1. I have it connected using the USB > 2. Given an Ip and used ifconfig to up the usb0 device > 3. Then i try to give the ./adb devices > > Result. :: i am not geting the deivces which are connected > > > > -- > Warm Regards, > Aditya > > _______________________________________________ > android-freerunner mailing list > [email protected] > http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org > > _______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
