Looking at the sources, it might be possible. If the ro.secure property is *not* set (and I believe that it is always set for typical device builds), then the adbd daemon will listen for requests on localhost port 5037. The problem is I'm really unsure that everything is going to work fine if an external client ever tries to access it (which would at a minimum require some amount port forwarding currently). The adb client expects the server to do some sort of transport switching/tunneling and it's likely that some features will not work properly due to this.
However, I agree it is desirable for core platform development to allow direct connection to the device. This may need some work though but I'll keep in mind when working on it in the near future. On Wed, Jan 21, 2009 at 7:15 AM, Mike Lockwood <[email protected]> wrote: > > It sounds like Divya wants to do this to develop on an OMAP > development board, not a real phone. In that case, the security issue > probably is not important. > > Wouldn't it be possible to modify adbd to listen for connections on > external ports and connect to it from a PC over ethernet? I thought I > heard someone had gotten that working in the x86 port. > > Mike > > On Wed, Jan 21, 2009 at 7:04 AM, David Turner <[email protected]> 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). > > > > On Wed, Jan 21, 2009 at 6:35 AM, divya <[email protected]> wrote: > >> > >> Hi, > >> > >> I have succefully got the android up and running on OMAP 3430. But > >> now I want to use adb tool to push applications on to the device and > >> also for debugging. > >> > >> I have assigned my OMAP 3430 board an IP. How can now connect to > >> the board using a windows machine(host). > >> > >> After searching for this information I have got a way from a linux > >> machine using the below commands: > >> > >> # Killall –a adb > >> # export ADBHOST=<target ip address> > >> # adb shell > >> > >> Is this right for linux host? Do we have the same for a windows > >> machine?.. > >> > >> Any information is welcome.... > >> > >> Regards, > >> Divya > >> > >> > >> > > > > > > > > > > > > > -- > Mike Lockwood > Google android team > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
