Note that I noticed it's not always the case (Now I tried different bssids still success), but it did solved before.Įnsure the port 5555 is open correctly. Also since I will not able to connect if port is wrong, so nothing to do with port.īecause another pc in the local network already connected, so the other guy have to adb disconnect first, then I can do adb disconnect and adb connect, since only one person can connect at the same time.Ī hotspot ssid name might consists of multiple bssids in (especially you're in office) local network, so you need to ensure your pc try all the hotspot bssids which match the android connected hotspot bssid. This is not ip problem since ping is working and nmap shows 5555 port is open. Note that my case is special, the usb has been disabled for security concerns. * daemon not running starting now at tcp:5037 The disconnect commands also confirm that its 110% offline PS C:\WINDOWS\system32> adb kill-serverĮrror: protocol fault (couldn't read status): Connection reset by peer Notice that the connection first failed, then it said it was connected which is weird behavior to begin with (no matter what, it always failed once and "succeeded" once), and in both instances, the device showed as offline.
These are the events of my command line in Windows PowerShell Admin to demonstrate (Wifi on and debug mode on and confirmed permission when the popup came): So, for me, the PORT needed to be both manually set and used in the connect line!
The adb tcpip 5555 line is not mentioned anywhere here. For me, the important part turned out to be the following line adb tcpip 5555 together with using the port in the IP of my phone like so: adb connect 192.168.1.87:5555 (only using one of them, did not work, i.e: writing the second alone didn't work, writing the first and then excluding the port in the IP also didn't work).
0 kommentar(er)
