My bad, Brian's right, to activate this, you need however to be sure that: - the ro.secure property is *not* set when the adbd daemon is launched - /dev/android_adb or /dev/android do *not* exist
I naively assumed that you had the adb device on your system. On Wed, Jan 21, 2009 at 9:51 PM, Brian Swetland <swetl...@google.com> wrote: > > > I think David is confusing the transport-over-IP feature which adbd on > the device will fail back to if it can't open the usb device driver with > the local adb control socket on the device which was disabled to avoid > possible security issues (potentially giving untrusted apps debugging > access to the world via adb). > > The IP transport stuff is a little cranky at times, but obviously does > work (and I've used it during bringup on boards where USB was not > working but an ethernet interface was). > > [Sean McNeil <seanmcne...@gmail.com>] > > > > Huh? I do this all the time. I setup ethernet over USB and then connect > > to the phone with: > > > > ADBHOST=192.168.0.202 adb kill-server > > ADBHOST=192.168.0.202 adb command > > > > I don't know what you mean that it isn't possible. I guess I'm doing the > > impossible, then. ;) > > > > David Turner wrote: > > > This is not currently possibe. > > > > > > First of all, you need to understand that there are 3 components to > ADB: > > > > > > - the 'adbd' daemon that runs on the device > > > - the 'adb server' that runs as a background process on the host > > > development machine > > > - the 'adb client', which can be either the adb executable or DDMS, > > > which communicate with the server > > > > > > the 'adbd' daemon that runs on a real device only listens to the USB > > > communication channel, and it simply is not possible to make it listen > > > to an IP address. consequently, the 'adb server' must run on a host > > > machine that is connected to the device through USB > > > > > > I believe these limitations are here for security reasons. You > > > certainly don't want anyone on the network be able to access the adbd > > > daemon on your device by default. > > > > > > ADBHOST is a relic of ancient code that has been removed for security > > > reasons. Its handling is probably broken and will not work as you > > > expect it to, and the best it could do is connect an adb client > > > running on machine A to an adb server running on machine B; which is > > > not exactly what you're looking for (and if the latter interests you, > > > you probably should better use SSH port forwarding to do that > securely). > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
