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? :)
  • This latest fw is a mess. I have several issues. The aforementioned issue with resting calories being all of a sudden 3-400 calories higher per day.

    I also have problems getting a GPS lock, the clock is all out of whack and the time keeps changing. It won't set automatically at all.

    The HR monitor is erratic. Despite turning it on/off several times which usually fixed any inaccuracy on previous fw, or where the HR would get stuck - it is not registering the correct HR it was sat between 60-70 bpm all day yesterday with a high of 80 and I was way over that a lot of the day.

    This is the first fw update since I bought the (potentially soon to be returned) watch, how long does it normally take to iron out these things post fw release?
  • Former Member
    0 Former Member over 8 years ago
    Firmware revert

    Connect your Forerunner 235 to your computer using the USB cable.
    Download and unzip Forerunner235Beta.zip. Place the GUPDATE.GCD file in the \GARMIN folder of your device's internal storage drive.
    Disconnect your device from the computer, approve the update on the watch, and wait for the update to finish.
    If you would like to revert to the last public release software, follow the above steps but place the GUPDATE-470.GCD file in the \GARMIN folder. Rename the file to GUPDATE.GCD before disconnecting your device. NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.


    Tried this procedure to attempt to revert to 4.70, but sadly it does not work. I did not get any promopt to approve the update, and the next time I connect the watch, the file has been deleted from the \GARMIN folder. This is on a Mac using Garmin Express. I eject the watch "drive" in Finder before disconnecting, to make sure that the file system is OK before the physical disconnect. Your original filename for 4.70 is different than mine, though. Where did you download that from?

    I'm new to Garmin. It's rather hard to understand how it's possible to release new firmware with a critical bug of this magnitude. The Garmin firmware release process must be badly broken. Very unprofessional. Were the real engineers all on summer holiday when this happened, or is this actually normal for Garmin?
  • Tried this procedure to attempt to revert to 4.70, but sadly it does not work. I did not get any promopt to approve the update, and the next time I connect the watch, the file has been deleted from the \GARMIN folder. This is on a Mac using Garmin Express. I eject the watch "drive" in Finder before disconnecting, to make sure that the file system is OK before the physical disconnect. Your original filename for 4.70 is different than mine, though. Where did you download that from?

    I'm new to Garmin. It's rather hard to understand how it's possible to release new firmware with a critical bug of this magnitude. The Garmin firmware release process must be badly broken. Very unprofessional. Were the real engineers all on summer holiday when this happened, or is this actually normal for Garmin?


    Originally Posted by scottj2 View Post
    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/downl...s.jsp?id=10450
  • Former Member
    0 Former Member over 8 years ago
    Short term I'd be happy with a 3/5/10 second average pace, the instant is so jumpy that I can't really use it...

    Just had a thought, has anyone with a foot pod tried going into its settings and selecting it as the pace source always? (Rather than only when there's no gps). Ie. Is the pace bug jumpyness only with gps pace?


    My footpod (auto calibrated) is set to be sole source of speed data and given the variability of data I am getting would SUGGEST that GPS is perhaps interfering with the output.

    It is also worth noting that that the autocalibration factor has moved over 3 points SINCE 5.20.
  • I'm new to Garmin. It's rather hard to understand how it's possible to release new firmware with a critical bug of this magnitude. The Garmin firmware release process must be badly broken. Very unprofessional. Were the real engineers all on summer holiday when this happened, or is this actually normal for Garmin?


    How have Garmin managed to do this. There have been several recent betas that people have been testing, and whilst I haven't the feedback ahs been OK.
    Then they obviously ignore the betas and release untested functionality.
    You only have to look at the amount of people complaining to see that any form of testing would have identified this issue.
    Completely unacceptable, right in the middle of people's racing season.
  • Former Member
    0 Former Member over 8 years ago
    Originally Posted by scottj2 View Post
    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/downl...s.jsp?id=10450


    That download link is truncated and does not work. Could you post the full link, please?
  • Former Member
    0 Former Member over 8 years ago
    i have just backdated my firmware to 4.70. this latest firmware is really not ideal for my training. as per mentioned above, how can garmin push out a firmware that cripples one of the main data field for us runners? (referring to instant pace/speed)

    my last 21km was more painful than it should have been due to the instant speed indicating that i have slowed to a crawl and believing in it, i pushed for a faster cadence and my breathing and heart rate just when bonkers along with that. then suddenly it showed that i have been sprinting and then i slowed down...did Garmin intended this to happen? Force Fartlek training onto every distance runner?

    something that i noted, after the backdate, my garmin express and garmin connect still indicates that i am on firmware 5.20. it's just freaking weird for now. hopefully garmin get this fixed soon. =(
  • Former Member
    0 Former Member over 8 years ago
    FW download link

    That download link is truncated and does not work. Could you post the full link, please?


    Found it: http://www8.garmin.com/support/download_details.jsp?id=10450
  • Former Member
    0 Former Member over 8 years ago
    is there any hope for me to get a download link for firmware 4.60? i don't want firmware 4.70, it's as bad as 5.20
  • Its earlier in this thread.