S9 baro loses gps and never finds again
yesterday i observed a very strange behaviour of my S9 during an activity.
The S9 lost GPS and could not find it back again.
It was more or less like the behaviour described in this topic:
(I do not want to necro this topic, this is the reason to create a new one).
So here is what happened in more detail:
- running for about 21km in the open - using a runnning activity (no autopause) and navigation.
- then walking thourgh tunnels/buildings (GPS is lost there naturally).
- turning around and walking back to where i left the open.
- GPS signal was not found again.
Only stopping and starting a new activity worked.
Note: I was using stryd, connected as a power pod (so i get power metrics only).
I thought that fusedtrack/fusedspeed is messing around with algorithms, so i wonder if stopping the activity when entering a ‘gps unfriendly zone’ would prevent this.
Did you guys ever see/hear about something similar? What would you suggest to possibly prevent this behaviour? Lets hope this one time only experience 🤨.
Still there are some question for general use of GPS during an activity:
- Is there a way to reset GNSS during an activity?
- Is there a way to switch GPS+QZSS to e.g. GPS+QZSS GLONASS?
- What does this GPS+QZSS do? (QZSS is the unkown component here)
Best regards and stay healthy
@isazi thx for the info
@matthiasklug Did your watch restart? I have lost GPS during a race in a deep canyon and the watch asks if you want to wait or continue. I just ignore the message and GPS is re-acquired very quickly. If your watch restarted it takes time for the AGPS data to be unpacked and that is when it can take a long time for me to get a GPS fix. Restarts are rare.
no the watch did not restart.
The screen that usually appears
(e.g. when starting an GPS related activity immediately and GPS icon is not blinking) did not appear, or i did not notice -i can not confirm that the pause&wait/discard-screen appeard-.
What happened/what i can confirm is that
the navigation display was looking like that:
And all the metrics pace, distance, etc. were messed up. The activity was still running (so was I - literally).