From: mariasophia@comprehension.com   
      
   Maria Sophia wrote:   
   > Shizuku is finally paired & running but it took about an hour of doing the   
   > same steps over and over and over again. Seriously. It's that sensitive.   
      
   ============================   
     SAMSUNG SHIZUKU RITUAL   
   ============================   
      
   1. Reboot the phone   
      
   2. Enable Shizuku notifications   
      a. Settings > Apps > Shizuku   
      b. Notifications > Allow   
      
   3. Connect to home Wi-Fi   
      
   4. Open Developer options   
      a. USB debugging: ON   
      b. Wireless debugging: ON   
      
   5. Reset wireless debugging state   
      a. Developer options > Wireless debugging   
      b. Select "Forget all pairs"   
      
   6. Prepare split-screen   
      a. Open Shizuku   
      b. Put Shizuku in split-screen TOP   
      c. Open Developer options > Wireless debugging in split-screen BOTTOM   
      
   7. Start pairing   
      a. In bottom half: select "Pair device with pairing code"   
      b. Note the pairing code and IP:PORT   
      
   8. Trigger Shizuku pairing   
      a. In top half: select "Start via Wireless debugging"   
      b. Enter the pairing code   
      c. Accept the system pairing prompt   
      
   9. Confirm service is running   
      a. Return to Shizuku main screen   
      b. Look for: "Shizuku is running"   
      
   Once Shizuku is running, it stays alive only as long as the ADB-over-Wi-Fi   
   session stays valid, but that session is extremely flaky in and of itself.   
      
   ============================   
     WHAT WILL KILL SHIZUKU   
   ============================   
      
   1. Rebooting the phone   
      a. Always wipes the ADB-over-WiFi session.   
      
   2. Turning off Wireless debugging   
      a. Even a brief toggle kills Shizuku.   
      
   3. Losing Wi-Fi connection   
      a. Wi-Fi drop   
      b. Router reboot   
      c. Switching to another network   
      
   4. Changing IP address   
      a. Phone gets a new LAN IP   
      b. Router assigns a new IP   
      c. Switching between 2.4 GHz and 5 GHz on some routers   
      
   5. Turning on Airplane mode   
      a. Disables Wi-Fi   
      b. ADB session dies instantly   
      
   6. Turning off USB debugging   
      a. Restarts the ADB daemon   
      b. Shizuku loses its bridge   
      
   7. Forgetting all pairs   
      a. Developer options > Wireless debugging > Forget all pairs   
      
   8. Battery saver or aggressive power modes   
      a. Samsung may suspend wireless debugging   
      b. Some models kill background ADB sessions   
      
   9. Long idle lockscreen time   
      a. Some Samsung builds suspend wireless debugging after extended idle   
      
   10. Switching Wi-Fi networks   
       a. Home Wi-Fi to mobile hotspot   
       b. Home Wi-Fi to work Wi-Fi   
       c. Any network change resets ADB   
      
   Anything that resets ADB, Wi-Fi, or pairing will kill Shizuku.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)