What is the port number then? is it 5037? Can I set it somewhere? (for rooted devices of course)
Thats what i search but cant get it to work from the phone wirhout first plugging the usb..
Sent from my Nexus One
What is the port number then? is it 5037? Can I set it somewhere? (for rooted devices of course)
setprop service.adb.tcp.port 5555
stop adbd
start adbd
setprop service.adb.tcp.port -1
stop adbd
start adbd
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.
search adbwireless in market - there is a app
i can´t post links :-/
search adbwireless in market - there is a app
i can´t post links :-/
I say that but it need root access and I don't know why?! the commands I posted here do not want root access and using an script app you can create two scripts to use enable/disable it without (I believe) root access.
Aehm... you said in an earlier post that it needs su and thats basically root... (su = super user)
I say that but it need root access and I don't know why?! the commands I posted here do not want root access and using an script app you can create two scripts to use enable/disable it without (I believe) root access.
He wasn't complaining that the app isn't working or is useless, he just questions that it needs root and there's nothing wrong if a user doesn't just allow every app SU access.It works perfectly and you have already rooted your phone according to your sig so why bother complaining and stating that it's "useless" when in fact you're wrong?
setprop service.adb.tcp.port 7896
getprop service.adb.tcp.port
He wasn't complaining that the app isn't working or is useless...
He wasn't complaining that the app isn't working or is useless, he just questions that it needs root and there's nothing wrong if a user doesn't just allow every app SU access.
I mostly prefer open source apps (don't know if the above app is OS) in this case because I can check what its doing and compile it myself or I have the tools and knowledge to see what exactly closed source app do but most users have not and a trust all policy isn't good (even the app is on the Google Market).
@bohlool
I just tested it and it doesn't work (like I thought) without requesting su access.
The part with the setprop command doesn't do anything if it's not executed from root user.
You can check it with:
Second command should give back the number you entered above.Code:setprop service.adb.tcp.port 7896 getprop service.adb.tcp.port
The setprop command doesn't return anything if it succeeds or fails, that's why you need to use the getprop to verify the value.
Interesting, because it work for me without su, I tested your command and it return the port number. I used gscript to run scripts without su and it worked. I should test it on an unrooted phone.
Sorry about the title, but an application that need more permission that it really need is useless to me, I cannot trust app, giving su permission to an unknown app specially while it doesn't need it.
Test it in a Terminal but it shouldnt work without root... otherwise it is a security issue on android/your ROM.
I was not talking about giving root access (this is a security hole a user opens because he wants to) but he was talking about that this is working without granting SU access and if this would be (but isn't from my testing) it would be a major security issue (not regarding exactly this but overwritting system properties with setprop from any app without root access).Not really...
I agree that giving root acces with adb over wifi like ssh might be a security issue.
BUT you need to be on the same wifi network plus activate usb debugging.
By that I mean that if it happens then you should be aware of what you did with your development settings.
setprop service.adb.tcp.port 5555
stop adbd
start adbd
setprop service.adb.tcp.port -1
stop adbd
start adbd
[I]# detach adbd from usb and tell it to listen to port tcp 2222
[/I]packetlss@wopr$ 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]packetlss@wopr$ adb connect 192.168.0.151:2222
connected to 192.168.0.151:2222
[I]# connect over ip
[/I]packetlss@wopr$ 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]packetlss@wopr$ adb usb
restarting in USB mode
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.