Fenix 5X - 4.16 Beta Release

Hello Fenix 5X users,

We have new beta software ready for your upcoming adventures!

Please read the 'notes' and 'installation instructions' in the 'Updates and Downloads' page found in the link below. We look forward to your feedback.

Fenix 5X: http://www8.garmin.com/support/downl...s.jsp?id=11665 (Please note there is a 2.32 Display update available as well)

Please send all bug reports to [EMAIL="[email protected]"][email protected][/EMAIL], and indicate which model of the fēnix 5 series you have in the subject line.

Note: Please allow for the updates to propagate across all servers. There is no need to post that the link does not work. It will after a bit of patience.

4.16 Change Log Notes:

Fixed a potential issue where the data field page may have ghost lines when visiting the DogTracker page during an activity.
Fixed an issue where the gesture backlight was not working as expected during Do Not Disturb.
Improved the user experience and accuracy of the Round-trip Course feature.

0 Former Member over 8 years ago

Has anyone else experienced a significant drop in image quality of bitmap-based custom maps with 4.16?
Wondering whether it is a problem with my particular maps (following all Garmin guidelines) or a more generic problem introduced by the betas. After reverting back to production 4.10, the very same maps display correctly again.

0 Former Member over 8 years ago

You are right. Disaster.
The same map - April 2017 and today.

0 Volker over 8 years ago

That looks really strange/bad. Have you sent an email to the fw team? What map is it? Looks like a Birdseye select map?

0 Former Member over 8 years ago

Haven't sent any mail yet. Wanted to see, whether it just was with my particular custom maps. But GPS_Maniak seems to encounter the exact same problem. Is it OK to use your screenshots/photos in a mail to the team?

0 marksibert over 8 years ago

I have been dealing with an interesting firmware bug on my last several activities. (road running, trail running, weight lifting). At the end of the activity, i can see the elapsed time change as soon as I hit the stop button. It'll jump from the actual elapsed time, say 54:15 to something insane like 1102:45:23.

On my trail/road runs, i have it set to auto-lap every 1 mile. The split times look fine in the results - except for the last lap. the extra time goes on the last lap.

I noticed this after installing the 4.14 beta firmware. But I had 1 normal strength training workout (where the bug did not manifest) immediately after installing 4.14. After that, strength, running, and trail running activities have all shown the bug. Upgrading to 4.16 did not fix it.

Has anyone else seen this behavior? Is it a known bug?

0 Crispin_Ellisdon over 8 years ago

marksibert, Yes it is an issue across the Fenix 5 range on the 4.1x betas. I have also reported this and had confirmation back that it is a known issue they are investigating. It wouldn't hurt you also reporting it as this is the first time I've seen someone post this issue on the 5X.

0 tickerguy over 8 years ago

The missing "training status" and load magically reappeared after my run this morning.... so apparently, whatever it was, it may have been some glitch with Connect that fixed itself (or they fixed something on the back end.)

0 gfuentess over 8 years ago

I have been dealing with an interesting firmware bug on my last several activities. (road running, trail running, weight lifting). At the end of the activity, i can see the elapsed time change as soon as I hit the stop button. It'll jump from the actual elapsed time, say 54:15 to something insane like 1102:45:23.

On my trail/road runs, i have it set to auto-lap every 1 mile. The split times look fine in the results - except for the last lap. the extra time goes on the last lap.

I noticed this after installing the 4.14 beta firmware. But I had 1 normal strength training workout (where the bug did not manifest) immediately after installing 4.14. After that, strength, running, and trail running activities have all shown the bug. Upgrading to 4.16 did not fix it.

Has anyone else seen this behavior? Is it a known bug?

Same boat here. Reported this bug since early 4.14 days but I haven't been asked for more info from the beta team and yes, it's still there in 4.16.

0 NYanakiev7 over 8 years ago

Hmm nothing new for over two weeks. Hopefully the upcoming software update will be a biggie!

0 Dexter101010 over 8 years ago

I am start to thinking of the faith of fenix3 hr.I think here will be the same....