Connection is rejected after unplugging the device from computer

[rdlf4]

So, this has happened to me all the time I need to recharge my phone, and I do so by plugging it to my computer. But normally, after it's been charged and unplugged, trying to connect to my phone again via wireless by issuing the command

adb connect 192.168.0.101

returns me with an error:

unable to connect to 192.168.0.101:5555: Connection refused

Then, I have to plug it to my computer again, do the same as I did before:

adb forward tcp:5555 tcp:7612

And then, do:

adb tcpip 7612

So that, my phone returns:

restarting in TCP mode port: 7612

And then, it finally connects.

My question is, why is it that every time I unplug it from my computer, it no longer works in TCP mode? Can't I leave it like that, in order to not have to re-do those steps after unplugging my device?

[rom1v]

Indeed, on some devices, disconnecting the USB cable breaks the adb-over-tcp connection. There are several threads about this on stackoverflow, but no real solution AFAIK.

[rdlf4]

I can confirm this issue is still present on v1.12.
With my device connected via USB, I do adb tcpip 5555. Right after that, Scrcpy has no problem to find and connect to my phone. However, after restarting my computer, my phone returns:

unable to connect to 192.168.0.101:5555: Connection refused

For those who're wondering, I have no port-managing app on my phone nor any Firewall.
And yes, my computer can still ping to my phone.

[rom1v]

I can confirm this issue is still present on v1.12.

The issue is independant from scrcpy, it's just adb.

https://stackoverflow.com/questions/33462720/adb-unable-to-connect-to-192-168-1-105555

[dbdonb]

I can confirm this issue is still present on v1.12.
With my device connected via USB, I do adb tcpip 5555. Right after that, Scrcpy has no problem to find and connect to my phone. However, after restarting my computer, my phone returns:

unable to connect to 192.168.0.101:5555: Connection refused

For those who're wondering, I have no port-managing app on my phone nor any Firewall.
And yes, my computer can still ping to my phone.

Hi,

Were you able to fix that issue?

The same happens to me. Once I restart my computer or the phone, I'm forced to connect Phone via USB and then enable adb over TCP everytime.

[rdlf4]

I can confirm this issue is still present on v1.12.
With my device connected via USB, I do adb tcpip 5555. Right after that, Scrcpy has no problem to find and connect to my phone. However, after restarting my computer, my phone returns:

unable to connect to 192.168.0.101:5555: Connection refused

For those who're wondering, I have no port-managing app on my phone nor any Firewall.
And yes, my computer can still ping to my phone.

Hi,

Were you able to fix that issue?

The same happens to me. Once I restart my computer or the phone, I'm forced to connect Phone via USB and then enable adb over TCP everytime.

Hello.
I was not able to fix it. However, there's a chance my computer will connect to my phone without having to plug it to my computer and re-enable adb-over-tcp connection. It's a hit or miss thing. But when that happens, it performs really really slow. My phone takes longer to detect a click event and scrolling is also affected. Really weird.
Checked my router's firewall - including LAN Firewall to see whether there are ports that have been restricted or blacklisted, but there's nothing there.

I'm in the dark and out of ideas.

[dbdonb]

I can confirm this issue is still present on v1.12.
With my device connected via USB, I do adb tcpip 5555. Right after that, Scrcpy has no problem to find and connect to my phone. However, after restarting my computer, my phone returns:

unable to connect to 192.168.0.101:5555: Connection refused

For those who're wondering, I have no port-managing app on my phone nor any Firewall.
And yes, my computer can still ping to my phone.

Hi,
Were you able to fix that issue?
The same happens to me. Once I restart my computer or the phone, I'm forced to connect Phone via USB and then enable adb over TCP everytime.

Hello.
I was not able to fix it. However, there's a chance my computer will connect to my phone without having to plug it to my computer and re-enable adb-over-tcp connection. It's a hit or miss thing. But when that happens, it performs really really slow. My phone takes longer to detect a click event and scrolling is also affected. Really weird.
Checked my router's firewall - including LAN Firewall to see whether there are ports that have been restricted or blacklisted, but there's nothing there.

I'm in the dark and out of ideas.

Hi,

Thanks for the quick response.

Looks like it automatically disables the adb tcp connection after sometime of idle, something similar the "remember me" cookies on websites. I hope that's not the case though.

[rdlf4]

I'll have a look into that once I get back home.
I just hope this isn't anything that requires rooting the phone in order to change or even disable it.

[dbdonb]

I'll have a look into that once I get back home.
I just hope this isn't anything that requires rooting the phone in order to change or even disable it.

Sure, keep us posted at your convenience. Thanks.

[cardboardcode]

@rdlf4
Hi all, I encountered a similar error to yours as I was setting up the wireless use of scrcpy. I managed to resolve my issue using the following step.

[Possible Solution]

Enable Allow ADB Debugging in charge only mode as shown in the picture attached.
[Stackoverflow Reference]

Hopefully this helps.

If this is indeed the problem, we will need to update the setup instructions for scrcpy wireless connection in the README.md. @rom1v I will be glad to do a quick Pull Request to update the documentation.

[rom1v]

If that's the problem, yes, you could submit a new entry in FAQ.md 👍

[rdlf4]

@cardboardcode Thanks for taking the time to look into this.
Unfortunately it seems that option you mentioned isn't available for Android 7.x-based devices, mine included. Matter fact, it seems I can only Enable USB debugging, revoke authorizations, and that's it.
As you can see from the screenshot attached.

Question is, where do I go from here? :/

[cardboardcode]

@rdlf4
It seems the suggested solution only applies to devices of Android 8.0 and above.

Since I am not an expert on this issue, I can only recommend a crude workaround or generic advice:

1. Upgrade to Android 8.0 and above.
2. Find the equivalent to Allow ADB Debugging in charge only mode within Android 7.0.

@rom1v
It does not seem to be the problem, at least in the specific context of this issue thread.