A super quick post to provide a little context on an issue Some (but not all) people who know are looking to see if your recorded GPS tracker is set to a hundred meters or more. In general, your route is correct, but it can be displaced to one side or the other. However, in many cases when the workout is completed, it isolates itself. In other words, it’s mostly a one-time issue.
This issue mostly affects companies that take advantage of the Sony GPS chipset in their devices, which are basically all new Garmin devices in the last few years, most new Sunto devices in the last few years, all Polar devices in the last few years, all Coros devices. , Vahu rivals and more. Or more or less everyone except Pal.
Very rough list of affected devices (I’m losing a ton here, this is just the most popular)
Coros everything except the original Coros Pace
– Garmin Forerunner 45/245/945 / Phoenix 5 Plus / Phoenix 6 / Mark / Vivoactive 3/4 / Venu
– Garmin Edge 130/130 Plus 530/830/1030 Plus
– Polar Ventage V / M / V2, Grit X
– Sunto 5 and Sunto 9
– Vahu alive
Again, I’m losing the botloid here, but it’s a big ticket from the top of my head.
All of these companies have switched to Sony GPS chipsets around 2018, with Polar and Sunto initially jumping on the ship, followed by Garamin, Coros and more. Sony GPS chipsets are widely used by these companies because of their long battery life and power savings.
But – that’s beyond all issues, and not the cause of this issue. The issue has to do with the Ephemeris data file, also called the EPO file (Extended Forecast Orbit) or Connected Predictive Ephemeris (CPE). Or a blank satellite pre-cache file. This is a file that is frequently distributed on your device (usually every few days). This is the file that your watch immediately detects GPS satellites when you go out. It’s basically a cheat sheet where the satellites are for the next few days, or for a week or so.
Your watch or bike computer This file is automatically retrieved via Bluetooth Smart from your phone, WiFi or USB depending on how you connect your watch. Your watches sync and most companies deliver it when a new version is needed. So from your side, you do nothing – it happens quietly in the background.
Right now, the data in this file is incorrect, and thus the data your watch uses for the first few minutes is also incorrect – leading to se fasets. You can see an example of this below A DCR reader:
The only thing that sustains the clock is the connection to the GPS satellites on the length of the workout, It will usually improve itself again As it pulls updated data from above. Most people are reporting that it will happen Resolve yourself by the end of the workout, or by the next workout. You can see another DCR reader here:
Right here – the same bugs at the starting points on my Phoenix 6X Pro and my wife’s forerunner 45S, then they sort themselves out – I walked, it ran, so my way is more accurate because I think to get the fix More time pic.twitter.com/tZ4ysgYPtW
– ac72 (7 ac72) January 2, 2021
To help prevent this, You can easily stick your watch / bike to the computer and record an hour’s workout, then discard it.. It has received the necessary satellite information to potentially improve it.
But it will not affect everyone. For example, I tried to put it off track today with two Sony based watches (Garmin FR745 and FR945) – and it didn’t work out. I suspect this because in my case the clock was pushed a little while playing with my kids yesterday and today, so my guess is that it has already been downloaded for the need to get out of the gate. I also tried with two non-Sony chipsets (Phoenix 5S and Apple Plus and Watch SE), and nowhere did I see any problems.
Talking to Garmin today, They are working on rectifying the issue, That they believe it will probably be that they will only update the satellite pre-cache data from the server, which in turn will catch your watch the way it always does. Also First they (and others) are working to sort out exactly what is wrong with the resulting data..
Talking to another person in the industry dealing with this issue, they noted that technically 2020 was 53 weeks, and this is the 53rd week. As such, the questionable Sony data file issue may actually be tied to that complexity.
Look… Just when you thought you ran away in 2020, it will still be waiting for you at the start of your run.
With that – thanks for reading!
.
