• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 4 subscribers
  • Views 2009 views
  • Users 0 members are here
Options
Related
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

MARQ - 5.63 Beta Release

Garmin_ODQA
over 4 years ago

Hello MARQ customers,

The newest MARQ beta software is now available for your upcoming adventures!

MARQ Adventurer: https://www8.garmin.com/support/download_details.jsp?id=15170
MARQ Athlete: https://www8.garmin.com/support/download_details.jsp?id=14864
MARQ Captain: https://www8.garmin.com/support/download_details.jsp?id=14868
MARQ Commander: https://www8.garmin.com/support/download_details.jsp?id=15182
MARQ Driver: https://www8.garmin.com/support/download_details.jsp?id=14870
MARQ Expedition: https://www8.garmin.com/support/download_details.jsp?id=14872

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


5.63 Change Log Notes:

  • Fixed an issue where the stress score could intermittently get stuck at 25.
  • Fixed an issue where the device will crash when trying to manually connect to an ANT sensor after enabling Airplane mode.
  • Fixed an issue where one would see a Wifi error message when launching the Golf activity.
  • Fixed an issue with golf maps drawing incorrectly after the last beta update.
  • Improved Indoor Bike OHR performance.
  • Brought in improvements for CIQ.
  • Brought in improvements and bug fixes for music.

Current beta peripheral software version numbers:

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

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.

  • 0 over 4 years ago

    For those of you who have encountered issues with Optical Heart Rate accuracy:

    As you can see from the change log notes, this version is only implementing fixes for indoor cycling. We have also been working on additional improvements for other use-cases, which should be available in the next few weeks.

    We’d love for this feature to be as accurate as possible. If you are still experiencing accuracy issues with Optical Heart Rate after installing this beta update, we would like to collect some information from you to investigate further. Please email the following details to [email protected]. Please note that we may not respond to your email unless we have further questions for you.

    • Please make the subject of the email: MARQ - HR Feedback - your first name
    • Under what circumstances did you encounter poor HR performance?
      • e. indoor cycling activity, all-day tracking, hiking, etc.
    • Please attach the following files to your email
      • The relevant activity .fit file, if the issue occurred during an activity
      • The GarminDevice.xml from the Garmin folder
      • The Settings.fit file from Garmin\Settings
      • All files in the Garmin\Monitor folder
      • Any pictures/screenshots/links to information in Garmin Connect that help explain the issue
    • Please also let us know if we have permission to access your Garmin Connect account. This will allow us to investigate your report faster, if we identify that other data is necessary for investigating. You do not have to grant us this permission, but doing so will allow us to be as thorough as possible in our investigation.

    Thanks,
    Mel
    Outdoor Software Quality Team

  • 0 over 4 years ago

    Does 0.63 incorporate the 0.62 updates as well?

  • 0 over 4 years ago in reply to 8937498

    Yes. In the beta software world the change log is from the last beta version and not the last production software version.

  • 0 over 4 years ago in reply to Garmin_ODQA

    I went for a hike today of 5+ miles and considering I overdid it so badly I puked when I got home - my heart rate wasn’t even close to that of reported. (I felt it hitting 170/180 at times and highest reported was 139 and that was like a few seconds)

    swimming and running works fine for me. Hit (CrossFit) and now hiking doesn’t ever go as high as it should. 

    I am running the latest stable, once there is more general fixes for heart rate in the upcoming beta I’ll take it a spin and report as instructed. 

    It’s strange that some work and others seem to have some algorithm that over compensate

    Best

    Thomas

  • 0 over 4 years ago

    Installed the 5.63 beta yesterday. Still need more time to verify if the stress level bug is gone. But got a new bug: The map screen do not update during activities. It stays static. It is only refreshed when changing data screens. I saw that the same bug was reported in the F6 forum for the 4.63 beta.

  • +1 over 4 years ago

    I believe I have stumbled upon another bug: After a logged training session, the watch stress widget stops recording stress history. It seems to store some data to Connect. Yesterday I got almost no useful data. Did restart the watch twice, and eventually (during the night) it recorded stress levels. But after removing the watch from the wrist, and doing my daily commute by bike to the office, there is no mor data recorded in the widget, although the continuous monitoring gives data. 

    I have reported this to the beta-team. And been asked to send data, which I have done. 

  • 0 over 4 years ago in reply to nyqand

    Yes ... I go exactly the same.

  • +1 over 4 years ago in reply to nyqand

    Same for me with 5.64 beta. Yesterday, I had to restart the device four times to get it working correctly again.