Data on Galaxy Watch not corresponding with data on phone

Goodmorning,

To start things off; I'm a new user to Strava and I used to run with Nike Run Club. Since I've bought a Galaxy Watch (Samsung), I've tried to run with Strava on my watch a couple of times now. 

Here's the problem I've experienced. If I look at my running history on my watch the pace differs from the pace displayed on my phone/website. 
The exact time (seconds) are not displayed in the running history on my watch.

I figured this might be because I've paused the run to tie my shoelaces, but that's just guessing.


Has anyone experienced similar problems, how did you solve it?
Let me know!

1

Comentários

7 comentários
  • I have been using the Active watch 2 and wanted to use Strava. The trouble is, Samsung Health has my Average pace around 8 (which is right) but when it syncs with Strava it shows up as 5 something which is ridiculous for me. Unless they fix this, I will have to leave Strava because it is misleading for the community features. 

    0
    Ações de comentário Permalink
  • I have this issue as well, unless I set the run to "race" the avg pace etc is not accurate.
    When I look at the pace graph it has lots of spikes in strava when I haven't paused or stopped. The cadence graph is accurate.
    This is using samsung health synced with strava

    0
    Ações de comentário Permalink
  • Yes, it is driving me crazy. I have used Endomondo in the past and it doesn't do this but I got the Active watch 2 and just wanted to use Samsung Health and Strava because the Endomondo and Strava apps on the watch are terrible. But I really don't like the stats being pulled over. I wish someone in support would take notice and work with Samsung.

    0
    Ações de comentário Permalink
  • Same here galaxy watch using Samsung health app.

    Data displayed in strava is completely different to that in Samsung health app.

    0
    Ações de comentário Permalink
  • I'm having this issue. While feeling guilty about beating lots of segment records with false timings, it also means that other people's segment times are wrong. In essence, it means that Strava's segment timings have unrealistic times that no one can actually beat.

    0
    Ações de comentário Permalink
  • Samsung tcx file has data has trackpoints with only HR data and some empty trackpoints but surely strava should be able to parse this properly? if there is no gps lat/long that does not mean pause does it?

    As the above poster has said there are so many users who have uploaded these tcx files, please strava fix the parsing and reparse them so we can have more accurate data!

    extract from recent samsung tcx file:

    <Trackpoint>

       <Time>2020-06-16T02:14:07Z</Time>

    </Trackpoint>

     

    <Trackpoint>

      <Time>2020-06-16T02:14:10Z</Time>

      <Position>

      <LatitudeDegrees>-37.675724</LatitudeDegrees>

      <LongitudeDegrees>145.04128</LongitudeDegrees>

      </Position>

      <AltitudeMeters>101.45887</AltitudeMeters>

      <Cadence>85.2685</Cadence>

      <Extensions>


      <TPX xmlns="http://www.garmin.com/xmlschemas/ActivityExtension/v2">

      <Speed>3.235</Speed>

      </TPX>

      </Extensions>

    </Trackpoint>


    <Trackpoint>

      <Time>2020-06-16T02:14:11Z</Time>

      <HeartRateBpm>

      <Value>91.0</Value>

      </HeartRateBpm>

    </Trackpoint>

    0
    Ações de comentário Permalink
  • Lots of discussion on the Samsung Wearable Community, about this same issue.

    'Samsung Health to Strava isn't Correct'

    Latest post, from 28th June 2020, says Sean from Strava is looking into the issue. 

    0
    Ações de comentário Permalink

Por favor, entrar para comentar.

Não encontrou o que estava à procura?

Nova publicação