Two field reports from tonight's 5G session: - 'Stuck connecting': the kiosk WebView always loaded the LAN URL first, and Chromium burns a minute+ of connect retries on a dead LAN IP before the mesh fallback fires. WebViewScreen now races a raw TCP probe — LAN gets 2.5s, else the mesh ULA (patient, 12s) — BEFORE creating the WebView, so startup lands on the right origin in seconds either side. Retry re-races instead of blindly reloading the LAN URL. - Pine/Home Assistant/BTCPay opened in the external browser over the mesh: same-node detection compared one host, but the node has two (LAN origin + mesh ULA) — kiosk loaded via the ULA meant app links failed isSameHost and routeOutbound bounced them to the browser. Same-node now matches either address, in the kiosk router, SSL allowances and the InAppBrowser. Served APK: 0.5.6 (vc26). Note: the binary also carries the in-flight listen_port groundwork from the dev-box session's archy-fips-core WIP (compiles clean, default posture unchanged); its source lands separately. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
26 MiB
26 MiB
The file is too large to be shown.
View Raw