Regression from per-session points file change (1feb2ef): the service returns START_STICKY, so when the OS kills it during screen-off, it restarts with a null intent and onStartCommand minted a NEW points file, repointing gps_live_points.jsonl and orphaning accumulated background points. Evidence: many tiny orphaned gps_points_*.jsonl fragments. Fix: onStartCommand creates a new session file only on a genuine start from JS (intent with extras). A START_STICKY restart (null intent) keeps writing to the existing session file from the pointer — one file per session until Stop. Verified on device: am kill (= START_STICKY restart) no longer creates a new file, pointer unchanged, trail resumes on return. Background writing confirmed: 49 points in 70s with screen off (Dozing) at 1Hz. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| gen/android/app/src/main | ||
| icons | ||
| src | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| tauri.conf.json | ||