Excessive elapsed time and very low pace on strava rides

Hi, Since the last two mtb rides I did with friends strava has serious issues with showing the correct time and pace, like saying I rode 6,5 hours with 7 km/h pace while of course that should be 2,5 hours with 19 km/h pace. In the feed it shows also that I did not ride with my friends. Any ideas on how to solve this issue? I really don't know what I could have changed in my phone or app settings that could have caused this problem. My phone is a huawei p8 lite with android of course.
7

Kommentare

11 Kommentare
  • I'm getting something similar, but not the same.

    The overall elapsed time is correct, as is the average speed.

    But if you look at the analysis and then switch the x-axis to time, that time now extends much further than it should (beyond the elapsed time for the whole ride). Zooming in on it, there are many times when it shows me stationary. This results in all of the segment times and average speeds being wrong.

    It used to work OK, like you I am not sure what changed to make it start doing this.

    This is on a Samsung A5.

     

    1
    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...

    I try all ways to fix from changing in app to delete and dwnloading again. ITs a problem with app and maybe with some versions Androids

    wait for fix... pls write to SUP guys its not good ...

    1
    Aktionen für Kommentare Permalink
  • Identical problem here to Rutger and Vladimir (the other Vladimir) but maybe not to Mark. Earliest documented instance is 14 December 2019 (daily+ runs). Support has been quite responsive but they seem to be misdiagnosing the problem and telling me it is with the AGPS on the Android. I started religiously clearing the AGPS minutes before the run (if it is indeed the AGPS, can't the app force-clear the AGPS if it needs to?) The incidence of the bug (unscientifically) went down but not to zero. Galaxy s8 active (that didn't have this problem for almost a year)

    When you look at the GPX of a problem activity, only the start time is correct and all following trackpoints have their timestamps distorted, perhaps proportionally. This is on its face awful: stored data is bogus. In the meanwhile World Athletics is making a billion-dollar decision based on a NY Times article exclusively based on Strava's data!

    0
    Aktionen für Kommentare Permalink
  • I am finding that since late December 2019 the elapsed time is often out by 25 to 30% although before I actually save the ride it is showing the right time. Most of my segment times are also similarly exaggerated. When I compare my rides with others I have ridden with by using Flybys it becomes really apparent as I fall further and further behind them on the animation despite riding alongside them on a ride of 2 hours. I’m feeling really uncomfortable about my data being publish with such distortion. Reading another thread it appears a number of others have the same problem despite having different phones. For the record mine is a Huawei p20.

    1
    Aktionen für Kommentare Permalink
  • I have been seeing similar but slightly different problems with my data recently (although I've been running more than biking lately but the issue seems related). Since noticing the issue I've started timing my runs with an independent stopwatch and here's what I've found.  I'm running the latest version of the Strava app on my Pixel 2 / Android V10

    1.  Moving time is always less than actual time even though I'm not stopping at all.   Generally the discrepancy is approx 20%

    2. Elapsed time is greater than actual time.  When I'm actually running the strava app tracks time equal to the stopwatch but when I save the activity the elapsed time changes.  When I download the .gpx files from Strava they show an elapsed time that matches the strava results page but do not match what was actually recorded. Erroneous elapsed times are approx 25% greater than actually recorded.

    3.  Average speed for the overall run is showing faster than reality because it is using the deflated moving time.

    4.  Average speed for segments is slower than reality because it is using the erroneous .gpx data.  

     

    0
    Aktionen für Kommentare Permalink
  • I just posted some relevant comments on this thread:

    https://support.strava.com/hc/en-us/community/posts/360056124992-Incorrect-pacing-on-Strava-on-Android?page=1#community_comment_360009063191

    I also included some links to other threads that might relate to the same underlying problem.

    0
    Aktionen für Kommentare Permalink
  • Very glad to find I'm not alone!  I've been having similar problems to Mark Baker with a Samsung S8 (Android 9) since late December when recording ride times.  Overall activity times and average speeds seem correct but some individual segment times are completely wrong.

    In my case it seems related to speed: downhill / flat segments (i.e. greater than around 15 km/h) seem reasonable, but all the significant uphill segments (less than 15 km/h) seem to be up to double the real elapsed time.  The 'analyse effort' data for these segments indicates recorded speed jumping up and down from zero when it should be near constant.  The overall route trace is a very close fit to the roads / tracks followed so I doubt it's an issue with bad GPS data and up until December I never had any issues on the same trails.  Following suggestions from other thread mentioned above I have the automatic time enabled already (it doesn't seem to help) but will try out the recommendation to apply a manual pause during my next activity to see if this works as a temporary solution.

    Please fix this Strava - I don't like suddenly being 'told' that I'm the slowest guy on the mountain!

    1
    Aktionen für Kommentare Permalink
  • Ditto - it is starting to get extremely frustrating now!!

    0
    Aktionen für Kommentare Permalink
  • Having the same issue with segments cycling.

     

    Some segments where I would consistently get 4-5 mins are now turning in to 10 mins sections one day and then back to 5 the next....completely random. I would be very late for work in my morning commute if this was the case as I leave the same time every day!

    When I do the strava flyby the timings for where I am at particular points are way out and by the time i'm at work the flybe still puts me as 2-3 miles away from my destination.

    This also seems to have started in December.

    0
    Aktionen für Kommentare Permalink
  • Finally... I am not alone after all.  I have also been experiencing many of these problems since December 2019 also.   Specifically, Strava is adding time to my activities after I stop recording and upload. Also, sometimes Strava records my speed as much slower than it is in reality.  For example, when I ride with friends and view the flyby Strava will show my pace as much slower when I actually was faster or riding at the same pace as my friends.  Interestingly, there does not seem to be a problem with the logging of my position relative to segments, just with the time and pace calculations.

    0
    Aktionen für Kommentare Permalink
  • Same here with a Galaxy S7 phone. Started in December, was fixed for a while but back to most of the same problems i'm reading here. Glad i'm not the only one but would like a fix soon. 

    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