Firmware 5.20 and current pace

I noticed that the stability of the current pace value became definitely worst than before. Now it is rapidly changing +/- 30 sec/km or even more while I'm running in a constant pace.

Same here. Did long run with long intervals at 5:35/km Saturday, instant pace was all over the place (from 4:30 all the way to 6:30). You could just see it in waves, going up, up, up, then down, down, down... I just held constant pace as much as I could and relied on lap pace. Result was ok. Did short intervals this morning (4:10 pace for 300m), at this higher pace the effect was less visible but still present; again I relied on the lap pace and managed to do reasonable intervals.

Surprising that something as basic as this could get screwed up in a multi-product, mid-lifecycle firmware release...

Same pace problem since update to 5.20

I have the same problem for me on my forerunner 230 since the update, the current pace is juste RIDICULOUS changing from 5.10/km to 6.15/km within a 3 seconds time frame !
GARMIN seriously how can your break such a CRITICAL metric in your device !!!

Waiting for a (imminent) update, and be quick, SUUNTO is knocking on my door right now.

Rollback to 5.07

It appears from the FR235 posts that some have tested a rollback to 5.07 beta, which seems to correct the issue. So at least this gives a potential fix (assuming there is no patch issued in the next few days).

I've already asked them for a fotfix - rollback to 5.07 - they said no way :(

EDIT.

Just found this one on 235 forums:
"Since some folks seemed to be confused on how to revert back to 4.70 or 5.07 beta, I'll provide some instructions. I did this successfully yesterday after some trial and error.

Some important notes:
1. It seems you can't directly install the beta software, you have to install 4.70 first. Then if you want to install beta, you can do so after installing 4.70.
2. YOU WILL LOSE ALL SETTINGS. Garmin says this in their instructions, and it's definitely true.
"NOTE: If you revert to an older version of software, all of your settings will be reset to defaults. "
Therefore, make sure your watch has been synced in Garmin Connect first to backup all your data. Take note of any personal settings you currently have because you'll need to reapply them.
3. I didn't lose any of my Connect IQ apps (watch faces, etc). But you may need to reconfigure them after.
4. You may also need to repair your watch to your phone and/or bluetooth devices.

Instructions:
1. Go to this URL: http://www8.garmin.com/support/download_details.jsp?id=9919
2. Download the zip file to your computer and unzip it. There will be two files of interest in there:
GUPDATE.GCD - This is the 5.07 BETA software. You won't be able to install this first. You have to revert to 4.70, then if you wish you can install this beta version after.
GUPDATE-470.GCD - This is version 4.70.
3. Connect your watch to your computer. DO NOT let it open in Garmin Express or Garmin Connect. Shut down all that business down, and open the watch directly in your file explorer.
4. Copy the GUPDATE-470.GCD file directly to the \GARMIN folder on your watch.
5. IMPORTANT: Rename that file that you just copied to your watch to GUPDATE.GCD.
At this point you should have one file directly on your watch under the \GARMIN folder. The file should be named GUPDATE.GCD
6. Unplug your watch.
7. Wait for it to prompt you to update.
8. Verify the firmware version by going to the System Settings on your watch.

You should now be running 4.70. If you want to update to the beta version, repeat the above steps, but with the beta version in the zip file you downloaded from Garmin. (See step 2 above.)

I'm successfully running 5.07 beta now, and can verify the instant pace is working properly. Therefore I can assume the new instant pace bug was definitely introduced in the new firmware. My girlfriends watch was also effected by the new firmware, so I suspect this is a widespread bug and it's a big one, in my opinion."

Reverting Frimware for FR230?

Do you know if this rollback solution works with the FR230 as well as the 235? Is the firmware identical for both? Don't want to brick my watch if I just need to wait a couple of days for Garmin to get a fix out there.

I've already asked them for a fotfix - rollback to 5.07 - they said no way :(

EDIT.

