From: mariasophia@comprehension.com   
      
   Maria Sophia wrote:   
   > If that looks easy, it's not because the combination of something   
   > (NovaLauncher UI or Notifications makes the pairing extremely sensitive).   
      
   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.   
      
   Here are idealized steps.   
   ===========================================================   
    SHIZUKU SETUP: THEORY vs REALITY (SAMSUNG EDITION)   
   ===========================================================   
      
   THEORY (8 steps, clean, sane):   
   ------------------------------   
   1. Enable Developer Options   
   2. Enable USB debugging   
   3. Enable Wireless debugging   
   4. Open Shizuku   
   5. Tap "Start via Wireless debugging"   
   6. System shows pairing dialog   
   7. Pair ¡÷ Shizuku starts service   
   8. Done   
      
   REALITY ON SAMSUNG (actual steps):   
   ---------------------------------------   
   1. Disconnect USB (Samsung blocks pairing if USB active)   
   2. Reboot phone (resets stuck ADB daemon)   
   3. Unlock phone (Samsung hides dialogs on lockscreen)   
   4. Switch to Nova 7.0.57 (One UI launcher suppresses popups)   
   5. Enable Shizuku notifications (Samsung blocks pairing dialog if OFF)   
   6. Turn off mobile data (Samsung sometimes routes ADB over LTE)   
   7. Connect to home Wi-Fi (ADB requires same LAN)   
   8. Developer options > Wireless debugging   
   9. Tap Wireless debugging text (hidden submenu)   
   10. Tap "Forget all pairs" (clear stale ADB sessions)   
   11. Turn USB debugging ON   
   12. Turn Wireless debugging ON (new IP:PORT appears)   
   13. Open Shizuku in split>screen top (forces popup visibility)   
   14. Open Wireless debugging bottom (keeps pairing session visible)   
   15. Tap "Start via Wireless debugging"   
   16. Tap "Pair device with pairing code"   
   17. Enter pairing code   
   18. Accept system pairing prompt   
   19. Shizuku finally says "Shizuku is running"   
   20. (Optional) Run start.sh manually for apps that need it   
      
   ===========================================================   
   SUMMARY:   
     THEORY: 8 steps   
     REALITY: ~20 steps   
     ROOT CAUSE: Samsung aggressively suppresses system dialogs,   
     rotates ports unpredictably, and hides ADB prompts unless   
     the app is visible in split-screen *and* notifications are on.   
   ===========================================================   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)