[REQUEST] Wireless ADB

[JeepFreak]

Test it in a Terminal but it shouldnt work without root... otherwise it is a security issue on android/your ROM.

It worked for me without SU. I didn't use gscript either.
Billy

 

[ScottHW]

Wireless = over 3G?

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

 

[djmcnz]

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

Nope... couldn't route from public to private network... well perhaps if you did some reverse proxy magic but that's going to be a lot of effort and routing config.

 

[ScottHW]

adb terminal output problem

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

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]

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?

.

 

[ScottHW]

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

alias ls='ls --color=never'

But you have to redo it every time you restart adb

 

[evgeny9]

Not working

Unfortunately, it does not work for me on rooted Samsung Galaxy Ace (Android 2.3.6):

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?

 

[baseballfanz]

Unfortunately, it does not work for me on rooted Samsung Galaxy Ace (Android 2.3.6):

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.

 

[evgeny9]

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

Thanks, but I'd like to make it working without any 3rd party apps and, besides that, to have an opportunity to use ADB on Wi-Fi on unrooted phones also.