Related
Options

Fenix 6 Series - 5.77 Beta Release

Garmin_ODQA
over 4 years ago

Hello Fenix 6 customers,

Please ensure that you are downloading the correct beta software for your specific device.

Fenix 6s: https://www8.garmin.com/support/download_details.jsp?id=15166
Fenix 6s Pro: https://www8.garmin.com/support/download_details.jsp?id=15164
Fenix 6: https://www8.garmin.com/support/download_details.jsp?id=15162
Fenix 6 Pro: https://www8.garmin.com/support/download_details.jsp?id=15160
Fenix 6x Pro: https://www8.garmin.com/support/download_details.jsp?id=15168

Instructions for installation are available below the change log on each of the above pages.

5.77 Change Log Notes:

  • Fixed an issue where the device would crash when starting a POI search right after canceling an 'Around Me' search.
  • Fixed an issue where features that auto-enable during the sleep window were not working as expected. (For Ex: Battery Saver.)
  • Made some improvements to the DogTracker widget.
  • Made several other bug fixes and code improvements.

We have temporarily removed in-activity data field editing in this beta. We have identified a few bugs and while they are difficult to reproduce, we do not want our customers to experience these issues. When these bugs are resolved, this feature will be added back in to software.

Current beta peripheral software version numbers below. New versions are indicated in red.

GPS: 2.70
Sensor Hub: 4.20
ANT/BLE/BT (Pro models): 4.30
ANT/BLE (non-Pro models): 2.10
Wi-Fi (Pro models only): 2.60

Please note, the beta updates released on these forums are not suitable for APAC region devices.

Please send all bug reports to [email protected], and indicate which model of the Fenix 6 Series you have in the subject line.

  • +1 over 4 years ago in reply to Dr Phil

    It just makes no sense the OHR sits at 70-80 when cycling for 20 or so minutes and immediately jumps to 130-140 when starting any activity profile, without changing wrist placement or anything else. OHR on the Fenix is broken during all-day tracking, for a lot of users. Maybe the rest of the users just don’t care? I want my watch to be as accurate as it can be during the day, but right now (5.77 and sensor 4.20) it is (at least for me) still far too inaccurate to be acceptable. For activities I use a strap, so my focus is just in the outside activity tracking.

  • 0 over 4 years ago

    PLEASE WORK ON THE GARMIN CONNECT APP!!!

    Backcountry-Skiing activity opening will always crash, if not done with a Fenix 6!!! It is great, that it works with the Fenix 6, and nice, that you delivered us that aktivity type - but makes no sense, that the app won‘t accept any other file than that from this watch series...

  • 0 over 4 years ago in reply to Odie21

    Awesome thanks. I now have a usable maps feature

  • 0 over 4 years ago

    Has anyone used the new feature for calculating intensity minutes based on heart rate zones?

    I've configured mine to use zone 3 and 4. Yesterday I did my first run since the feature was released (been ill) and 16:30 in z3 and 7:52 in z4 but I only got 5+5 intensity minutes.
    https://connect.garmin.com/modern/activity/4450666479

    I guess that Garmin Connect still wants consecutive minutes for the intensity minutes to count but how many? From the manual "You can work toward achieving your weekly intensity minutes goal by participating in at least 10 consecutive minutes of moderate to vigorous intensity activities.". 

    In my opinion this is wrong, if I do a 46 minutes run and have 16:30 and 7:52 in z3 and z4 I want that as intensity minutes.

  • +1 over 4 years ago in reply to Loen82

    Also Stryd make assumptions but using it the distance for a lot of users is perfect. Algorithms can do miracles ;) 

  • 0 over 4 years ago

    The good things is: this fw fixes Bluetooth connectivity issues (could not connect) to my external HR sensors. The problem was with two last betas Thumbsup

    I got an opportunity to test OHR while swimming today. I was wearing Garmin Swim HRM so the data in the Garmin Connect is from the strap, but in the Endomondo I can see the data from the watch OHR... Was swimming for ~1 hour mixing breaststroke and backstroke. The data from the watch was quite close to the strap readings for backstroke. Difference is <5 bpm. So good job there! But the breaststroke... oh dear, readings from the watch are 15-20 bpm higher on average! So that data is totally useless.

  • 0 over 4 years ago in reply to Simone.01

    Uhm, what kind of assumptions? They are using 9 accellero meters and some rules of physics. 

  • +1 over 4 years ago

    For me with 5.77 beta and sensor hub 4.2 the heartrate is still not accurate when there is no activity started. The heartrate reacts very slow and only sometimes goes over 100 bpm.

    There is one bug when i was on an activity with a cheststrap and i stop the activity the heartrate WHR falls down to 70 bpm when my real heartrate is about 120 bpm. After that it never goes over 100 bpm. But when i was on an activity with WHR turned on and i stop the activity the WHR stays on top and the following minutes/hourd the heartrate seems to be accurate.

    This has to be fixed!

  • 0 over 4 years ago

    Im still having the ‘short GPS distance’ issue today after it manually somehow updated to 2.70 when I selected run. 

    I ran a measured 4.6 mile race, and the rest of the field that I see see their strava results all clocked 4.58-4.70. Mine clocked 4.28! Over quarter of a mile difference over just 4.6 miles is not acceptable!

    Yesterday using gps version 2.6 I did a 15.1 mile race and ran side by side with someone using the Fenix 5, they clocked the required 15.11, my Fenix 6 clocked short again at just 14.90 miles. 

    I know people will say there is a % tolerance to be expected, but in group runs and especially races, I’m the only one clocking short mileage on every run, and it simply isn’t good enough.  

  • 0 over 4 years ago in reply to BigRed-80

    Agree that GPS distance measuring too short is still an issue. Consistently 2-3% short on my runs. And sure there are expected tolerances but my other devices never had this issue.