Related
Options

Fenix 6 Series - 8.78 Beta Release

Garmin_ODQA
over 5 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.

8.78 Change Log Notes:

  • Brought in improvements for grit and flow.
  • Fixed an issue where the device could crash on the map page during an expedition activity.
  • Fixed an issue where the device would crash while powering down if battery saver was enabled.
  • Fixed an issue where the device could crash during the multisport activity creation wizard.

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

GPS: 4.30
Sensor Hub: 5.07
ANT/BLE/BT (Pro models): 5.04
ANT/BLE (non-Pro models): 2.11
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.

  • 0 over 5 years ago in reply to Crispin_Ellisdon

    Thanks Crispin, I'll try today a secondary master reset and make a full charge, so we will see tomorrow how it goes. :) 

  • 0 over 5 years ago in reply to Simone.01
    Simone.01 said:
    Very good! Is it walking or hiking activity? 

    The issue was that hiking was giving generally lower heart rate than walking. As you can see now, overall pretty good on this test. Spike at the end? No idea. Might have moved the watch on my wrist. Might be just a WHR artifact. Might be anything.

    Is it fixed? Don’t know but certainly better than it was.

  • 0 over 5 years ago in reply to Simone.01
    Simone.01 said:
    1) If you forget to disable it every time you start an activity the watch will broadcast HR and this is not good for battery life. 

    You might choose not to believe me but one of the two F6s I used for the Walk and Hike test was still broadcasting HR during the activity yet no apparent difference in energy consumption. 

  • 0 over 5 years ago in reply to NYanakiev7

    Same here. This morning it informed me that sensor hub was updated. I've checked manually and i see indeed 5.06.

    Does it make sense to update again from the beta files to 5.07? I mean, will it be updated again to 5.06 after some time due to synchronization via GCM? any thoughts/suggestions on this?

  • 0 over 5 years ago in reply to maglodilevente

    I'm running 8.78 on my 6X Pro Solar and just completed 75 minutes indoor cycling. I was comparing power data from my Neo 2 vs Assioma Duo pedals to see whether firmware 0.0.34 had closed the gap in power readings. Sensors connected as follows....

    6XPSo - Wahoo  TickR strap, Neo speed, Assioma power, Assioma cadence - Battery drain 0.92% per hour from FIT file

    5X+ - Wahoo TickR strap, Neo speed, Neo power, Neo cadence - Battery drain 0.80% per hour from FIT file

    Sensor hub was reverted to 5.06 from 5.07 before the ride by GCM. Grrrrr!

    I used battery monitoring apps on my 5X+ in the past and had the suspicion that they contributed to accelerated battery drain. I've not used once since. Battery life is generally great.

  • 0 over 5 years ago in reply to kona_221

    Makes sense but MTB profile didn't have Incident detection. Today i use the app cycling to do my mtb ride just becauseof this. I think is important Garmin allow to select incident detection on mtb.

  • 0 over 5 years ago in reply to Crispin_Ellisdon

    I just think you are not looking at this the right way, and neither did Garmin unless its a bug.  So, there are two methods to broadcast and lets say that are two uses for this. One use case are people that want to use the F6 to record and activity, use another device to record the same activity, while using the F6 as the HRM.  Great.  Now the second method that only want to use the "second" device to record the activity and use the F6 as the HRM.  Firstly, both use cases are running an activity so in both cases the HRM needs to be accurate, period, done.  Why would Garmin, want to, by choice provide you with two options (described above) but give you worse data on one of the choices.  If they want to force one option over the other than they should have only provided that option.  To give a broadcast option that sucks in terms of accuracy doesn't help anyone.  

  • 0 over 5 years ago in reply to Crispin_Ellisdon

    Firstly how do you guys paste portions of answers from others into your reply (it seems more than just copy/paste) but in response to Crispin regarding why I wouldn't want to broadcast HR in activity.

    1.  As stated above, you can easily forget to turn it off.  Also you have to go to settings and mess with this in the beginning and at the end of activity.

    2.  Need to remember to discard activity on the F6

    3.  Wasting battery on the F6 unless you set a special activity that doesn't use GPS, etc

    4. When I broadcast (not in activity) I want to use the watch as an HRM much like you use your strap. I am using it as an HRM instead of a strap and the device I am broadcasting to has all the data I need.  That is how this is meant to work, the watch becomes your "HRM Strap" and I have no need to use it for anything else.  And when I am done, I just press STOP on the watch. I dont need to remember to go to settings and change them again.

  • 0 over 5 years ago in reply to avikoren1
    avikoren1 said:
    Firstly how do you guys paste portions of answers

    Select text you want to quote, quote button appears. Click on the Quote button:

  • 0 over 5 years ago in reply to avikoren1

    [Looks like , has answered your query about quotes.]

    avikoren1 said:
    I just think you are not looking at this the right way,

    You perhaps missed the bit (see below) where I said in an earlier reply that I actually agreed with your view that the not-in-activity HR broadcast should use the 'higher power' WHR mode.  I do not believe it's a bug (it behaves as it was designed to, whether we like it or not), but I also agree that in an ideal world the standard/plain/not-in-activity broadcast HR would use the 'higher power' activity mode WHR rather than the 'lower power' 24/7 mode.  Whilst that is just our view and makes sense to us, I suspect that we might find someone complain if it were changed to the high power activity WHR, as they prefer that it consumes as little power as possible. So you and I might be happier with the change, but you'll be amazed how many people get upset when little things like this are changed (I suspect for Garmin this falls into the category of "you can please some of the people some of the time, but you can't please all of the people all of the time...", so I imagine they probably won't change it).

    Crispin_Ellisdon said:
    avikoren1 said:
    It seems to me that when you BROADCAST it implies an activity is being recorded and they should provide the best accuracy they can.

    I’m inclined to agree with this statement

    All that said, for the reasons I have explained, I simply find broadcast HR in-activity soooo much more useful than the basic out of activity broadcast HR.  So much so, that the only time I use the basic broadcast HR is out of curiosity when someone complains on the forums how it works Wink