Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48626 - [android-tools] adb tcpip not working

Attached to Project: Community Packages
Opened by Denys Vitali (denvit) - Friday, 18 March 2016, 07:28 GMT
Last edited by Jonathan Roemer (pid1) - Thursday, 08 September 2016, 21:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading from android-tools 6.0.1_r16-1 to 6.0.1_r22-1 the `adb tcpip` is broken, I was unable to connect with my Pixel C over wifi.
Downgrading to 6.0.1_r16-1 solved the problem.

Additional info:
* Package version affected: 6.0.1_r22-1
* No config / log available


Steps to reproduce:
Connect the device via USB
Kill an eventually open adb server with `adb kill-server`
Start adb with `adb tcpip`
Connect to the device's ip address with for example `adb connect 10.96.2.67`
Check the result, is it able to connect?
This task depends upon

Closed by  Jonathan Roemer (pid1)
Thursday, 08 September 2016, 21:10 GMT
Reason for closing:  Not a bug
Comment by Anatol Pomozov (anatolik) - Saturday, 19 March 2016, 18:47 GMT
I see only minor adb changes between r16 and r22 nothing should affect the network behavior.

In fact by default I cannot connect neither with old nor new adb. I need to restart adbd at the device first. Check my worklog below


$ adb kill-server
$ adb tcpip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
$ adb connect 10.0.0.15
unable to connect to 10.0.0.15:5555

^^^ This is what you see ^^^^
.... Let's connect USB and restart adbd with port number ...

$ adb shell
shell@bullhead:/ $ getprop service.adb.tcp.port

^^^^ Port number is not set ^^^^
shell@bullhead:/ $ setprop service.adb.tcp.port 5555
shell@bullhead:/ $ stop adbd
shell@bullhead:/ $ start adbd
shell@bullhead:/ $

.... Disconnect USB, let's connect over wifi ....

$ adb kill-server
$ adb tcpip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
invalid port 0
$ adb tcpip 5555
restarting in TCP mode port: 5555
$ adb connect 10.0.0.15
connected to 10.0.0.15:5555
$ adb shell

^^^ Here we go, using adb over wifi ^^^^^

Loading...