Time gets added to my walking activity during upload.

For the last three days I've been walking just over four miles. Each mile is taking me about 14.5 mins and I get home just over an hour after I set off. The Stava app agrees with me when I stop it but once the activity is uploaded it adds approx 32 mins to my activity and reduces my pace to over 20 mins/mile!

This happens via mobile data and when using wifi and I've also checked my start/finish times on an analog clock. Yesterday I set off at 9am, got home just after 10am and was showered and eating breakfast but according to the Strava app I shuld still have been walking.

it's not good. I thought that maybe Strava think I walk too fast but looking at my previous walk over the same routes and distance they are pretty much accurate. Any ideas why this is happening?

7

Kommentare

  • I have been having seemingly the same problem since at least mid-December 2019. I have at least four activities (I run daily) where the sum of the start time and the elapsed time is documentedly several minutes after the upload time. When I download and analyze the resulting GPX, all timestamps after the initial one seem fake; it appears as if the time axis had been artificially stretched to match the fake overall time. The position data is excellent. I believe this bug was introduced fairly recently, I would have noticed otherwise. Galaxy S8 active. I tried what Strava's support suggested, turning the phone's Location off/on before a run; in the last documented case the bug was nevertheless triggered. The fake GPX seems especially insiduous and this shouldn't happen! an app deliberately fudging data we're trusting it to preserve for posterity destroys all faith one may have.

    5
    Aktionen für Kommentare Permalink
  • Seeing the same issue.  Clueless why it would do this on the raw data.

    3
    Aktionen für Kommentare Permalink
  • Also seeing this issue, and also dating from mid December.  Elapsed & Moving time recording was working perfectly for me before.  I believe the issue corresponded with a Strava app upgrade.

    I would also point out that (elapsed) time recording is fine *during* the recording of the activity.  When I stop running the time showing in the app is correct, it is only once I have hit the Finish button, and the activity has uploaded to the Strava site that the corruption of times occurs.

     

    4
    Aktionen für Kommentare Permalink
  • I have the same problem. I record my walks and the app has been adding extra time to activities, even though I've saved & sync straight away (data & WiFi). My app has updated twice since the problem started (Dec) and it still hasn't been fixed.

    I have looked through the Strava support pages and there doesn't seem to be a way to fix it. I can only assume that it's a problem with the app and not our phones..

    3
    Aktionen für Kommentare Permalink
  • ok guys. Iam not alone. Supports no answer... Android. Sony XZ1 Xperia. From 23 December 2019 I have the same trouble: more time to workout after posting, but have a normal time and avg speed before stop. I did several test and see that app add from 10 to 15 minutes to workout with 1-2 hrs long so you have less avg speed and more CLEAN time and much more ALL time... wait for fix...

    2
    Aktionen für Kommentare Permalink
  • I have same issue since late December 2019. I am using the Strava app on a Huawei android phone (p20 lite). As with other users, once uploaded my rides indicate me arriving home long after I've already done so. Many of my segment times are recorded as much longer than others who I am cycling with. When  I “View flybys” through a browser I fall behind others that I have actually cycled next to or even ahead of so much so that over a 2 hour ride I end up about 30 minutes behind them on the animation. I guess this has been caused through a Strava update. Unless solvable I will have to give up using the app which I have very much enjoyed using, with very few problems over the last the last five years.

    1
    Aktionen für Kommentare Permalink
  • I have the same problem. I'm using the Pixel 4xl and get around 10-15% added to my elapsed time. I've been seeing this problem for the last month or so.

    2
    Aktionen für Kommentare Permalink
  • Yeah had exactly  the same thing on a Samsung Galaxy S7. Was working perfectly and then since Xmas it has added 10 minutes to the end of a walk when saved to the cloud. The display shows the right time up until then. Also the pace calculations for a run are completely off, where it gives me a 5:15 average split but then says the fastest split was 6 mins for a 5km run, which obviously doesn't make sense at all as some should be under and some over 5:15. The audio cues during the run gave the rights times. It was working fine up until early December so I assume they've broken something somewhere.

    Have found a workaround, which is to save original from the activity on Strava website. Then upload the .fit file generated into FitTools.com. Use the crop tool to load the file, make no changes, just press OK and then save generated file to disk. Then delete the original activity from Strava (so it doesn't see it as a duplicate) and upload the new .fit file generated by FitTools. Mark the activity as a run/walk whatever and it all seems to work, segments still are OK, the time issue is fixed and the pace is correct. So I guess Strava have an issue with their own .fit file that they upload from your device!!!

    0
    Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post