adb over ethernet and not over USB

[a druid]

Hi,

I wondered, whether I could use adb over ethernet instead of adb over
USB

Looking at the forums I did not really understand, whether this is
feasible, was feasible, would be easy to
accomplish.

Thanks in advance for any pointer / suggestions.

I saw mentioning of an obsolete environment variable ADBHOST,
but no up to date discussion about adb over ethernet

Does anybody know more?


Thanks in advance for any pointers

[RongJun Ying]

Try this:

# ADBHOST=[you host ip address] ./adb -d devices

-----------------------------
Ying RongJun China

[a druid]

On Apr 17, 12:00 pm, RongJun Ying <rjy...@gmail.com> wrote:
> Try this:
>
> # ADBHOST=[you host ip address] ./adb -d devices
>

This is what I tried:
On the device to be debugged netstat returns this:
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 127.0.0.1:5037 0.0.0.0:*
LISTEN
tcp 0 0 0.0.0.0:5555 0.0.0.0:*
LISTEN
udp 0 0 0.0.0.0:962
0.0.0.0:*
#

Does this mean, that the application is listening on the debug port?
Which port should the device be listening for debug to be working.
If it is not lsitening How to I have to start adbd to be listening on
ehternet?



ADBHOST=[you host ip address] ./adb kill-server ;

ADBHOST=[you host ip address] ./adb -d device

only returns the emulator if one is running (or nothing if none is
running)

How can I find out whether the problem is on the adbd side or the adb-
server side?

thanks for any further suggestions



> -----------------------------
> Ying RongJun China

[a druid]

Hello,


No idea, what I made wrong. I retried and now it's working.


The correct steps seem to be
adb kill-server
ADBHOST=ip_address adb <command>


thanks again.

On Apr 17, 12:00 pm, RongJun Ying <rjy...@gmail.com> wrote:

> Try this:
>
> # ADBHOST=[you host ip address] ./adb -d devices
>
> -----------------------------
> Ying RongJun China
>

[a druid]

Hi,

It's working now. No idea, what I made wrong.

What is important though is to kill the previous server.
> ADBHOST=[you host ip address] ./adb kill-server
> ADBHOST=[you host ip address] ./adb devices


what is a little confusing though is, that the output of "./adb
devices"
is dentical between a real device and an emulated device.


Thanks again and bye

On Apr 17, 12:00 pm, RongJun Ying <rjy...@gmail.com> wrote:

> Try this:
>
> # ADBHOST=[you host ip address] ./adb -d devices
>
> -----------------------------
> Ying RongJun China
>

[RongJun Ying]

Sorry,
The "-d" arg is not needed.

-d means connecttion via the USB.

---------------------------------------
Ying RongJun China

[anantvijayk]

hi,

I have OMAP3EVM with the kernel and root filesystem from the mistral's
site. the device is up and everything works fine.

The device is connected through ethernet port on board. The target
device has an ip assigned and is reachable by the other machines.

I'm trying to run adb over ethernet.

My pc ip: 192.168.102.130
My device ip: 192.168.101.56

Here are the steps i ran from my pc:
# ADBHOST=192.168.101.56 adb kill-server
# ADBHOST=192.168.101.56 adb shell

output:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

Also the netstat on the target device gave me this:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:5037 0.0.0.0:*
LISTEN

udp 0 0 0.0.0.0:619 0.0.0.0:*
LISTEN

My netstat does not show this line when compared with yours:

tcp 0 0 0.0.0.0:5555 0.0.0.0:* LISTEN

how do i get this line in my netstat on device?
Any config i'm missing??

thanks in advance,
Anantvijay

> > > Thanks in advance for any pointers- Hide quoted text -
>
> - Show quoted text -