Fenix 5/5s Plus - 6.51 Beta Release

My question is how the heck did we go from a 6.00 to 6.51 with only one bug fix?

The folder inside the .zip file says 5.58. So on average, this beta is version 6.045....

odsweng

Please add option to Watch System Menu to upgrade to Beta software, nobody wants to do it manually by copying files. Please note, that it is not possible to copy files to Watch USB drive on OS X without installing 3rd party software. Thank you in advance, kind regards from Czech Republic ;-)

This is a great idea that would make trying out Beta software much easier for those of us on OS X.

First of all: kudos to Garmin for pushing this out in a timely fashion - could've been a longer discussion regarding third party power meters etc.

To everybody who has already installed this: Is it safe? ;)

Just to add my confirmation that the power spike issues seem to be gone on this 6.51 beta. This Wattbike ride from a while back on 5.57 beta had a couple of monster spikes https://connect.garmin.com/modern/activity/3145500170. Whereas my (slightly pedestrian, after a heavy on barbell squats weights session yesterday) ride on the Wattbike today, with 6.51 beta, shows no odd spikes at all https://connect.garmin.com/modern/activity/3234744922 (before anyone asks, the 2 apparent ‘drop outs’ are where I had to briefly get off the bike to adjust the seat and the power went off on the Wattbike computer as the batteries are shot - the joys of using shared gym kit).

First of all, thank you Garmin for addressing this so quickly!

I installed this version yesterday and tried it out with Tacx Flow Smart trainer and the power spikes I had with firmware version 6.00 were gone. My F5 Plus was showing the same power readings as Zwift.

Gadence from Garmin sensor was also reporting correct readings to the watch during the exercise.
However, the speed was still mising and showing 0 km/h for almost the whole 50mim ride endig with only 0.25 km distance (Zwift reported 33 kmph avg speed).
This used to work for me with firmware 5.10 (Garmin showing some 5-10 km/h less than Zwift) so still not able to follow Garmin planned exercises with sections such as drive 16km that I used to.

Before the ride I also tried to calibrate the power just in case three times but it just gave me error code -1 every time. Maybe I try resetting to factory settings next.

Fw 6.0 is running really fine here, GPS tracks seems much precise and music BT connections are perfect, no losing or repairing issues, so no energies to try another fw....:o

How long would I have to expect to wait for an APAC version?

I just upgraded to the 5S Plus, and my first indoor bike workout (paired with a Tacx Neo) shows I burnt 5912 Calories, Avg Power of 1088w, Max Power of 62750W and NP of 1738 W :(

EDIT: on top of this, how are people working around the problem? It seems like the only thing I can do is delete the activities from GCM, then delete them from my device.. But, if I clean up the FIT files and add back in to Garmin Connect, they won't sync back across to my watch and fix up my recovery advisor etc, right?

New bug in 6.51 (?)

today i went for a trail run activity. All features worked like charm and battery consumption was great. After the 2h Trail Run Activity, I checked the metrics on Garmin Connect. The elevation graph was ok and the ascending/descending meters correct. The problem is on min/max elevation. The min -24m and the max 270m. These number are way off. I thing that the continuous auto calibration during activity, does not work properly. Have you guys experience something like that? When I went home the altimeter was showing -111. After a calibration, its showing correctly 25m.

How long would I have to expect to wait for an APAC version?

I just upgraded to the 5S Plus, and my first indoor bike workout (paired with a Tacx Neo) shows I burnt 5912 Calories, Avg Power of 1088w, Max Power of 62750W and NP of 1738 W :(

EDIT: on top of this, how are people working around the problem? It seems like the only thing I can do is delete the activities from GCM, then delete them from my device.. But, if I clean up the FIT files and add back in to Garmin Connect, they won't sync back across to my watch and fix up my recovery advisor etc, right?

As a fellow APAC sufferer - here is my calculation:

From first beta to release: about 4-6 weeks
From general release to APAC release : 2-4 weeks
Add some Christmas holidays (optional) - 1-2 weeks.

So APAC users will have to way probably between 6 (best case) weeks - to 12 weeks for the release.

So beta is from Dec 17th - So best case Jan 28th - worst case March 11th.

That is unless Garmin pull a fast one like with the Spotify release (5.x release) where it came pretty fast for APAC.