Fix: background GPS points lost on OS service restart
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.
This commit is contained in:
parent
97539c9110
commit
d4ef9a1f9f
3 changed files with 18 additions and 9 deletions
|
|
@ -49,7 +49,7 @@
|
|||
| Файл | Строк | Назначение |
|
||||
|------|-------|------------|
|
||||
| `MainActivity.kt` | ~300 | FileObserver IPC, seed DB, safe insets, SAF, BLE commands, OTA check |
|
||||
| `GpsRecorderService.kt` | ~500 | Foreground service GPS, WakeLock, JSONL, 50Hz акселерометр/гироскоп, dead reckoning, raw sensor files |
|
||||
| `GpsRecorderService.kt` | ~500 | Foreground service GPS, WakeLock, JSONL (один файл на сессию до Стоп, идемпотентный onStartCommand при START_STICKY-перезапуске ОС), 50Hz акселерометр/гироскоп, dead reckoning, raw sensor files |
|
||||
| `BleHrService.kt` | ~340 | Foreground service BLE HR, FitPro protocol, GATT queue, scan/connect |
|
||||
| `generated/*.kt` | ~1100 | Tauri-сгенерированные: WebView, IPC, permissions |
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue