docs: BUG-01 closed — tested on iOS + Android, yaris.local resolves, Phase 26 DONE
This commit is contained in:
@@ -9,13 +9,13 @@ When CLOSED, move the entire entry to Resolved — don't duplicate.
|
||||
## Open bugs
|
||||
|
||||
### BUG-01 — WiFi/hotspot unreachable from phone while cell data is on
|
||||
- **Status**: `IN PROGRESS` (dual-radio deployed, awaiting owner test)
|
||||
- **Fix applied**: Dual-radio setup — wlan0 is permanent AP, wlan1 handles internet
|
||||
uplink. `yaris_uplink.py` never touches wlan0. Settings page has "In-car access"
|
||||
card showing hotspot URL with copy button and cell-data warning.
|
||||
- **Needs verification**: Connect phone to Pi hotspot "yaris 911" at 10.42.0.1;
|
||||
confirm it stays up >3 min while cell data is on. Try with phone hotspot
|
||||
enable/disable to verify AP survives uplink changes.
|
||||
- **Status**: `CLOSED` 2026-08-11
|
||||
- **Fix**: Dual-radio setup — wlan0 is permanent AP at 10.42.0.1 (SSID "yaris 911",
|
||||
password "yaris911!"), wlan1 handles internet uplink only. `yaris_uplink.py` never
|
||||
touches wlan0. Settings page has "In-car access" card showing hotspot URL with copy
|
||||
button and cell-data warning.
|
||||
- **Verification**: Tested on both iOS and Android 2026-08-11. Both connect to AP,
|
||||
`yaris.local` resolves and loads the dashboard. AP stays up with cell data active.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -1860,8 +1860,10 @@ phase roadmap.
|
||||
|
||||
---
|
||||
|
||||
### Phase 26: Road-test bug fixes — 🚧 IN PROGRESS (10 closed, 1 awaiting test, 1 hardware)
|
||||
**Last updated 2026-08-11.**
|
||||
### Phase 26: Road-test bug fixes — ✅ DONE (11 closed, 1 hardware)
|
||||
**Completed 2026-08-11.** All software bugs from the Phase 25 road test are fixed,
|
||||
deployed, and verified. Only BUG-02 (Pi micro-USB hardware) remains — owner's
|
||||
responsibility.
|
||||
|
||||
**Closed (verified in prod):**
|
||||
- BUG-03: DTC/MIL persistence (`e2f2314`)
|
||||
@@ -1891,14 +1893,15 @@ rather than incremental patching:
|
||||
- **Same JS file works on both Pi and server**: tile URL/attrib/zoom defaults read from
|
||||
`data-*` attributes on `#history-map`, with Pi-local fallbacks when absent.
|
||||
|
||||
**Deployed, awaiting owner test:**
|
||||
- BUG-01: Dual-radio — wlan0="yaris 911" at 10.42.0.1, wlan1=internet uplink.
|
||||
Bench-verified AP stays up. Needs real phone connection test.
|
||||
|
||||
**Still open:** None.
|
||||
BUG-02 is hardware (Pi micro-USB port damage) — owner's responsibility.
|
||||
- BUG-06: `_to_tz_aware()` in `app_upload.py` converts naive SQLite timestamps to TZ-aware before upload. One-time SQL migration on Unraid corrected all existing tracking_points (+4h EDT) and recomputed 43 trips. Server trip times now match real-world clock.
|
||||
- BUG-07 history.js rewrite (see above) — rapid trip-switching no longer freezes, loading spinner + active row highlight provide clear feedback. Verified on Pi and server.
|
||||
**Deployed and verified:**
|
||||
- BUG-01: Dual-radio — wlan0="yaris 911" at 10.42.0.1 (password "yaris911!"),
|
||||
wlan1=uplink. Tested on iOS + Android, `yaris.local` resolves, AP stays up
|
||||
with cell data active.
|
||||
- BUG-06: `_to_tz_aware()` in `app_upload.py` converts naive SQLite timestamps
|
||||
to TZ-aware before upload. One-time SQL migration on Unraid corrected all
|
||||
existing tracking_points (+4h EDT) and recomputed 43 trips.
|
||||
- BUG-07: history.js rewrite — rapid trip-switching no longer freezes, loading
|
||||
spinner + active row highlight. Verified on Pi and server.
|
||||
|
||||
**Still open:** None.
|
||||
BUG-02 is hardware (Pi micro-USB port damage) — owner's responsibility.
|
||||
|
||||
Reference in New Issue
Block a user