No issues here with GPS and my BT connection with my iPhone 6 has not been lost since 3.7 was installed (happened almost daily before). Altitude sensor is also working better (after manual calibration to the correct altitude). Are these watches not all the same looking at hardware?
The difference does not have to come from different Hardware. it can be due to different usage / use cases... it is a lot different if you run with your phone connected or not for example. what SW features you use. environmental conditions etc. this is why the issues does not apply 100% of the people, but they obviously apply to MANY users
In my opinion this is not acceptable. Yes, problems will happen - sure, but that's exactly why a downgrade should be allowed. Why are we expected to use a malfunctioning expensive device for weeks when it's totally technically possible to go back to a functioning version until the problem is resolved?
@Garmin-Joey
i totally agree with that - it is not acceptable ! it took Garmin 6 months to stabilize this watch and now they broke basic functionality due to careless firmware update. GPS lock time is a very basic function that should have been tested before releasing 3.7 - so this is a QA failure. moving from few seconds to a few minutes of GPS lock time is a HUGE issue to be overlooked! as the previous version was super stable there is no reason Garmin will not allow reverting to it...
The problem seems to be the EPO file sync from Garmin express. I will try on my 645m
Viewed on the forerunner 935 threads :
Originally posted by Crispin_Ellisdon View Post For those still having the original “EPO Expired” issue, I have been having the exact same issue with both my Fenix 5 and Fenix 5+. After some messing around last night, I found that it was Garmin Express responsible for dropping an Expired EPO file on to the watch. If I closed Garmin Express completely (close on the system tray in Win 10), then deleted the EPO.bin files on the watches before ejecting from USB, the watches would initially show “EPO Missing” until after a few syncs with Garmin Connrct Mobile (GCM), at which point I got “EPO Current”. If I hooked up to Garmin Express again, the good EPO file from GCM would get overwritten by a bad EPO file from Express. So, until this is fixed, the key is to always close Express and delete the EPO.bin file before ejecting, every time you’ve hooked up the watch to your PC/Mac. Unsurpringly, my Fenix 5+ was back to it’s normal rapid GPS lock before my run this morning and the GPS track of the Run was better than my last 3 runs with the expired EPO (and yes, I did do a 30 minute static GPS soak with both watches last week, after the GPS 2.23 update). So having a curent EPO.bin file does appear to be important to getting good GPS tracks.
Whilst the Expired EPO files is obviously a Garmin data servers/Express thing, rather than device software, I’ve reported the issue to the Fenix beta team, so hopefully they can get the appropriate people to fix the bug in the data servers.
The problem seems to be the EPO file sync from Garmin express. I will try on my 645m
Viewed on the forerunner 935 threads :
Originally posted by Crispin_Ellisdon View Post For those still having the original “EPO Expired” issue, I have been having the exact same issue with both my Fenix 5 and Fenix 5+. After some messing around last night, I found that it was Garmin Express responsible for dropping an Expired EPO file on to the watch. If I closed Garmin Express completely (close on the system tray in Win 10), then deleted the EPO.bin files on the watches before ejecting from USB, the watches would initially show “EPO Missing” until after a few syncs with Garmin Connrct Mobile (GCM), at which point I got “EPO Current”. If I hooked up to Garmin Express again, the good EPO file from GCM would get overwritten by a bad EPO file from Express. So, until this is fixed, the key is to always close Express and delete the EPO.bin file before ejecting, every time you’ve hooked up the watch to your PC/Mac. Unsurpringly, my Fenix 5+ was back to it’s normal rapid GPS lock before my run this morning and the GPS track of the Run was better than my last 3 runs with the expired EPO (and yes, I did do a 30 minute static GPS soak with both watches last week, after the GPS 2.23 update). So having a curent EPO.bin file does appear to be important to getting good GPS tracks.
Whilst the Expired EPO files is obviously a Garmin data servers/Express thing, rather than device software, I’ve reported the issue to the Fenix beta team, so hopefully they can get the appropriate people to fix the bug in the data servers.
Great news !! Deleted the EPO.bin and sync only with GCM solve the problem. After this fix GPS initial fix is normal (<2s)
Seriously, this GPS thing happened to me as well during my 10k run for about 1.5 km with nonstop GPS notifications, pissingly distracting. Completly frustrated of being a very expensive beta rabbit user.
I am getting in a state to turn this device back to hell where it comes from, btw for 449€!!!
Seriously, this GPS thing happened to me as well during my 10k run for about 1.5 km with nonstop GPS notifications, pissingly distracting. Completly frustrated of being a very expensive beta rabbit user.
I am getting in a state to turn this device back to hell where it comes from, btw for 449€!!!
It currently is happening on all devices, see the other forums, even on 620
Thanks for the tip, but it doesn't work. Deleted the EPO file, got no GPS fix in about a minute, synced a couple of time to get a new EPO file and tried again: still GPS fix takes ages.
Yeah, don't do that! As I said in the "HowTo": - Make sure the Garmin Sync Software on your computer is *off / closed* - Connecting watch to computer - Use your explorer, search and delete the EPO file (this contains corrupt GPS data after the FW upgrade) - Disconnect your watch, put it next to a window and go into the activity mode (you dont need to start an activity)
Don't sync your watch directly with your phone or PC, because that will just download a defect EPO again. Let your watch find GPS on it's own for a few times.
Edit: Getting the first GPS Fix can take up to 20 Minutes without an EPO File.
