Windows client immediately exits after creating ADB forwarding (Samsung M31 / Android 12)

[El4aby7]

Environment:

• VCamdroid: Latest GitHub Release
• Windows 10 22H2 (19045)
• Samsung Galaxy M31
• Android 12

What happens:

• Desktop app launches.
• ADB detects the phone correctly.
• Desktop app creates the expected port forward:
  adb forward --list
  R58N60DJ41K tcp:8554 tcp:8554
• The Android app opens the camera.
• The desktop app immediately closes.
• If I launch the Android app first, the desktop app never connects.
• If I launch the desktop app first, the Android app disconnects shortly after.

vcamdroid.log:

[SERVER] Initialized on port

6969

[ADB:6969] Failed to start
[ADB:8554] Failed to start
[SERVER] Started
[SERVER] Closing...
[SERVER] Closed.

Additional debugging:

• adb devices works correctly.
• Only one adb installation is present.
• adb version is 34.0.4.
• adb forward is created automatically.
• Android logcat does not show a FATAL EXCEPTION for com.darusc.vcamdroid.

Is this a known compatibility issue with Android 12 or Samsung devices, or is there anything else I can [test?](url)