Sujet : Re: Do you use ADB (or ScreenCopy) with Android & Windows?
De : marion (at) *nospam* facts.com (Marion)
Groupes : comp.mobile.androidDate : 09. May 2025, 10:34:30
Autres entêtes
Organisation : BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID : <vvki75$2kl0$1@nnrp.usenet.blueworldhosting.com>
References : 1 2 3 4
User-Agent : MacSOUP/2.8.5 (ea919cf118) (Mac OS 10.12.6)
On Fri, 9 May 2025 08:43:13 +0100, Andy Burns wrote :
So here are my questions which only someone using adb can answer.
Q1: What port doesyour Windows adb use?
5037
Q2: Where is that port set inside of the adb tool?
It's the default baked-into adb.exe
Hi Andy,
That's what I had thought. I'm on Android 13. Windows 10.
When I run this, it finds nothing even when adb is connected to Android.
C:\> netstat -ano | findstr "5037"
But when I run this, it finds the adb connection.
netstat -ano | findstr "55555"
TCP 127.0.0.1:8584 127.0.0.1:55555 ESTABLISHED 2668
TCP 127.0.0.1:55555 0.0.0.0:0 LISTENING
11968
TCP 127.0.0.1:55555 127.0.0.1:8584 ESTABLISHED
11968
I guess I should have listed the version of adb, which mine may be old.
Let me check... OK.
C:\> adb --version
Android Debug Bridge version 1.0.41
Version 35.0.2-12147458
Installed as C:\app\android\adb\adb.exe
Running on Windows 10.0.19045
Makes no sense (yet) why my adb uses port 55555 and nobody else's does.
Let me look it up.... oh... oh my... geez... really?... shit....
Apparently, while you can't change the port the adb server on your Windows
machine uses for USB connections (it's fixed at 5037), you can instruct the
adb daemon on your Android device to listen on a different port for network
connections after an initial setup via USB.
Maybe I did that looooooooooooong ago and forgot all about it?
(I would have picked 5555+55 so it might have been me all along.)
I forgot how I did it though... looking it upo... as we speak...