Re: Do you use ADB (or ScreenCopy) with Android & Windows?

On 9 May 2025 14:58:37 GMT, Frank Slootweg wrote :

"Note: All adb clients use port 5037 to communicate with the adb server.
 The server then sets up connections to all running devices. It locates
 emulators by scanning odd-numbered ports in the range 5555 to 5585,
 which is the range used by the first 16 emulators."
 
From:
 
'How adb works'
<https://developer.android.com/tools/adb#:~:text=Note%3A%20All%20adb%20clients%20use,by%20the%20first%2016%20emulators.>

Frank,

My problem with you is your attitude.
Sometimes you are an asshole. Sometimes you're not an asshole.

It's random for you.
I react to you the way you unilaterally talk about me, Frank.

I'm a mirror of your own attitude.
Don't forget that.

The record will show that my reaction to you is not random in that I react
to you being an adult as befitting an adujlt conversation. And yet, when
you are an asshole, Frank - I treat you like you are. Remember that.

It's *always* you unilaterally being the asshole first, Frank.

Think about that.
It's been decades so you should figure that out by now.

When you are being an asshole - I tell it to you Frank.
You don't like that. Sure. But then don't be an asshole Frank.

You know NOTHING about this problem set Frank.
You being an asshole is compounded by your utter ignrance, Frank.

So cut the crap, Frank.
Act like an adult.

You're wrong that you can't change the port that ADB uses, Frank.

I already proved you can assign the port that ADB uses, which I had done,
years ago, in an attempt to get around Android adb Wi-Fi security in around
Android 10/11 time frames.
    C:\> set | findstr /i adb
          ANDROID_ADB_SERVER_PORT=55555

To test if that was why adb was using port 55555, here's what I did...
 C:\> set ANDROID_ADB_SERVER_PORT=

Bingo!

Now adb on Windows is using the port that everyone else sees it using!
 C:\> adb devices
      * daemon not running; starting now at tcp:5037
      * daemon started successfully
      List of devices attached
      SMSGA325GV1     device

OK. So this happens to be the answer to the 3 questions...I think.
 Q1: What port does *your* Windows adb use?
 A1: TCP:5037 (by default, unless you change it, which you can)

 Q2: Where is that port set inside of the Windows adb tool?
 A2: If you need to change the adb default, you can use:
     C:\> setenv ANDROID_ADB_SERVER_PORT 55555
     Win+R > sysdm.cpl > Advanced > Environment Variables
     System Variables > ANDROID_ADB_SERVER_PORT
  
 Q3: On Windows, what did you do to *reserve* that port?
     If it's below 1024, you don't have to do anything.
     If it's above 1023, and it's TCP, you should reserve the port.
     C:\> netsh int ipv4 add excludedportrange protocol=tcp startport=55555 numberofports=1
     [Note: Winnat with UDP uses a different set of random ports.]

If you do not reserve any port above the privileged ports,
for TCP (it's a different set for UDP) then you'll be sorry
if you also turn on Hyper-V (which Docker & WSL might do).

I consider this technical problem resolved with this information.