Fenix 5/5s Plus - 6.51 Beta Release

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.

I have had this happen in the past where the "auto calibrate" during an activity doesn't work. Do a hard reset like this (from Artivis):
Hard reset (for clearing problems with corrupted data, garmin logo loop, missing activities etc)
1. Power off the fenix 5 and wait for couple seconds
2. Press and release the Power button
3. Once the Garmin Logo appears Press and hold the Start and Back buttons.
4. When you hear the first beep (after couple seconds) let the Start (upper right) button go
5. When you hear the second beep (couple seconds after first beep) let the back (lower right) button go
6. The device will boot back up and you will be prompted to enter your profile information. You will have to reconfigure the watch, reload apps, watchfaces etc..

WARNING: It clears ALL user made settings, apps, watch faces, data fields, current activities, totals etc!

This worked for me about 5 months ago and I just noticed last week after the 6.0 update that my watch was doing this again. I did a hard reset and it is working correctly now.

Best

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.

Yea, I thought that may be the case. I remember waiting a long time on the original 5S. If that's the case, I might have to push for a refund under Australian Consumer Law given the power data is screwy and just get an Edge instead for now.

Ridiculous how Garmin keep introducing bugs like this. As someone who works in software development with a strong emphasis on QA, there's no real excuse -- especially with a company Garmin's size.

Updated my watch and works fine with Elite Misuro B+ (https://www.elite-it.com/en/products/accessories/sensors/misuro-b). No more power spikes! :-)

Getting the run around with Garmin support and their scripted responses. I provided a zip file of my device contents, they're wanting specifics on dates, etc of the issue -- if they looked at ANY of my FIT files they would see the power spikes. They also completely ignored me pointing them to the link showing it's an already known issue, and failed to answer when a fix will be available for APAC devices. Unbelievable. I think I'll just go for a refund at this point, as the device isn't fit for purpose.

I can confirm that the power spikes happen during firmware version 6.0, and I can confirm that they are gone since I use beta firmware 6.51 on my Fenix 5+.

Best regards
Christian

When will the new FW released? I am currently traveling on a long trip and cannot upload beta SW since I do not have access to a PC...
My hope is that the new FW will fix my current issues I am experiencing on my Fenix 5+. Whenever I arrive at a new timezone and set time with gps I have to reset my watch (a tmp file seems to prevent syncronization with my phone in those cases; I suspect something got corrupted that is only temporarily fixed with a full reset).
General comment: Garmin needs to enable FW updates etc with phones and tablets...or is there already a way that I am not aware of? Hints appreciated...
Thanks!

I was getting huge spikes connecting to my newly installed 2INpower running FW 6.00. So I upgraded to the 6.51 BETA. Prior to that, I was connecting to my 2014 KICKR with no spikes. But now after going to 6.51 I got 1 huge spike on the KICKR around the 1:06:40 mark. Activity is here: https://connect.garmin.com/modern/activity/3338711372. Got up to 3,893 W. Won't have my 2INpower until next week to retest. However, I haven't seen a KICKR spike until I upgraded to 6.51. Let me know if you need more information.

Is this firmware EVER going to be released? I don't like using a beta on my watch if possible. 17 December this shipped and we are still waiting...

I was told by Garmin support it was supposed to be released by end of January, but obviously it wasn't.

I was also told I could try the beta, even though support knew i had an APAC device..

The power bug is very frustrating. I'm also noticing my VO2Max is stuck on 45 and won't budge.

When I was training with the Fenix 5s (non-plus), it would go 48 - 53 depending where in my training plan I was.

Device is largely useless at this point.