Just found this one on 235 forums:
"Since some folks seemed to be confused on how to revert back to 4.70 or 5.07 beta, I'll provide some instructions. I did this successfully yesterday after some trial and error.

Some important notes:
1. It seems you can't directly install the beta software, you have to install 4.70 first. Then if you want to install beta, you can do so after installing 4.70.
2. YOU WILL LOSE ALL SETTINGS. Garmin says this in their instructions, and it's definitely true.
"NOTE: If you revert to an older version of software, all of your settings will be reset to defaults. "
Therefore, make sure your watch has been synced in Garmin Connect first to backup all your data. Take note of any personal settings you currently have because you'll need to reapply them.
3. I didn't lose any of my Connect IQ apps (watch faces, etc). But you may need to reconfigure them after.
4. You may also need to repair your watch to your phone and/or bluetooth devices.

Instructions:
1. Go to this URL: http://www8.garmin.com/support/download_details.jsp?id=9919
2. Download the zip file to your computer and unzip it. There will be two files of interest in there:
GUPDATE.GCD - This is the 5.07 BETA software. You won't be able to install this first. You have to revert to 4.70, then if you wish you can install this beta version after.
GUPDATE-470.GCD - This is version 4.70.
3. Connect your watch to your computer. DO NOT let it open in Garmin Express or Garmin Connect. Shut down all that business down, and open the watch directly in your file explorer.
4. Copy the GUPDATE-470.GCD file directly to the \GARMIN folder on your watch.
5. IMPORTANT: Rename that file that you just copied to your watch to GUPDATE.GCD.
At this point you should have one file directly on your watch under the \GARMIN folder. The file should be named GUPDATE.GCD
6. Unplug your watch.
7. Wait for it to prompt you to update.
8. Verify the firmware version by going to the System Settings on your watch.

You should now be running 4.70. If you want to update to the beta version, repeat the above steps, but with the beta version in the zip file you downloaded from Garmin. (See step 2 above.)

I'm successfully running 5.07 beta now, and can verify the instant pace is working properly. Therefore I can assume the new instant pace bug was definitely introduced in the new firmware. My girlfriends watch was also effected by the new firmware, so I suspect this is a widespread bug and it's a big one, in my opinion."

Personally I dont want to lose any of my settings by reverting back to prior firmware.

I'd rather have GARMIN to test their Firmware update prior to releasing it !

This is classic development routine you may think.

Oh I absolutely agree with you; this is completely unacceptable for such an obvious bug that was immediately noticed by anyone that actually used it. I just want to be able to train with pace as soon as possible as I have a race coming up, and I'm getting impatient waiting for them to put out a solution!

Personally I dont want to lose any of my settings by reverting back to prior firmware.

I'd rather have GARMIN to test their Firmware update prior to releasing it !

This is classic development routine you may think.

Do you know if this rollback solution works with the FR230 as well as the 235? Is the firmware identical for both? Don't want to brick my watch if I just need to wait a couple of days for Garmin to get a fix out there.

I've changed the link, to 230 firmware

this is completely unacceptable for such an obvious bug that was immediately noticed by anyone that actually used it.

Don't presume to speak for or know the habits of all users. I don't have (current) Pace as a data field on any of my data screens when I run, and only the Lap Pace matters to me.

You only know how you use the watch, so please stick to that scope when you want to have a whinge, and convey your individual disappointment, thanks.

Well even if not every single individual user uses this field, surely you'd agree that if you're Garmin pushing out this firmware update, "Current Pace" is something important enough to be worthy of basic testing. My point is that this is one of the most commonly used features on the watch, and this malfunction would be readily apparent after any basic testing. It's not a bug buried deep in the features or menus.

Don't presume to speak for or know the habits of all users. I don't have (current) Pace as a data field on any of my data screens when I run, and only the Lap Pace matters to me.

You only know how you use the watch, so please stick to that scope when you want to have a whinge, and convey your individual disappointment, thanks.