To help resolve this, you can simply stick your watch/bike computer outside and let it record an hour exercise, then simply discard it after that. It’ll have gotten the needed satellite info to most likely correct itself.
But it will not affect everybody. I tried today with two Sony based watches (Garmin FR745 and FR945) to get it to lay down an inaccurate track– and it wouldn’t. I suspect this is since in my case the watch had actually been bumped on a few times while having fun with my kids the other day and today, so my guess is it had already re-downloaded what it required to be proper out of the gate. I also tried with 2 non-Sony chipsets (Fenix FIVE and Apple Watch SE), and didn’t see any issues either.
In speaking with Garmin today, they’re working on a fix for the concern, that they think will probably be that they simply upgrade the satellite pre-cache data from the server, which in turn your watch will get just as it always does. However initially they (and others) are working to sort out what precisely is wrong with the information that’s triggering this.
In speaking to another individual in the industry handling the issue, they noted that technically 2020 had 53 weeks, and this is the 53rd week. As such, the suspect Sony information file concern might really be connected to that complexity.
See … just when you thought you left 2020, it’s still there waiting for you at the start of your run.
With that– thanks for checking out!
Just a simply quick very fast provide an offer bit small context on an issue someProblembut not however )folks are seeing where your recorded GPS tape-recorded is offset by balanced out of a hundred meters or more. Your watch or bike computer immediately gets this file through Bluetooth Smart from your phone, WiFi, or USB, depending on how you connect your watch. Now, the information in this file is incorrect, and hence the information your watch utilizes for those first couple of minutes is likewise incorrect– leading to the offsets. I tried today with 2 Sony based watches (Garmin FR745 and FR945) to get it to lay down an inaccurate track– and it wouldn’t., that they believe will most likely be that they simply upgrade the satellite pre-cache data from the server, which in turn your watch will grab just as it always does.
Just a very fast post to offer a tiny bit of context on a concern some(however not all )folks are seeing where your recorded GPS track is offset by upwards of a hundred meters or more. In basic, the pattern of your path is right, however it may be displaced to one side or the other. In lots of cases by the completion of the workout, it sorts itself out. Simply put, it’s primarily a one-time concern. The issue mainly appears to be impacting business that take advantage of the Sony GPS chipset in their gadgets, which is essentially all brand-new Garmin devices in the last few years, many new Suunto gadgets in the last few years, all Polar gadgets in the last couple of years, all COROS devices, the Wahoo RIVAL, and more. More or less everyone other than Apple.
Very rough list of affected gadgets (I’m missing a load here, these are just the most popular ones)
— COROS GPS watches (requirement to verify initial Pace though)
— Garmin Forerunner 45/245/745/ 945/Fenix 6/MARQ/Vivoactive 3/4/Venu
— Garmin Edge 130 Plus 530/830/1030 Plus
— Polar Vantage V/M/V2, Grit X, Ignite
— Suunto 5 & & Suunto 9
— Wahoo RIVAL
Again, I’m missing a boatload here, but that’s the huge tickets ones off the top of my head.
All these business have changed to the Sony GPS chipset since around 2018, with Polar and Suunto at first jumping onboard, followed quickly thereafter by Garmin, COROS, and more. The Sony GPS chipset is extensively utilized by these companies since of the power savings delivering longer battery life.
However– that’s all besides the point, and not the cause of the issue. The issue is to do with the ephemeris information file, also called the EPO file (Extended Prediction Orbit) or Connected Predictive Ephemeris (CPE). Or simply the satellite pre-cache file. That’s the file that’s delivered to your gadget on a frequent basis (typically every few days). When you go outside, this file is what makes your watch near-instantly find GPS satellites. It’s essentially a cheat-sheet of where the satellites are for the next couple of days, or approximately a week or so.
Your watch or bike computer automatically gets this file by means of Bluetooth Smart from your phone, WiFi, or USB, depending upon how you link your watch. A lot of companies deliver it anytime your watch syncs and needs a brand-new version. From your side, you never ever do anything– it just silently occurs in the background.
Now, the data in this file is incorrect, and thus the information your watch uses for those first couple of minutes is also wrong– leading to the offsets. You can see an example of this listed below, from one DCR reader:
And another: As the watch sustains it’s connection with GPS satellites over the length of the workout, it’ll usually re-correct itself as it pulls in updated information from above. The majority of people are reporting that it’ll resolve itself either by the end of the workout, or the next workout. You can see that here from yet another DCR reader:
Same here– similar mistakes on start point on my Fenix 6X Pro and my wife’s Forerunner 45S, then they sort themselves out– I walked, she ran, so my path is more precise as it had more time to get a fix I guess … pic.twitter.com/tZ4ysgYPtW
— ac72 (@ac72) January 2, 2021