Fenix 5S/5 - 9.71 Beta Release

Hello Fenix 5/5S users,

We have new beta software ready for your upcoming adventures!

Fenix 5S: https://www8.garmin.com/support/download_details.jsp?id=11661
Fenix 5: https://www8.garmin.com/support/download_details.jsp?id=11663

Note: Please allow for the updates to propagate across all servers. There is no need to post that the link does not work. It will after a bit of patience.

9.71 Change Log Notes: Please send all bug reports to [EMAIL="[email protected]"][email protected][/EMAIL], and indicate which model of the fenix 5 series you have in the subject line.
  • Added support for Connect IQ SDK v3.0.

Please note, the beta updates released on these forums are not suitable for APAC region devices.
  • Successfully installed 9.71 beta (coming from 9.2).

    1. After 9.71 beta update, GPS shows version: 4.40 (!)

    2. Went into system updates and then installed the GPS update - version shows: 0.00

    3. Reboot - GPS version shows 2.2

    Everything looks ok for now - will report back if I find something.
  • 1. 3rd party watch faces are laggy/slow, when switching to widgets (but was there before this beta).

    2. can i make any use out of Connect IQ v3.0 right now or do i have to wait for apps and/or the announced app store?
  • Former Member
    0 Former Member over 7 years ago
    1. 3rd party watch faces are laggy/slow, when switching to widgets (but was there before this beta).



    Yes it seems slower than before.
  • 2. can i make any use out of Connect IQ v3.0 right now or do i have to wait for apps and/or the announced app store?


    Apps should run fine. There was one change in permissions that was announced a few weeks back, and most developers were able to make that change already using CIQ 2.4.6. It had to do with getting the location for things like sunrise/sunset calculations. At this point, the SDK for 3.0. is in "beta3", and with beta SDKs, developers can't build for the app store yet. The bigger changes in CIQ3 have to do with music and maps, but neither apply for the f5/f5s, even when CIQ3 can be used with the app store.

    Here's the developer blog post about "what new" in CIQ3.0, so you can see what's going to be possible (based on the device), and there are some things only developers will see (like the new Byte Arrays)
    https://developer.garmin.com/index.php/blog/post/connect-iq-3.0.0-beta-now-available
  • jim_m_58, thank you for your explanation!

    with CIQ3.0 i was hoping that watch faces and widgets might have access to more data of the fenix to show and calculate them. at the moment the access to data seems to be quite limited for 3rd party apps/widgets/watch faces. i would like to see "sum up the (newly calculated) daily distance with the distance of other activities", "showing the training load and recovery time in a watch face" or "allowing apps like elliptical to write the distance into the real activity data (not only into the IQ data)".
  • Hi,

    I'd like to share my experience with 9.71 Beta (coming from 9.2).

    When checking Tree benchamrk:
    https://apps.garmin.com/en-US/apps/a...b-90f3b8fbecc8

    Performance went quite down from 1900~ points in 9.2 to 830 point in 9.74.
    https://imgur.com/a/ILb17A6

    Still experiencing big lags when using non standard watch faces.

    Today HR was way off - showing like 240 in the morning (I usually have around 50). I have never experienced such way off readings. It took few minutes to normalized, now seems to be working again.
  • Former Member
    0 Former Member over 7 years ago
    Hi,

    I'd like to share my experience with 9.71 Beta (coming from 9.2).

    When checking Tree benchamrk:
    https://apps.garmin.com/en-US/apps/a...b-90f3b8fbecc8

    Performance went quite down from 1900~ points in 9.2 to 830 point in 9.74.
    https://imgur.com/a/ILb17A6

    Still experiencing big lags when using non standard watch faces.

    Today HR was way off - showing like 240 in the morning (I usually have around 50). I have never experienced such way off readings. It took few minutes to normalized, now seems to be working again.


    Have you emailed the beta team? That's the best way to get their attention.

    If we're talking about lag with non-standard watchfaces, we need to mention which ones. For example, I tend to use very light watchfaces (Core, Sun Rings Pro) and I see very little lag - if the watchface is quite data intensive it will make a difference and then we'll be comparing apples with oranges,,,


    Plus with a beta, performance issues are probably going to be a given...!

    PS Garmin, your new anti-spam robot checker is a PITA!
  • Beta software usually has debug code in it that won’t be there in the production version which will affect performance to an extent. The slower the processor and the less the memory on board the more that performance hit will be noticeable.
  • I can confirm the benchmark result in the ~800 range which appears lower than normal.