Device disconnects when the screen is locked/unlocked, using ADB TCPIP

[inaciopestana]

So, I use Scrcpy for a white. In my old phone, when a TCPIP ADB connection was established, I could lock/unlock the phone screen (both using the physical button and the shortcuts on Scrcpy) and the Scrcpy connection stay active.

Now with my new phone (Samsung S25, Android 16), this behavior seems to have change. Everytime I lock/unlock the screen while using the Scrcpy, the scrcpy screen closes.

I have read this: https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#device-disconnected, that states that "If scrcpy stops itself with the warning "Device disconnected", then the adb connection has been closed.", but this is not seems to be true in my case because, if i launch Scrcpy again after the scrpy windows was closed due to lock/unlock screen, it connects right away with the device again.

So, it seems that the screen lock/unlock is temporarly killing the adb connection, but now entirely. Is there a fix to this, so Scrcpy could behave as it uses to behave (like in my previous phone, the Samsung S23)?

Thanks.

[rom1v]

https://github.com/Genymobile/scrcpy/issues/2995#issuecomment-1029114499 https://github.com/Genymobile/scrcpy/issues/1382#issuecomment-627591729

[inaciopestana]

Thanks, dev. You can close the incident.

For those who are wondering, just go to "Developer options", then set the "USB default configutation" to "Charging" on the Samsung S25 device.

[Mmanish7]

Thanks, dev. You can close the incident.

For those who are wondering, just go to "Developer options", then set the "USB default configutation" to "Charging" on the Samsung S25 device.

What about wireless?