Fenix 6 Series - 19.78 Public Beta

Hello Fenix 6 customers,

Our next beta version for the Fenix 6 series is now available! 

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

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

19.78 Change Log Notes:

  • Improved altitude calibration.
  • Fixed fonts used on the activity timer when the device is set to French.
  • Fixed intermittent issue that would cause device shutdown while saving an activity.
  • Fixed Tennis, Pickleball, and Padel outdoor activities to only prompt the user for altitude calibration when the device’s Altimeter Auto Calibration setting is set to Nightly.
  • Fixed issue with HIIT activities where the Workout Complete banner would continually be displayed after completing a HIIT timer workout.
  • Connect IQ improvements and bug fixes.
  • Other minor improvements and bug fixes.

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

GPS: 5.30
Sensor Hub: 11.01
ANT/BLE/BT (Pro models): 6.11
ANT/BLE (non-Pro models): 3.00
Wi-Fi (Pro models only): 2.60

Please note, the beta updates released on these forums are not compatible 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

  • Hey Garmin! Just ask Coros how the hell they have a rock-steady altimeter and elevation data field, even in a 199$ watch! It's not nuclear science! Don't say anything about OHR...

    I just sold my 750$ 6 Sapphire and get rid off all the beloved bugs... Ok handThumbsup

  • Watch is going back to garmin for a replacement.    Something weird happened in between the beta update not installing properly and express trying to do a sync.    Pretty happy with garmins response.    It's 2 years old and free refurbished replacement with another 12 month warranty.    

  • The music is probably disabled in the Power Manager's profile

    Thanks, yes, my bad.

  • Weird thing is I had the same but then did the same steps you outlined in the previous beta. I’ve switched off nightly calibration so it asks at the beginning of an activity. It’s behaving overnight and after the first nights weirdness is ok. 

  • Hi all, understand this thread is in the end mostly about altimeter, however... Just to understand if this is only relevant to Italian language:

    Also on non beta softwares since the time I own my Fenix 6s, possibility to answer messages (connected to android) is not working if in the name of the seller in the phonebook is present an emoji (likHearte if you have a contact named "Doughtier Heart" instead of just "daughter")

    I️s this happening also in other languages, and in case... Why is not addressed in the countless firmware revisions that the watch goes through?

    Thanks!

  • 19.20 is stable for me too, if you don't consider a low drift in altitude related to the barometer / altitude changes, which are difficult to identify clearly by the watch. But since the altitude is recalibrated at each activity, the value is almost always accurate, at +/- 10 meters.

    What I don't understand is the logic in this - so to speak - "improved" altimeter calibration process. Which value is the watch going to get to calibrate the altimeter at night ? DEM ? Location info from the phone ? What if the phone is off, or not connected ? Last known location ? How can this ever be accurate ? If someone has any clue on how this whole thing is suposed to work, maybe it would be easier to find the most relevant settings... Slight smile

  • What I don't understand is the logic in this - so to speak - "improved" altimeter calibration process. Which value is the watch going to get to calibrate the altimeter at night ? DEM ? Location info from the phone ? What if the phone is off, or not connected ? Last known location ? How can this ever be accurate ? If someone has any clue on how this whole thing is suposed to work, maybe it would be easier to find the most relevant settings

    Yeah I find myself  tending to agree with this as time goes on.

    I can understand the mindset of offering nightly calibration - if it is used for example if you're doing a multi-night activity and camping out in the wilds. But I think there's possibly too much to go wrong with making it a default. I think if anything, the "calibrate at activity" start makes sense... for me anyway, doing that the value is normally already pretty much spot on and I can sort of ignore it and skip it

  • Hi all, understand this thread is in the end mostly about altimeter, however... Just to understand if this is only relevant to Italian language:

    Also on non beta softwares since the time I own my Fenix 6s, possibility to answer messages (connected to android) is not working if in the name of the seller in the phonebook is present an emoj

    There was an older bug that stopped LiveTrack sending emails if your user name had an emoji in it, so there is a history of something similar. SO I wouldn't be surprised if this is the case.

  • I can't find where I got this info from, but I believe that nightly calibration uses either Wifi or a BT phone connection.

    It's probably be the watch issuing a request via BT or Wifi to retrieve the altitude for the location where the phone or wifi network is known to be. I guess that they don't yet have good enough handling for all possible error scenarios.

    Maybe they could make use of a fixed weather location if the user set that up. 

    I have it set up now as: Altimeter Auto Cal ON, Sensor mode Auto, and before each outdoor activity I do a calibrate using DEM or manually to a known altitude. Works as well as 19.20, except for the altimeter graph sometimes.

  • I’ve re-run through the steps I posted before so we’ll see how it behaves this evening. Such an odd one!