A straight line across your Strava ride often means the recording has a gap between usable location points. Start by identifying which device recorded the activity, then inspect its location access, background restrictions, and original recording. Do not assume a Strava server problem or buy a new watch before checking where the route first went wrong.
If the missing section was never recorded, changing the distance afterward will not reconstruct the exact road you rode. The most useful fix may be preventing the next gap while preserving what remains of this activity.
Find the device that produced the route
Was the ride recorded directly in the Strava phone app, on a watch, on a bike computer, or in another app that later synchronized it? That answer determines which settings matter.
If you used a watch, open the activity in the watch manufacturer's app. If the straight line is already there, investigate the watch's recording and positioning. If the original route is complete but Strava differs, focus on the transfer or import process and preserve the original file.
If you recorded on the phone, review what happened near the gap: did you lock the screen, switch apps, enter a tunnel, enable a battery mode, or lose recording entirely? Timing clues are useful, although one coincidence does not prove the cause.
Understand what the line is showing
Strava explains that when GPS signal is lost and later reacquired, the points before and after the gap can be joined by a straight line. GPS drift and bouncing points can create different-looking errors. A tidy diagonal across several streets can therefore represent missing information rather than a shortcut.
Compare the activity's elapsed time, recorded route, and any pause behavior. A map that looks wrong may also affect distance or pace, but the numbers alone cannot tell you which setting caused the problem.
| What you observe | What to inspect first | Useful evidence |
|---|---|---|
| Gap begins after screen locks | Background operation and battery restrictions on the recording app | Approximate lock time and where the gap begins |
| Gap occurs under heavy obstruction | GPS reception and device placement | Terrain, tunnel, buildings, and original track |
| Watch app also shows the gap | Watch recording settings and device support | Original activity in the manufacturer's app |
| Original route is complete | Transfer or synchronization stage | Source file and both versions of the activity |
Check phone permissions without changing everything
For a phone recording, confirm that location services are enabled and Strava has the location access it requests for recording. Review precise-location options where your operating system provides them. Menu labels vary by phone and software version, so use the current Strava instructions for your platform.
On Android, inspect battery optimization and background restrictions that apply specifically to Strava. Strava's support guidance notes that power-saving or task-management tools can interrupt GPS recording. Make a targeted change to the recording app instead of disabling every privacy or battery safeguard on the phone.
On iPhone, Strava recommends basic checks such as restarting, reviewing location services, and allowing an unobstructed view of the sky before recording. Begin outside, give positioning time to settle, and avoid judging reception only while standing inside a building.
If a phone-wide low-power mode was active, test its effect on a short outing before relying on it for a long ride. Keep track of what you changed so you can restore settings that do not help.
Run one short, controlled test
-
Charge the recording device and note its app and operating-system versions.
-
Choose a short, familiar route with a clear view of the sky.
-
Wait for a plausible location before starting the activity.
-
Record a few minutes with the screen active, then a few with it locked.
-
Finish and inspect the original recording before evaluating any synchronized copy.
-
Change one relevant setting if needed and repeat the same simple test.
Keep the test separate from a ride you care about. The goal is to discover a reproducible pattern, not to sacrifice another long activity while adjusting five settings at once.
A road-navigation app appearing accurate does not necessarily establish that your raw GPS recording is healthy. Strava notes that navigation apps may snap positions to known roads. Compare another activity-recording app if support asks you to test positioning elsewhere.
Preserve the original before trying repairs
Save an available original activity file or retain the source activity in the recording app. Take screenshots showing the gap and its approximate time. If you contact support, include the recording device, phone model where relevant, and whether the source and imported versions differ.
Distance correction and other editing options are not the same as recovering missing GPS samples. Avoid presenting an estimated reconstruction as a precise record. If you make a manual adjustment for your training log, label the estimate for your own future reference.
Repeatedly deleting and reimporting an activity can also complicate troubleshooting or create duplicates. Identify the failure stage first and follow the support instructions for that device or integration.
Buy equipment only for a demonstrated need
A dedicated watch or bike computer may offer features you value, including a different battery profile or mounting arrangement. It still needs suitable settings and reception. One damaged activity does not establish that your phone is incapable of recording rides.
If short tests repeatedly fail across recording apps despite correct permissions, gather the evidence and seek device support. If only one integration fails, investigate that integration. Spend money after you understand the problem you expect new hardware to solve.
Frequently asked questions
Can Strava fill in the exact missing route?
Its GPS troubleshooting guidance says missing recorded data cannot simply be filled in. Preserve the original and distinguish any estimate from actual tracking.
Should I disable all battery-saving settings?
No. Start with restrictions affecting the recording app and test targeted changes on a short route.
Does a straight line prove Strava lost my upload?
No. Compare the source recording with the uploaded activity. The gap may have originated before synchronization.
