Strava

How Strava Improves Auto Pause for Everyone

Original post Improving Auto Pause for Everyone

Article Summary

Strava's engineering team faced a deceptively hard problem: how do you automatically detect when a runner stops moving without draining their battery or showing the wrong pace?

The Strava team rebuilt their auto-pause feature from scratch to work across all devices, not just the iPhone 5s. They had to solve fundamentally different problems for cyclists (who want reliability) versus runners (who need sub-second accuracy).

Key Takeaways

Critical Insight

By combining accelerometer motion detection with GPS fallbacks, Strava achieved sub-second pause/resume accuracy while maintaining the same stats from recording to upload.

Continue reading

What This Article Covers

Problem

Strava's server removes stopped time after you upload an activity, but the auto-pause feature on your phone only kicks in after 10 seconds of no movement. This creates a gap: if you stop for 25 seconds, only 15 seconds get removed from your recorded time.

Solution

Strava Engineering added a backup resume function that uses GPS data. It helps when runners hold their phones still while looking at the screen, which can accidentally trigger false pauses. The fix smooths out the accelerometer motion signal to prevent this.

Impact

When you record with auto-pause on, the server skips its normal cleanup process. Your stats in the app at the end of your activity, like total time, splits, and pace, now match what you see on Strava after uploading.

The team discovered that holding your phone too steady while running can accidentally trigger a pause, leading to an unexpected GPS-based backup system.

This page summarizes “Improving Auto Pause for Everyone” by Strava, published Nov 15, 2022. All credit for the original work goes to the authors.

Read the original on medium.com (opens in new tab)

AI tools for iOS

Browse all AI tools →