ADFA-5197 docs(connectivity): device-to-device options, mechanisms and decision - #438
Merged
Merged
Conversation
…-Fi Direct alternative
…d decision Adds an engineering note that answers ADFA-5197 (preserve hotspot name/password across restarts) and maps the device-to-device connectivity options for K2Go. Finding: a fixed SSID/passphrase on a user-owned Android phone is not achievable with public APIs — the platform reserves AP naming for system components (LOHS/SoftAP/Wi-Fi Direct hand the app system-generated credentials it can read but not pin). The stable, printable experience the ticket wants is delivered by moving the AP off the phone (external router, fixed creds) and reaching the host by name via NSD/mDNS — a standard, unprivileged API — so a DHCP address that changes doesn't matter. LOHS + on-screen QR stays as the hardware-less fallback. Covers, grounded in the codebase: options A–E with the API mechanism folded in (LOHS, Wi-Fi Direct, Device Owner, Wi-Fi Aware, external AP); the `:8085` reachability cross-cut (bind is nginx-in-proot, not Android; interface discovery already done in `NetworkInterfaces`); an addressing-by-mode table; permissions; and a verified vs. to-verify checklist. Docs only — no code change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an engineering note that answers ADFA-5197 (preserve hotspot name/password across
restarts) and maps the device-to-device connectivity options for K2Go.
Finding: a fixed SSID/passphrase on a user-owned Android phone is not achievable with public
APIs — the platform reserves AP naming for system components (LOHS/SoftAP/Wi-Fi Direct hand the
app system-generated credentials it can read but not pin). The stable, printable experience the
ticket wants is delivered by moving the AP off the phone (external router, fixed creds) and
reaching the host by name via NSD/mDNS — a standard, unprivileged API — so a DHCP address that
changes doesn't matter. LOHS + on-screen QR stays as the hardware-less fallback.
Covers, grounded in the codebase: options A–E with the API mechanism folded in (LOHS, Wi-Fi
Direct, Device Owner, Wi-Fi Aware, external AP); the
:8085reachability cross-cut (bind isnginx-in-proot, not Android; interface discovery already done in
NetworkInterfaces); anaddressing-by-mode table; permissions; and a verified vs. to-verify checklist.
Docs only — no code change.