Software Version 8.00

I got a LTHR this morning in a run that always gives me LTHR readings: 5K with 75% above LTHR and 25% below.

I've been trying to log into this forum for almost 3 months, finally I've been able to!.

Feedback on F5s, firmw v8.0.

So far:

1. Floor count works more consistently compared to previous firmw versions. In v7.6 was almost useless.
2. GPS plot on GC seem to be the same. Some sporadic glitches that derive on speed peaks (cycling, speed 190 - 218 km/h!) -this also ocurred on v7.6 but not before-.
3. HR is a bit higher, but readings make more sense on excercise. Now I reach 170 sometimes when on previous firmwares was really rare to see values above 153.
4. Almost believe that battery drops 1% more per day -same daily charging routine and no 3rd party watch screens in use that would justify the difference-.
5. Repetitions count works, but it is too sensitive to exact repetition movement pattern. If one repetition if out of pattern, the general result is that the count stops. No way to fix but to restart the activity.

The rest, seems to be working as always.


Quick question, since I've not seen so far... is there any 'wish list of change requests' to Garmin?. Watch faces should allow to add HR average reading and/or Stress level to the configurable fields, even if it may not make much sense due the update every minute logic. When you work in an office, it would be fun to have it available.


Regards!

Here's another one for your entertainment. Remember the (mentioned by others too) issue of alert tones disappearing after FW 7.6? Well, I have had another experience of this kind now with FW 8 - I checked my settings on GC (windows), and saw that alert tones were set to "on". So nerd that I am, I set them to "during activity" - which is what the setting was supposed to be according to my watch settings, and how they actually worked up until Sunday morning (I changed the setting Sunday afternoon). On Monday I did not run, and today, lo and behold, the alert tones on my watch were gone again for my Tuesday morning run... So, I set the GC setting back to "on", synced my watch, and then manually set the watch setting back to "during activity". I'll update you, faithfully, on what my experience will be tomorrow. Just beats me, how such a simple setting can be messed up in this way in version 8 (!) of the firmware...

Has anybody actually got any sort of response from Garmin on the post version 8.0 issues? I raised a case via the website mid week last week and still have had no response to it. I assume that they must be aware that this code version has caused numerous issues.

I find that the quickest way to get a reply from any company's support these days is to nudge them on Facebook. Anyway, your best bet is to call them.

I was on the phone with them yesterday and got sort of confirmed there's some software issue with battery after the 8.0.0 upgrade, I have used the web updater to reinstall the software and did a reset but if I wear the watch in watch mode with no custom watch face the battery gets depleted with about 1% every five mins. If I leave the watch on the table the battery seems to be normal.

I'm not sure about the connection to FW 8 (which is now on my watch) specifically, but since FW 7.6 I have had three instances of the GPS taking absolute ages to lock on. The previous two instances, this was after I had changed locale, so I put it down to having to reacquire the satellites. But this time it was in a spot where I run every day and had run the two previous days. The sky was completely clear, and everything else was exactly the way it is every day. For some reason, the GPS took more than 3 minutes to lock on (in fact I started the run without GPS lock eventually, as I don't have the time to stand around in the cold for 10 minutes - and it took 1.5 KM for the GPS to lock on), when the usual is less than 20 seconds.
I have been using the watch in that exact same spot for the past six months, and this particular problem appeared the first time after FW 7.6.

I definitely experienced much slower GPS lock (1-2 minutes) with 7.60. It went back to normal (just a few seconds) when I installed 8.00.

Once you start moving, it is harder for the GPS to get an initial lock - 1.5 km is not surprising. Although as you say, it is hard to know which is the better choice when you are standing around in the cold waiting. :)

I typically update the watch with the Public Betas. They never seem to mess with customized data stored on the phone. It’s disappointing that this latest one can’t seem to manage the same. After the update last week I noticed that my HR max got reset on the watch and then apparently that info overwrote the info on Connect. Then today, I did a treadmill run for the first time since the update and clearly the calibration I had in place that was giving me very accurate readings previously was woefully off. I calibrated the run so we’ll see if it sticks. Also odd, was how bad the run was off. The first time I ever used the watch, the default calibration was off by about .1 miles per mile. This was closer to .3.

I’m a huge fan of Garmin, having had Vivosmart and Vivoactive previously, but the Fenix is the first one where it seems like every official update winds up jacking with data or existing features. I’m fine if an update’s new features may be glitchy initially, but I have to think that the developer team on the Fenix is different from their other teams and just aren’t dealing with quality control.

After the update to FW 8.0 my fenix 5 is frequently not recording the resting data.
More in detail HR data is not continuous and movement data are missing.
With previous FW only HR was some time discontinuous.
My watch is usually well fitted to my wrist
ciq.forums.garmin.com/.../1316486.jpg

Here's another one for your entertainment. Remember the (mentioned by others too) issue of alert tones disappearing after FW 7.6? Well, I have had another experience of this kind now with FW 8 - I checked my settings on GC (windows), and saw that alert tones were set to "on". So nerd that I am, I set them to "during activity" - which is what the setting was supposed to be according to my watch settings, and how they actually worked up until Sunday morning (I changed the setting Sunday afternoon). On Monday I did not run, and today, lo and behold, the alert tones on my watch were gone again for my Tuesday morning run... So, I set the GC setting back to "on", synced my watch, and then manually set the watch setting back to "during activity". I'll update you, faithfully, on what my experience will be tomorrow. Just beats me, how such a simple setting can be messed up in this way in version 8 (!) of the firmware...

Indeed, after the reset as per above - alert tones work again as advertised.

I have only one issue from update 8.0 i don't have LTHR ;-( yet

I think it is fair to ay that version 8.0.0 has been an absolute disaster of an update, and garmin really should be embarrased about it. I would even think they should be thinking about scrapping it and advising people to roll back.