[FEATURE] Persist wireless ADB after app restart and device reboot (cold start)

[codewithtamim]

Summary

Wireless ADB should remain usable after the user force-stops the app, clears it from recents, or the process is killed and restarted—and after a full device reboot when wireless debugging is enabled and pairing is still valid. Today the connection or authorization state may not be re-established automatically on cold start or boot, so users may need to re-open settings or re-pair more often than necessary.

Scope (suggested)

• Connection lifecycle: Ensure pairing material and any session state needed for a working autoConnect path are restored or re-established when the app process starts again, within Android wireless-debugging constraints (including behavior differences after reboot, e.g. port or address changes).
• Startup / boot: Consider reconnect or connection checks from app entry (Application, first activity, or installer flow) aligned with WirelessAdbInstaller / AdbConnectionManager without blocking UI longer than necessary; account for first launch after reboot.
• UX: When the OS still requires a new authorization or pairing step, keep the existing setup / pairing flows; this issue is about not losing a still-valid wireless session unnecessarily.

Acceptance criteria

• Cold start after swipe-away or force-stop: the install path still works when wireless debugging is enabled and the device was previously paired (document OEM / Android version limits where behavior differs).
• After device reboot, with wireless debugging turned back on (per user/OS): the install path works without a full re-pair when keys and platform state allow it; document cases where Android assigns a new pairing port or requires re-authorization.
• Clear behavior when re-authorization is required (reuse existing pairing and setup routes; no silent failure).

Notes

• AdbConnectionManager and DataStore-backed keys already persist RSA material across restarts; this work focuses on connection/session behavior after process death and post-reboot recovery, not duplicating key storage.
• Reboot may change wireless debugging endpoints (e.g. port); discovery or settings deep-links may still be needed—call out in docs or in-app copy if unavoidable.
• Coordinate with any follow-ups on ADB install UX (e.g. warnings when ADB is not ready).