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? :)

0 Former Member over 8 years ago

The unexpected current pace problem ruined my training today. Very disappointed of Garmin now and wondering if I should return the watch to the store.

0 Former Member over 8 years ago

anyone have a link to download the 4.6 firmware?

0 KR17 over 8 years ago

I was able to revert back to 4.70. So far nothing adverse.

Trouble is I deliberately stayed at 4.6 as everyone was saying 4.7 was shyte.
Now I'm stuck at 5.2 which is even shyter.

Sort it out Garmin, this bloody thing is 9+ months old now, we are well past teething troubles.

0 FlipStone over 8 years ago

Hmmm, pace/speed problems are only the instant variant right?

I usually work with avg or lap pace and that seems to be fine to me in my case. Calories, not sure, had a pretty active day (walking the dog twice, ran 15k and doing household chores) so while 3757 calories is a lot (my weight is about 65kg) it might be true. Run was already ~900... Haven't noticed weird calory counts earlier either.

Overall no complaints on this firmware from my side, although I'm not quite sure if it's a worthwhile update from the 5.07b which also worked great.

0 Former Member over 8 years ago

To be clear, it's not just a problem displaying current pace. It's actually recording the wrong pace, which affects workouts, lap/avg pace, etc. It's just that it probably averages out to be close enough with a wide enough pace window.

This morning I had a 0:10 pace window in my workout, and it was beeping at me to slow down for 8:15 pace when it felt about 9:30. It took a LONG time before it settled in.

You can easily see the difference in pace graphs on Garmin Connect. It's much jumpier now.

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?

0 Former Member over 8 years ago

Erratic current speed/pace in 5.20

after updating to firmware 5.20, ran a half yesterday with my fr235. i also observed the erratic current pace/speed that the watch now indicates. personally i rely quite a bit on the current speed/pace to tell me whether to speed up or down cross referencing with my HR for my runs.

as many mentioned, the lap pace appears to be accurate as it averages out the erratic ups-and-downs.

I didn't have this problem in 4.70. Is there a way for me to push the watch to 4.70? Is Garmin gonna fix this issue? I too have a race coming up in 2 weeks time. Not exactly a good time to have the watch bugging up on me now.

0 Former Member over 8 years ago

My pace is also crazily all over the place. Watch is virtually useless to me now. Please fix!!

0 francrubio over 8 years ago

Yesterday , i was ready to connect and recharge my watch for todays run, and i have no clue on why the update started because i'm 100% sure that i didn't pressed the buttons.
But ...well,... here we are.

Today Long Run (15K - 1h30') with FR235 with FW 5.2
https://connect.garmin.com/modern/activity/1303249605

Heart Rate: It took just 3 seconds to show me the NEW aleart "Wrist HR ready" , nice, less than what it took to the GPS+GLONASS to acquire signal.
Apple Media Service: Tested with Spotify, and Podcast. Working fine. LOVE YOU!
Watch Faces: Those that stopped working properly on the previous v4.7 update, now working fine.
Alerts Vibration: This time , configuration was kept properly.
Pace: I used to use the avg pace, that seems to be fine, then i can't tell you how the instant peace it is.
Whatsapp Notifications Repared: No more reverse text.

Seems that Garmin sent a bunch of repairs on this FW. But i still think that it's not admisible to have this kinds of bugs, or errors.

Note: During the afternoon, the Watch Face went crazy, and when trying to list all the watch faces to choose the previous one, it was imposible. Restarted the FR, and now seems to be working fine.

0 KR17 over 8 years ago

I was able to revert back to 4.70. So far nothing adverse.

How did you do this? I downloaded 5.07 beta and tried as per the readme but not been prompted and if I got to updates on the watch it just tells me to check the garmin website?

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.