Android client
The Android application embeds KnotRoute through a gomobile AAR and does not require a separately installed daemon.
Recommended onboarding
Section titled “Recommended onboarding”- Obtain a QR/deep-link from KnotRoute Control.
- Open the
knotroute://join?...URI. - Review the Network ID and Beacon list.
- Save the network profile.
- Connect.
- Install the local CA through Android’s system UI if
.knotHTTPS is required.
Network profiles
Section titled “Network profiles”Multiple profiles allow separate Production, Test, Home or Lab overlays on the same device.
Browser
Section titled “Browser”The embedded browser sends .knot traffic through the local KnotRoute proxy. The application does not require VpnService or occupy the system VPN slot.
Local CA
Section titled “Local CA”Android requires user interaction to add a user CA. TLS errors are treated as failures rather than bypassed.
Troubleshooting
Section titled “Troubleshooting”Check Network ID, Beacon reachability, Internet connectivity, foreground service status, system time and application diagnostics.
Runtime lifecycle
Section titled “Runtime lifecycle”The foreground service owns the embedded core. After profile changes it performs an ordered stop/start and the Activity reapplies WebView proxy override only after the new core generation is ready. The UI also applies system-bar/display-cutout insets for API 36 edge-to-edge layouts. Circuit hops remain under Advanced settings; ordinary onboarding only needs profile name, Network ID and Beacon HTTP(S) URLs.