Yes the security aspect is important so I agree with the suggestion.
However, I think I did try something along these lines a while back
but it didn't work. Is this the right approach? With the phone on USB:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
Rebooting the phone removed the property.
Thanks
On Aug 27, 1:15 pm, Chris Stratton <[email protected]> wrote:
> On Saturday, August 27, 2011 11:03:26 AM UTC-4, kypriakos wrote:
>
> > What does the "adb connect" do exactly? Not much info on the adb page
> > about it.
>
> You would use it to connect to a device which has an adbd listening on
> something other than the USB, for example listening on TCP so that you can
> have ADB over wireless (or even wired ethernet on some non-handheld
> platforms).
>
> For something you would leave running, ssh could be preferable as ADB has no
> security.
>
> In either case though, excepting system-level debugging its probably
> preferable to have the daemon started/stopped by an android app control
> panel, with status bar notification while it is on, so that you only have it
> on when you expect to be using it.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
