# #32 — position-driven native navigation and speech

Android build 0.11.0-navigation; physical TECNO KF8; checked 2026-09-19.

The selected road route, or an individual charging-plan leg, starts an independent Android location foreground service. Location matching advances along the returned geometry and selects upcoming maneuver instructions. The UI shows progress, current instruction/distance, location certainty, voice availability and explicit off-route status. A restored route is drawn from its private checkpoint. No PC process supplies navigation, speech or location processing.

The service requests location at 2 seconds / 5 m and never holds the display awake. GPS quality, monotonic ordering, resume boundaries and freshness gate progress. A 30-second deadline marks location uncertain and suppresses guidance; a speech claim additionally requires a fix within 5 seconds. Poor/no GPS stops current speech. Off-route is explicit and never presented as a newly calculated route. Normal matching bounds progress; GPS gaps, restarts and failed local matching use two consistent global matches before reacquiring progress. Ambiguous earlier/later crossing branches remain uncertain.

English provider instructions use an installed local English TTS voice. Audio focus is requested per prompt, transient focus loss stops speech, and enqueue success is not labelled completion: the engine callback persists completed/interrupted/unavailable outcome. Session/maneuver/threshold speech claims are committed before enqueue and survive restart. An interrupted threshold is not automatically repeated; a later relevant threshold remains eligible. Mute is persisted, carried to a new session and synchronized to the checkbox. Missing TTS leaves visual navigation available with an unavailable voice state.

The route is stored once; frequent SQLite progress updates contain only the small session checkpoint. A killed process restores interrupted and requires explicit visible-app resume. End removes navigation's listener, deadline, notification and TTS/audio focus. Independently active trip recording is not ended by that action. Permission denial leaves planning available; settings and resume controls remain visible. Notification denial is not treated as a location-service permission.

Automated verification:

- Eight navigation application-boundary tests cover progress, prompt deduplication, stop/late fixes, poor/stale/off-route fixes, stable recovery, retained speech claims after restart, ambiguous crossings, failed claim persistence, recovery beyond 500 m after both long and shorter plausible gaps, and mute across sessions/restart.
- Seven existing recording/routing JVM tests also pass. Android debug build/lint and 44 Node tests pass.
- Standards/spec review findings about bounded-window recovery and mute mismatch were corrected, regression-tested and re-reviewed with no remaining findings.

Baseline physical-device replay verifies start from the route UI, permission denial, local voice readiness, TTS completion with the screen off, one advance and one near-turn announcement without repeated claims at the same position, lost-location status, activity reopen without a new session, force-stop/interrupted recovery, and end stopping progress/speech. Android mock-provider replay is synthetic and is not road-accuracy or audible-speaker measurement evidence; TTS completion is acknowledged by the native engine.

Advanced physical-device replay also verifies native audio-focus interruption marks the spoken claim interrupted without repeating it, explicit off-route status and two-fix recovery, mute across end/start with the checkbox matching native state, an independent recorder remaining active after guidance ends, visual progress with the TTS package temporarily disabled, and uncertainty when system location is disabled. Temporary engine/provider/app-op/permission/database changes are restored after testing.

Ignored device evidence: `research/runtime/issue32-device.json` and `research/runtime/issue32-device-advanced.json`. Debug replay/focus helpers require shell/DUMP permission and an explicitly synthetic session and are excluded from release builds. Android 13 notification denial and Android 14–15 launch enforcement cannot be exercised on the Android 11 TECNO; manifest/SDK guards and lint are checked. Full offline navigation and automatic replanning are not claimed here.

Platform basis: [Android foreground-service launch](https://developer.android.com/develop/background-work/services/fgs/launch), [TTS callback contract](https://developer.android.com/reference/android/speech/tts/TextToSpeech), [audio focus](https://developer.android.com/media/optimize/audio-focus), and the [research decision](/omox/android-navigation-decision/).
