Fatigue & Breaks: Frequently Asked Questions
I stopped, but the app didn't record it/trip stiched together.
Why didn’t the app record my break?
The analysis typically fails to register a break if your device loses its connection to GPS nodes for a period of time.
During a signal drop, the app waits for the connection to return so it can compare your new location to where you were when the signal was lost:
- If it receives your location and reads the device as still, the trip ends and your break is recorded.
- If it receives your location and shows you have moved, the system interprets this as a temporary mid-trip signal drop and "stitches" the pre- and post-drop driving data into one continuous trip.
What is the best practice for making sure my breaks are tracked?
To minimize signal drops and ensure your rest periods are logged accurately, follow these best practices:
- Take your device with you when leaving your vehicle: This signals your device's GPS that you have stopped traveling in a vehicle.
- Avoid stopping in built-up areas that block signals: Where possible, avoid parking in underground garages or dense built-up areas that reduce or eliminate GPS signals. Taking your device out of the vehicle is especially important if you must stop in these zones.
- Ensure you are taking at least 5 minutes break: This is to make sure youve stretched and given your brain time to reset and prepare for concentrating again on the road.
Why does the app "stitch" trips together instead of starting a new one?
Without these programmed behaviors, every time you stop in heavy traffic or at a red light for a few moments, your trip would officially end and a brand-new one would begin. This would clutter your trip timeline and severely disrupt your recording accuracy.