Jamming leaves gaps in your fleet's position history.
Replay documented Baltic and Gulf jamming events against your navigation stack. Find ETA calculation and route reconstruction failures in CI before customers do.
What breaks when GPS is jammed
Jamming doesn't just mean "no GPS". It creates position gaps, stale coordinates, and recovery sequences your navigation logic may never have handled.
š”
Position gaps break ETA
Intermittent jamming causes the position stream to go silent for 30ā90 seconds at a time. ETA algorithms extrapolate stale data, drift, and report wildly wrong arrival times ā creating customer complaints with no app bug to blame.
šŗ
Route reconstruction fails
A GPS blackout through a tunnel or under a bridge leaves a hole in the route log. Map-matching algorithms snap to the wrong road on recovery, corrupting the recorded route and misattributing mileage.
š
Cold-start reacquisition lag
After a full blackout, GPS cold-starts take 20ā60 seconds. During that window your app shows stale position, may re-route incorrectly, or silently stops updating ā none of which are tested until a real outage.
Recommended scenarios for fleet apps
These scenarios cover the GPS failure modes most common in fleet operations ā all based on documented jamming incidents affecting shipping and commercial transport.
gnss/baltic-jamming-2024
Baltic Jamming 2024
Intermittent jamming near the Finnish coast ā repeated signal loss and recovery cycles over 90 seconds. Tests how your app handles a position stream that flickers out repeatedly without ever fully stabilising.
Relevant for: ETA calculation, route logging, position interpolation
gnss/tunnel-transit
Tunnel Transit
Complete GPS blackout through a 3-minute tunnel followed by a realistic cold-start reacquisition sequence. Tests map-matching on recovery, dead-reckoning fallbacks, and ETA continuity through the gap.
Relevant for: map-matching, dead reckoning, route reconstruction
gnss/baltic-drift-2024
Baltic Drift 2024
Gradual position drift observed in Baltic shipping lanes ā slow spoof ramp over 5 minutes, 2ā8 km of accumulated error. Tests whether your tracking logic detects drift or silently follows a position that's increasingly wrong.
Relevant for: drift detection, anomaly alerting, geofence accuracy
multi/tunnel-with-imu Team
Tunnel with IMU
GPS blackout combined with simultaneous IMU noise injection. Tests dead-reckoning quality under the realistic condition where both the primary and fallback sensor are degraded.
multi/everything-fails Team
Everything Fails
GPS, accelerometer, barometer, and magnetometer all degrade simultaneously. The ultimate stress test for sensor fusion stacks that manage commercial vehicle fleets across long routes.
Track navigation resilience in CI
Run the fleet scenario suite on every release branch. Save a baseline after passing, and catch regressions automatically with a JUnit report that integrates into any CI dashboard.
Run the fleet scenario suite
sensorchaos suite \
--scenarios gnss/baltic-jamming-2024,\
gnss/tunnel-transit,\
gnss/baltic-drift-2024 \
--device emulator-5554 \
--save-baseline fleet-baseline.jsonCatch regressions on every PR
sensorchaos suite \
--scenarios gnss/baltic-jamming-2024,\
gnss/tunnel-transit,\
gnss/baltic-drift-2024 \
--compare-baseline fleet-baseline.json \
--regression-threshold 0.05 \
--junit-report results.xml \
--exit-code-on-fail--regression-threshold 0.05 flag fails the build only if a sub-score drops by more than 5% ā preventing noise-driven failures while catching real regressions. See the CI docs for full pipeline templates.
Stop finding navigation bugs from customer reports.
Start a 14-day free trial. No credit card required. Works with any Android emulator in under 5 minutes.