This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

**Update Pulled** Marq - 8.76 Beta Release

Hello MARQ customers,

We apologize for the amount of issues you faced over the weekend. We have since removed 8.76 and have replaced every link below with 8.75 if you wish to backdate to the previous beta (or public release).

The newest MARQ beta software is now available for your upcoming adventures! The beta below is not compatible with MARQ Aviator.

MARQ: https://www8.garmin.com/support/download_details.jsp?id=15220

Instructions for installation are available below the change log on the page linked above.

8.76 Change Log Notes:

  • Added support for Grit and Flow metrics to cycling profiles.
  • Improved optical heart rate during hiking activities. (Requires 5.07 Sensor Hub)
  • Made several improvements to Indoor Climb.
  • Updated the UX layouts for steps, floors, stress, intensity minutes and pulse ox widgets.
  • Updated performance, training status, body battery, respiration and calories to use the new page indicators.
  • Made several other bug fixes and code improvements.

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

GPS: 4.30
Wi-Fi: 2.60
Sensor Hub: 5.07
ANT/BLE/BT: 5.04

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 MARQ Collection you have in the subject line.

  • Yes factory reset, the statement "We have since removed 8.76 and have replaced every link below with 8.75 if you wish to backdate to the previous beta (or public release)." should make it completely clear that it will factory reset the device.  If I was returning to 8.10 then I would completely expect the reset.

  • See my post in the Fenix 6 thread. It is expected in all kind of versions not just within the release ones. I know it's a pain in the .... but it is much better than put the watch in an inconsistent state with mixing all the old and new settings. That will cause problems sooner or later. But most probably sooner.

  • I've definitely had issues in the past (admittedly way back in Fenix 5 days) when restoring some of the settings files after downgrading software.  The older software clearly cannot 'read' the settings made by the newer software and that can cause stability problems.  I'd recommend doing a settings reset if you downgrade software, even if a settings reset wasn't forced.

    For those that are on 8.76 beta and haven't tried to downgrade, unless 8.76 is driving you nuts (I've not had any crashes in activity with it), then just stick with it for a few days and a shiny new beta will surely appear to sweep away your woes (without a settings reset).

  • There’s nothing of any consequence wrong with 8.76 that is impacting my usage. I’ve not had the issues with widgets crashing that others have reported. I don’t use Pulse Ox anyway and I can live with the two Training Status screens not displaying properly as the information is everywhere else. And I’m also seeing some of the best battery usage during activity that I can recall. So downgrading for me anyway is just not worth the time and effort required to set up the watch again from scratch.

  • We apologize for the confusion. However, step 7 of the installation instructions in the link above state: 

    NOTE: If you revert to an older version of software, all of your settings will be reset to defaults.

    This is a good 'lessons learned' for us to make sure we put this notice in a forum post in case we have to do this again in the future, although our goal is not to!

  • Same. Also love the fact the Garmin releases beta builds, could never get that from TAG Heuer on the connected.

  • Wouldn't it be better to rename 8.75 8.77 so that when we update we do not lose some of the data in our watches?

  • For the reasons explained, it’s not just a case of changing software numbers upward. There is a need to make sure that the newer software version can accept any settings created by 8.76. What you do not want is create new problems by not doing this. That’s why I’d say wait for a new beta software to come out if issues with 8.76 are just a minor irritation to you.

  • probably the better thing to do for the moment