"GPS signal lost" notification popping up during a race is extremely annoying
-
@sartoric
I agree, in a “race mode” this notification could be smaller… it is good to be informed about that, but as @silentvoyager says you will not pause the watch because of that.
I wouldn’t even pause it during general non racing activities.
I take bets if and when this would be implemented… … too many very good ideas in this forum that overload Suunto team… -
I find it similarly bad design decision as with S5 “keep moving to see direction” notification. There are tons of ways to notify the user without obstructing the metrics and displaying full screen plain text is one of the worst ones.
-
yes it is!
-
@silentvoyager glonass does help at BT. Consistently come in at about 4.70 - 4.75 on that loop w my S9.
Surprised you lost complete connection though. Run there all the time and have never had that happen.
-
@Łukasz-Szmigiel said in "GPS signal lost" notification popping up during a race is extremely annoying:
I find it similarly bad design decision as with S5 “keep moving to see direction” notification.
And “the watch is locked” notification when trying to hit the lap button when the watch is locked. If not for that notification I could use the lap button as backlight.
None of this notifications are useful for a pro user that uses the watch as an instrument.
-
@stromdiddily said in "GPS signal lost" notification popping up during a race is extremely annoying:
@silentvoyager glonass does help at BT. Consistently come in at about 4.70 - 4.75 on that loop w my S9.
Surprised you lost complete connection though. Run there all the time and have never had that happen.
Yes, perhaps I should have enabled Glonass. I thought about that myself. I was surprised to see that another person’s Fenix X6 nailed the distance perfectly - 14.9 miles for the 3 loops.
It is interesting that the first loop on my S9 was pretty good, although still short on distance. But each next loop the quality deteriorated and it had cut corners more with each next loop. And finally it had lost the satellites twice on the third loop.
-
@silentvoyager said in "GPS signal lost" notification popping up during a race is extremely annoying:
Yes, perhaps I should have enabled Glonass
And perhaps that is a topic for a separate thread. I would create a custom battery mode with Glonass enabled and use when it matters.
But, even though enabling Glonass or Galileo significantly impacts battery life these settings are not under battery modes and instead global. Why?
Now, if I enable Glonass and forget to turn it off my watch wouldn’t last an upcoming 100 miler.
-
@silentvoyager I can answer one question (or 2)
It’s global afaik because it affects all operations. Even altitude calibration to time sync etc.
Regarding the battery mode, I think the chip can do that but not during runtime without being repowered on. But this might have changed or was my assumption, looking at the code of the sony about 1y ago. But that is smalltalk. IT should be possible.
-
@Dimitrios-Kanellopoulos OK, the default may still be global but there should be an option to override that under the battery mode to allow users to maximize the battery life.
For example, I’d have Glonass enabled by default, but for running a 100 miler I’d create a custom mode with GPS only. And switching between modes would remind me how long the battery will last in each mode, taking into account whether Glonass is enabled or not.
-
@silentvoyager I agree. I hate GNSS switching modes as well.
-
@sartoric said in "GPS signal lost" notification popping up during a race is extremely annoying:
@silentvoyager said in "GPS signal lost" notification popping up during a race is extremely annoying:
the watch measured only 13.89 miles vs the official 15.6
Well, maybe because you’ve lost GPS signal?
I guess that fusedtrack can’t always do miracleI am pretty sure the distance ended up longer, not shorter due to switching to accelerometer measured distance during those 10 minutes. When I run on treadmill my watch typically measures 20-25% more than actual.
Looking at Movescount, the first loop was 4.57 mi, the second - 4.65 mi, and the third where the GPS was lost - 4.67 mi.
-
@silentvoyager GPS is slowing you down! Maybe use indoor run next time?
