[REQUEST] Wireless ADB

Search This thread

ScottHW

Senior Member
Sep 23, 2010
160
29
Wireless = over 3G?

Is it possible to use adb over a cell network with a method similar to this?
 

ScottHW

Senior Member
Sep 23, 2010
160
29
adb terminal output problem

I think messing around with this screwed up my adb output somehow, because now I'm having this problem

Code:
C:\adb\android-sdk-windows\tools>adb shell ls -al
drwxr-xr-x   14 0        0                0 Jun  9 12:26 ←[1;34m.←[0m
drwxr-xr-x   14 0        0                0 Jun  9 12:26 ←[1;34m..←[0m
drwxr-xr-x    3 0        0                0 Jun  9 12:26 ←[1;34macct←[0m
drwxrwx--x    1 1000     2001          2048 Jun  9 09:15 ←[1;34mcache←[0m
dr-x------    2 0        0                0 Jun  9 12:26 ←[1;34mconfig←[0m
lrwxrwxrwx    1 0        0               17 Jun  9 12:26 ←[1;36md←[0m -> ←[1;34m/sys/kernel/debug←[0m

Apparently, it's related to ls terminal color output...?
http://forum.xda-developers.com/showthread.php?t=653429

I never had this problem before. I'm using Win7 (64-bit)
 

leecavturbo

Senior Member
Jul 27, 2010
693
18
just been having a play. hope i don't get your problem above.
i just wanted initially to play and try screencast (which works over wifi) but have since realised i'd like to push apk's and other stuff as you can when usb connected. so can windows recognize the device as connected via usb? so it shows in device manager?
adbwireless3.jpg

.
 
Last edited:

ScottHW

Senior Member
Sep 23, 2010
160
29
I think messing around with this screwed up my adb output somehow, because now I'm having this problem
....
I never had this problem before. I'm using Win7 (64-bit)

Small upate: I noticed that I actually only have the problems with ls -al when the phone is fully booted. When I use adb booted in Recovery (CWM) the file listings are fine.

It's possible that I have never used adb while the phone is fully booted before, and just assumed that the Recovery behavior was universal and when I got the funky behavior, it wasn't messing around with ADB, it was just because I didn't know what "normal" was.

Short term fix is still just to use an alias for ls
Code:
alias ls='ls --color=never'
But you have to redo it every time you restart adb :(
 
Last edited:

evgeny9

Senior Member
Jan 26, 2012
52
8
Not working

Unfortunately, it does not work for me on rooted Samsung Galaxy Ace (Android 2.3.6):
Code:
C:\android>adb tcpip 5555
restarting in TCP mode port: 5555

C:\android>adb connect 192.168.0.115
unable to connect to 192.168.0.115:5555
Couldn't you help me with this problem?
 
Last edited:

baseballfanz

Senior Member
Oct 19, 2010
6,829
1,702
Sugar Land TX
Samsung Galaxy A52 5G
Unfortunately, it does not work for me on rooted Samsung Galaxy Ace (Android 2.3.6):
Code:
C:\android>adb tcpip 5555
restarting in TCP mode port: 5555

C:\android>adb connect 192.168.0.115
unable to connect to 192.168.0.115:5555
Couldn't you help me with this problem?

Just get the wireless ADB app from Play Store. It had work on all my rooted app.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    Solved

    I finally solved the problem. these are the commands to enable adb over wifi:


    Code:
    setprop service.adb.tcp.port 5555
    stop adbd
    start adbd

    and to disable it:


    Code:
    setprop service.adb.tcp.port -1
    stop adbd
    start adbd


    I assume you need su access to run it. I tested it and its working.
    3
    Getting adbd to listen to tcpip in the phone is quite easy.

    Example below:
    Code:
    [I]# detach adbd from usb and tell it to listen to port tcp 2222
    [/I][email protected]$ adb tcpip 2222
    restarting in TCP mode port: 2222
    
    [I]# tell your local adb command to use ip:port to connect through instead of usb (192.168.0.151 is my N1 on Wifi)
    [/I][email protected]$ adb connect 192.168.0.151:2222
    connected to 192.168.0.151:2222
    
    [I]# connect over ip 
    [/I][email protected]$ adb shell
    # uname -a
    Linux localhost 2.6.29.6-cyanogenmod #3 PREEMPT Wed Jan 27 07:21:12 EST 2010 armv7l GNU/Linux
    # exit
    
    [I]# tell adbd to go back to listen on usb
    [/I][email protected]$ adb usb
    restarting in USB mode
    1
    Thank you, your method works well.

    With my nook all I need to do is "adb connect 192.168.1.x:5555" I don't have to put adb into tcpip mode or enter "uname -a" in shell.
    I would love to see "Wireless Debugging" in Settings -> Applications -> Development, or really anywhere in Settings. I haven't voided my N1's warranty, so an app to add this functionality would be great.

    That's because the nook adbd is configured to listen to tcp by default, on most other platforms it just listens to USB by default.

    The 'uname -a' was just to show that I actually was connected to the phone. Nothing to do with the actual adb stuff at all, I was just lazy and copied from my terminal :)