XPost: alt.comp.os.windows-10, comp.mobile.android   
   From: spam@nospam.com   
      
   Andy Burns wrote:   
      
   >> Why can't adb establish a connection all by itself over Wi-Fi?   
   >   
   > Are you querying the need for a QR code or pairing-code to be entered?   
      
   Hi Andy,   
      
   I think I figured out the problem.   
      
   I have never seen a QR code, nor a "pairing code", per se, but of course,   
   there is a pairing process over USB with adb & the phone that is almost   
   automatic where it simply asks me to accept it and remember it when the   
   pairing is initially established.   
      
   The problem was that the pairing only happened over USB (not over Wi-Fi).   
   I could only pair over USB (& then I could use the connection over Wi-Fi).   
      
   But I think I solved that problem just now when I tried to test it again.   
      
   Today I started fresh by killing adb on Windows (C:\> adb kill-server),   
   and then I revoked all previous pairing credentials on the phone.   
    Android 12 Developer options > Revoke USB debugging authorizations   
      
   Then I set the Android "Wireless debugging" option on. <== this is new!   
    Android 12 Developer options > Wireless debugging = On   
      
   In addition to these two Android settings which I had already turned on.   
    Android 12 Developer options > USB debugging = On   
    Android 12 Developer options > Disable adb authorization timeout = On   
      
   So that the Android developer options USB settings looked like this.   
        
      
   > I'd have   
   > though that was a worthwhile security "bump" so that Johnny Hacker can't   
   connect   
   > to your phone without an action from you ...   
      
   I just wanted to get rid of the USB cable, that's all.   
   I think I solved it by setting "Wireless debugging = On" though.   
      
   Now I can connect adb to the phone over Wi-Fi _without_ needing the USB   
   cable in the beginning to establish the initial connection credentials.   
      
   1. With the phone _not_ connected over USB but only over Wi-Fi to your LAN.   
   2. On the PC, kill the adb server (to get to a known good starting point).   
      C:\> adb kill-server   
   3. On the phone, wipe out existing credentials (for a good start point).   
      Android 12 Developer options > Revoke USB debugging authorizations   
   4. C:\> adb tcpip 5555   
           error: no devices/emulators found   
   5. C:\> adb connect 192.168.0.2:5555   
           failed to authenticate to 192.168.0.2:5555   
      But, after about 30 seconds, this pops up a query   
           "Allow USB debugging?" on your phone, and   
           (o)Always allow from this computer   
   6. C:\> adb tcpip 5555   
           restarting in TCP mode port: 5555   
   7. C:\> adb devices   
           List of devices attached   
           192.168.0.2:5555       device   
      
   Who knew?   
   Not me.   
      
   In summary, my recent experience has been that...   
   A. Pairing between adb & the phone "just works" over USB, and,   
   B. Once paired over USB, then Wi-Fi connections "just work" also, but,   
   C. You need that extra switch to be on to do the pairing step over Wi-Fi.   
      Android 12 Developer options > Wireless debugging = On   
      
   These are the settings that worked completely over Wi-Fi (no USB needed).   
        
   --   
   On Usenet, kind hearted people try to help each other all day every day.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)