On Tue, Mar 3, 2009 at 11:05 AM, 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. The first time you run adb it spawns a process that handles the communication between your adb command and the adb daemon running on the device: Say $ adb shell that talks to the adb process running on your computer which in turn talks to the adb process running on your FreeRunner. If for whatever reason the adb process running on the device closes the connection (you reboot the device for example), you have to restart the adb process on your computer. Do it like this: $ adb kill-server $ ADBHOST=192.168.0.202 adb wait-for-device from there on you can run: $ adb shell ls / or whatever you need to run. Marcelo _______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
