From Newsgroup: comp.mobile.android
I never fully understood networking - as I never had much problems.
However... this happens: <
https://i.postimg.cc/28n8vs1j/adb-port-55555.jpg>
Background:
1. I boot up the PC & I use adb every day, all day, while I'm at home.
2. My phone is always connected by USB or Wi-Fi over adb on Windows 10.
3. Mostly I use adb to mirror Android onto Windows when I'm at my desk.
This way I can operate the Android phone using the Windows PC hardware (keyboard, mouse, display, speakers, microphone, clipboard).
I shut down every night and every once in a while the adb default port is "broken" for reasons unknown to me. This happens infrequently - but it
happens enough that I need a better debugging technique.
Normally rebooting solves the problem but why should I not know what is
hanging up port 55555 (adb over Wi-Fi) and/or port 5555 (adb on USB)?
Below is the log of what you see in the screenshot.
While a reboot will almost certainly solve it, why should I need to boot?
Q: Do you have advice on how to fix what is using adb default ports?
<
https://i.postimg.cc/28n8vs1j/adb-port-55555.jpg>
C:\app\editor\android\scrcpy>adb devices
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
adb.exe: failed to check server version: cannot connect to daemon
C:\app\editor\android\scrcpy>adb connect 192.168.1.4:55555
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
C:\app\editor\android\scrcpy>usb
scrcpy 1.24 <
https://github.com/Genymobile/scrcpy>
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
ERROR: "adb start-server" exited unexpectedly
ERROR: Could not start adb daemon
ERROR: Server connection failed
C:\app\editor\android\scrcpy>scrcpy -s 192.168.1.4
scrcpy 1.24 <
https://github.com/Genymobile/scrcpy>
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
ERROR: "adb start-server" exited unexpectedly
ERROR: Could not start adb daemon
ERROR: Server connection failed
C:\app\editor\android\scrcpy> adb connect 192.168.1.4:38287
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
C:\app\editor\android\scrcpy> adb pair 192.168.1.4:37011
Enter pairing code: 253341
* daemon not running; starting now at tcp:55555
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
C:\app\editor\android\scrcpy>netstat | findstr 55555 C:\app\editor\android\scrcpy>nmap -vvv 192.168.1.4 -p 55555
Starting Nmap 7.93 (
https://nmap.org ) at 2024-07-19 08:57 Central
Daylight Time
Initiating ARP Ping Scan at 08:57
Scanning 192.168.1.4 [1 port]
Completed ARP Ping Scan at 08:57, 0.23s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 08:57
Completed Parallel DNS resolution of 1 host. at 08:57, 0.03s elapsed
DNS resolution of 1 IPs took 0.19s. Mode: Async [#: 2, OK: 0, NX: 1, DR: 0,
SF: 0, TR: 1, CN: 0]
Initiating SYN Stealth Scan at 08:57
Scanning 192.168.1.4 [1 port]
Completed SYN Stealth Scan at 08:57, 0.07s elapsed (1 total ports)
Nmap scan report for 192.168.1.4
Host is up, received arp-response (0.13s latency).
Scanned at 2024-07-19 08:57:14 Central Daylight Time for 0s
PORT STATE SERVICE REASON
55555/tcp closed unknown reset ttl 64
MAC Address: 3E:56:75:5C:0C:DB (Unknown)
Read data files from: C:\app\network\scanner\nmap
Nmap done: 1 IP address (1 host up) scanned in 0.93 seconds
Raw packets sent: 2 (72B) | Rcvd: 2 (68B)
--- Synchronet 3.20a-Linux NewsLink 1.114