Host Wi-Fi join and management in Flutter and Rust connection setup #31

Activity

1. atomicdeploy commented on Oct 27, 2026

   

   atomicdeploy

   on Oct 27, 2026

   OwnerAuthor

   More actions

   Implemented a bounded source checkpoint on the existing PR #27 branch: Android OS-consented app-only Wi-Fi join (45s acquisition, permission/cancel/loss/close cleanup), Android saved-network/settings flows, non-secret per-entry SSID hints, and Windows adapter-specific saved profile enumeration/join with explicit switch confirmation and system settings for new networks. Uses shared UI controls; normal board identity/authentication stays unchanged. Flutter analysis + 4 focused tests pass; Windows compile check passes. APK/native focused test still building. No live network switches or board operations were performed; installed OS consent/AP/routing remains a separate acceptance gate.
2. atomicdeploy commented on Oct 27, 2026

   

   atomicdeploy

   on Oct 27, 2026

   Last edited by atomicdeploy

   OwnerAuthor

   More actions

   Published checkpoint e924adc in PR #27.

   • Android explicit consent-based local Wi-Fi join, cancellation, timeout, binding cleanup, saved-network flow and OS settings.
   • Windows Native Wi-Fi adapter/profile enumeration and confirmed join, plus OS settings for new networks.
   • Contextual connection UI, SSID hints, separate credentials and normal board verification retained.
   • Flutter analysis and 5 focused tests passed; Rust Check, 1 focused test, and Release passed.
   • APK and Windows candidates built; hashes and exact UI entry points in docs/HOST-WIFI.md.
   • Donor/hash comparison check passed; clean source checkpoint pushed.
   • Install candidates and exercise actual Android consent/denial/routing plus Windows join/board handshake. No production network or board was changed.

   The guarded cleanup removed only verified unused 2.782 GiB desktop/target/debug artifacts, preserving release cache/settings/rollback/running apps. No CI or installed-device acceptance is claimed.
3. atomicdeploy commented on Oct 27, 2026

   

   atomicdeploy

   on Oct 27, 2026

   OwnerAuthor

   More actions

   Requested tablet deployment completed on restored ASUS connection: SM-X906B now runs the current 0.2.8/build23 APK (SHA256 72cd52693b7d794cf35091162a75ab9aa196a7bb75d1376d7b30529f1c8d13d4). Built through build-mobile.ps1 -Mode ApkPreview -BuildOnly -BoardProductionHold; staged hash and installed base.apk hash both match. adb install -r succeeded without clearing data; app foreground and screenshot inspected: Connected to ledcontroller.local, all80 table cells rendered,11 retained selections. No fatal app exception in bounded current-process logs; vendor graphics warnings remain. No phone or production-board changes. Interactive OS Wi-Fi consent/loss behavior remains unverified; this is deployment/startup evidence, not complete feature acceptance. Source is pushed on PR27; current-head CI/review still gates merge.