This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firmware v5.20 user discussion / feedback

The release announcement for firmware version 5.20 certainly makes this sound like a compelling update:

Changes made from version 4.70 to 5.20:

  • Added support for Connect IQ 1.3.0 SDK. See the Connect IQ 1.3.0 SDK for a list of new features.
  • Added support for broadcasting optical heart rate over ANT to other devices during an activity.
  • Added support for phone apps to subscribe for more frequent data updates.
  • Added support for Apple Media Service - users can now control any active music player, e.g. Spotify, as well as volume (requires iOS 8.0 and higher).
  • Fixed an issue in which text on some Connect IQ watch faces may not display correctly.
  • Several improvements to optical heart rate.
  • Various bug fixes and stability improvements.



I'd managed to hold off updating to firmware v4.70 (from v4.60) for many weeks – after transferring the firmware file to my watch but dismissed the update manually – after seeing all the reports of issues, especially around garbled notifications, but the other night the watch somehow got updated to v4.70 anyway. I might as well take the leap and go to v5.20, now that it appears in Garmin Express for me several minutes ago.

Who else is game? :)
  • Former Member
    0 Former Member over 8 years ago
    Instant Pace Bug!

    i've notice only one issue so far after updating yesterday night: during this morning run, the current pace fluctuated way more than it ussually does. Today i did an easy, constant pace run so i wouldn't expect that variations (one second it would show i'm running at 4:40 min/km and the next it would show 5:50 min/km. Has anyone else seen this?


    Ahh yes. Me too. Forgot to mention in previous post. My pace on watch was all over place; very erratic.


    I also have this pace issue. I was at a very stable 9:30 min/mile, and the watch would fluctuate between 8:20 min/mile and 12:45 min/mile. This made the pace alert (9:15 - 9:45 min/mile) completely freak out and useless. Please look into this Garmin.

    This happened on GPS+GLONASS and GPS only, with and without pace alerts.
  • Interesting with all the people complaining about the pace fluctuations. I thought I noticed something similar when I was using 5.07 beta, but figured it was all in my head and maybe I was just tired from marathon training and was running inconsistently.

    I was going to run on the dreadmill tonight to avoid the heat, but now I'm set on suffering outside just to test the pace accuracy.
  • Former Member
    0 Former Member over 8 years ago
    Went another run this morning. Pace is still very erratic and heart rate is rendered useless now. For a 6 mile run average pace was 130. I'd usually be around 150.
    What's going on Garmin???
  • Former Member
    0 Former Member over 8 years ago
    Pace issue after update.

    After update my pace is fluctuating way too much. More than a minute while I was keeping the same speed. This information is useless now.
  • Former Member
    0 Former Member over 8 years ago
    i've notice only one issue so far after updating yesterday night: during this morning run, the current pace fluctuated way more than it ussually does. Today i did an easy, constant pace run so i wouldn't expect that variations (one second it would show i'm running at 4:40 min/km and the next it would show 5:50 min/km. Has anyone else seen this?


    I had an exact same issue this morning! Started my run right after updating.
  • Oh great, the sole reason for leaving tomtom and moving to garmin was the instant pace was unusable.
    Now i will have to wait another 2 months to see if garmin can fix this without breaking anything else.
    For the record I clicked remind me so I could see what other people thought of the update, and it went ahead anyway. Have a race in a month that I will need reliable instant pace for.
    Thanks garmin.
  • For the record I clicked remind me so I could see what other people thought of the update, and it went ahead anyway.
    That would have meant you were to be prompted each and every time you prepped a timed activity, which makes it easy to make a user mistake at one point or another to ‘approve’ the update just by pressing to (try to) get on with the activity.

    If you didn't want that, then you should have selected Dismiss. The firmware update file has already been uploaded to your watch, but at least you'd have to take the initiative to dig through the watch's menu tree to start the update.
  • Still no HRM lock

    I updated to 5.20 a couple days ago. Tried the HRM lock. Got it very quickly. Hopeful. Tried it for my run yesterday. Got quick HRM lock. Did my run. All was fine. But this morning, I am still waiting, going on 10 minutes, for a HRM lock. So that problem is still not fixed. This is the same pattern I've seen from the start with this ongoing bug. It works the first time or two after updating or restarting, then it will not get HRM lock.
  • Ok, I went for a run outside as promised last night. I was supposed to be doing 8 miles of strides, but I decided to stick to a nice even pace to get a better baseline for testing the pace and HRM. I ended up doing 5 miles outside, then finishing the last 3 miles on the treadmill due to heat.

    One minor thing:
    I seemed to have lost a lot of my settings customization when I upgraded this time around. I don't mean Connect IQ apps or watch faces; I mean random device settings. Example, I usually have Alert Tones (Settings -> System -> Sounds) turned off, but it was reset to the factory default setting of "On" after the upgrade. There were a few more as well. I also lost my steps and heart rate data for the day. Not a huge deal, just something to note.

    Instant/Current Pace:
    It's definitely not working as well as it used to. I dialed in a nice easy pace and let the watch level out. It would randomly display exaggerated pace numbers. One second it would read 8:00 min/mile, the next it would read 9:45 min/mile, then 6:30 min/mile. It was actually quite comical. It would make it very hard to dial into a pace on a long run, or to do any kind of speed work where you need to lock into a pace. The release notes don't say much in regards to any of this, so I'm unsure if they changed logic for calculating instant pace, or if something is going on with the GPS and the instant pace is just a victim. Or maybe due to the fact my device settings were reset, maybe I lost all the GPS cache and stride details that help calculate these things? FWIW, Average pace and lap pace seemed fine.

    HRM:
    Getting a heart rate lock is instant for me now. As soon as I open an activity, I already have a heart rate being displayed. The only weird thing is, I don't get the heart rate lock notification until some time after. So is the heart rate being displayed premature, and it doesn't actually have a good lock yet? As others have reported, it seemed to take a few minutes into the run (5 or so in my case) to actually show my true heart rate. It was far too low and inaccurate for the first 5 minutes. No cadence locks or anything of that nature for this run. I haven't really paid attention to RHR yet. I like to give it a few days after an upgrade to settle in.

    Treadmill pace:
    I didn't plan on testing this, but since I had to finish out my run on the treadmill, I kept my eye on it. Treadmill pace for me has always been touchy. There's a sweet spot for pace accuracy, and if I deviate from it at all, it's not great. Last night it was accurate at 8:30 min/mile, but totally inaccurate when I jumped up to 7:00 min/mile. Even more so than usual. Again, I don't know if it lost all my underlying data that helps calculate pace via the accelerometer, but I'll keep my eye on it.

    To be fair, I'll try it out for a few more days. In my experience, I like to let the devices have a few days to "level out" before freaking out. Sometimes little quirks will work themselves out. Especially if I lost a lot of my settings, maybe the watch needs a few days to build up caches, etc.

    If anyone is totally struggling with this upgrade and want to revert back, you might be able to via the old beta version download. Version 5.07 beta and version 4.70 are in that download folder. I haven't ever attempted this and have no idea if it would work, so do so at your own risk.
    http://www8.garmin.com/support/download_details.jsp?id=10450
  • Former Member
    0 Former Member over 8 years ago
    Pace issue

    The same pace issue as others, Garmin please FIX IT.