Fenix 5S/5 - 9.73 Beta Release

Hello Fenix 5/5S users,

We have new beta software ready for your upcoming adventures!

Fenix 5S: https://www8.garmin.com/support/down...s.jsp?id=11661
Fenix 5: https://www8.garmin.com/support/down...s.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.73 Change Log Notes:
  • Added canned text reply support (Android only).
  • Added additional Connect IQ 3.0 features.
  • Fixed an issue that could cause elevation graphs to be smoothed and total ascent and descent values to be inaccurate.
  • Fixed an issue that could prevent sensors connected over BLE from reporting data.
  • Fixed an issue causing HR data for pool swim activities to be graphed incorrectly in Garmin Connect.

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.

Please note, the beta updates released on these forums are not suitable for APAC region devices.
  • Former Member
    0 Former Member over 6 years ago
    Anyone else is noticing better GPS+Galileo tracks? The first run after the beta update was really spot on!:eek:
  • 3/4 times I connect F5 to my Mac it restarts - just reporting
  • Anyone else is noticing better GPS+Galileo tracks? The first run after the beta update was really spot on!:eek:


    I had a great track over the weekend with GPS+Galileo on this beta software. I'm being cautiously optimistic.
  • Former Member
    0 Former Member over 6 years ago
    • Fixed an issue causing HR data for pool swim activities to be graphed incorrectly in Garmin Connect.



    Hello there, I still cannot see HR data at all in swimming activities... Is there something hidden to activate somewhere ?
  • Hello there, I still cannot see HR data at all in swimming activities... Is there something hidden to activate somewhere ?


    Do you use an external HR? The wrist HR is disabled while swimming.
  • Former Member
    0 Former Member over 6 years ago
    Do you use an external HR? The wrist HR is disabled while swimming.


    No, I don't. I saw in the manual that wrist HR is disabled (recording) during swimming activities, but that's unfortunate as the HR widget works pretty fine for me in the water (results consistent with activity). I was hoping this limitation was no longer an issue when I saw this :

    Fixed an issue causing HR data for pool swim activities to be graphed incorrectly in Garmin Connect


    I still dont understand why the choice is not left to the customer to enable or not wrist HR recording for swimming activities. Even an rough estimate of HR is better than nothing.

    The apple watch, which is using quite the same HR sensor does record HR for swimming activities, So I was hoping Garmin would one day add this very much needed feature which should have been there starting from day one on such a premium product as the Fenix 5.
  • Wrist HR + Swimming Activity: it would be great because it works very good (I´ve tested it with other activities, but then laps are not counted)!
    I asked several times for this. But they do not seem to care.
    Everyone who is missing it: please contact Garmin-Support!!!
  • Hi.

    I'm the developer of the widget "Weekly Activity". As AJRykala previously posted, the widget uses the hashCode() function to generate a hash key to be able to access to special features of the widget. The hashCode() is applied on the unique identifier of the device, which is obtained calling Toybox.System.getDeviceSettings().uniqueIdentifier

    The main problem is that the hashCode() function in 9.73 beta firmware returns different values for the same input string depending on the device where this function is called, and these values are different from the ones that are obtained in the Garmin simulator. This it's not happening in other firmware versions neither in other devices. I get the same values in my Fenix 3 as in the Garmin simulator.

    Thanks to AJRykala's help I've seen that, for example:

    94ee97321e81ef7555f83ec693f815acd01ff54e”.hashCode() returns -1579362389 in the Garmin simulator
    94ee97321e81ef7555f83ec693f815acd01ff54e”.hashCode() returns -1445144661 in AJRykala's F5 with 9.73 beta

    Other users with FR935 devices and 9.73 firmware are facing the same problem with the registration based on this hashCode.

    The hashCode() should return the same value for the same input. It's not a random function. I decided to use the Garmin function instead of implementing my own hash function for obvious reasons (a firmware function is probably faster, and the final size of the code of the Apps is smaller).

    I hope this helps Garmin to fix the hashCode() function in this beta firmware.

  • I hope this helps Garmin to fix the hashCode() function in this beta firmware.


    Yes, you are noticing a change to the String.hashCode() function that was made in ConnectIQ 3.0. The result of this change is that hash values for long strings may be different from what you would have seen with previous versions of ConnectIQ.

    That said, it is not our expectation that the result of a call to hashCode() be persisted in any way. We internally depend on hashCode() returning equal hash values for objects that are equal (for all primitive types and for any class type that provides its own implementations of equals and hashCode()) during a single run of an application. This allows us to insert and search for objects in a Lang.Dictionary.

    Travis