quoije/yaris-obd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: phone-hotspot requires LTE-only phone (no simultaneous AP client)

Browse Source 
- FEAT-07: documented the WiFi-sharing/routing loop that breaks the Pi's
  uplink when the phone hosts the hotspot and is also on the Pi's AP
This commit is contained in:
Mathieu Moran
2026-08-12 22:32:07 -04:00
parent 26597888ba
commit 51417abf75
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
FEATURES.md
+6
View File
@@ -132,6 +132,12 @@ dedicated PLAN.md phase (or fold it into the relevant existing work) and mark it
appearing in range, and falls back to home-wifi when it disappears. The wlan0 AP appearing in range, and falls back to home-wifi when it disappears. The wlan0 AP
stays up regardless. Test flow: Settings → save hotspot name + password → "Wait for stays up regardless. Test flow: Settings → save hotspot name + password → "Wait for
hotspot" → enable phone hotspot → verify mode changes to "Phone hotspot". hotspot" → enable phone hotspot → verify mode changes to "Phone hotspot".
- **Known limitation (2026-08-12)**: the phone can't host the hotspot *and* connect to
the Pi's AP at the same time — that creates a WiFi-sharing/routing loop and the Pi
loses internet (`NameResolutionError` on uploads). To use the phone hotspot as the
Pi's uplink, the phone must be LTE-only (WiFi off). Browse the Pi UI from a second
device on the AP instead. Also, the phone's DHCP DNS was flaky for the `.dev` tunnel,
so `phone-hotspot` now forces `8.8.8.8` + `1.1.1.1` (see `deploy/yaris_uplink.py`).
### FEAT-08 — Predictable IP on phone hotspot (DHCP client-id) ### FEAT-08 — Predictable IP on phone hotspot (DHCP client-id)
- **Status**: `SHIPPED` 2026-08-11 (Phase 22) - **Status**: `SHIPPED` 2026-08-11 (Phase 22)