GPS far out in London half
-
@FindingUsername
the screenshot of your laps no not really tell me much at first sight. could you please send screenshots of the track or even better a public link to your activity.few questions in advance: what battery mode did you use? did you maybe activate power saving?
and to comment already something in advance: I’ve recently learned that GNSS is a very sensitive system with insane technology… I’ve bad a bad track beginning of this week, too. some days are better, some worse… sometimes good in the morning and few hours later it turns bad. as a spoiler: that’s not Suunto, that’s the systems in general
-
Thanks for your thoughts. Not sure which power mode. Suspect, just checking now, it might have been power saving. Did that do it?
Not sure there are any public tracking type details I can pass on.
The only point sending the previous screenshot was to point to my miracle mile 3 - and in detail below.
Other screen shot attached too. Thanks!
-
@FindingUsername
please check if you used battery performance mode and if power saving in the watch settings are disabled.I recently had a GNSS issue, too, and it didn’t happen since.
zoomed to my actual track:
zoomed out to the entire recording
-
@freeheeler @FindingUsername I think it is not a GNSS issue, but Suunto counting distance twice, hence insane pace
This is still not resolved after a year and half. Before that update it worked ok.
https://forum.suunto.com/topic/6243/running-in-a-tunnel-caused-issues-in-the-total-distance-computation -
@Likarnik would that not imply that the pace should be a factor 2 faster? Rather than almost a factor 5?
-
@el2thek said in GPS far out in London half:
@Likarnik would that not imply that the pace should be a factor 2 faster? Rather than almost a factor 5?
do you say that the error is not true ?
-
@Mff73 Not at all. Just that distance * 2 = pace / 2. Whereas looking at the pace per mile OP posted the pace changed a lot more than that.
-
Can confirm I didn’t speed up quite that much in the tunnel.
Yes, probably it was on power saving mode.
But this is a simple issue of a tunnel screwing the whole thing (surely?), which is an unacceptably stupid and obvious mistake for a clever phone/app to make.
-
@el2thek I did not dig into details. You can check this post from my link https://forum.suunto.com/post/96865, @tuxella also had 0,33min/km and 1,12min/km in his example not sure how this is calculated, maybe some FusedSpeed magic that we don’t know about.
-
Can you guys provide me (also in private) with links to activities that have this issue (and on which it is clearly visible) that I can share with Suunto?
