4aiman
cd975b5640
On stretches where the fix rate drops (dt > gapThresholdSec, incl. dead- reckoning) the straight chord mis-measures the path, so computeStats now estimates gap distance by avg(speed)*dt (capped at max speed; a tiny chord over a long gap means the rider was stopped and the reported speed is stale -> trust the position). A fast jump WITHOUT a time gap is a teleport glitch and is dropped. Distance now depends only on ts + speed, not on the `estimated` flag (which live points carry but DB rows don't), so the live counter, Stop and recompute finally agree. Verified on a real ride: at gapThreshold=30 -> 35.7 km / 1024 kcal (map-measured ~35 km); clean tracks without gaps unchanged. Settings: read GPS config on input+change (reliable on mobile), add a "Save GPS settings" button and a "saved" toast so it's clear the value persisted; changing gapThreshold + recompute now visibly applies. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| gen/android/app/src/main | ||
| icons | ||
| src | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| tauri.conf.json | ||