Fenix 5S/5 - 10.55 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.

10.55 Change Log Notes:
  • Fixed an occasional issue where the displayed lengths or distance during a pool swim could briefly show incorrect values.
  • GPS FW (2.24) should improve pace accuracy for running/walking activities and track performance for open water swimming activities.
Our public beta users are encouraged to load the new GPS firmware and use it for their next activities. If there are any activities where the GPS performance did not improve, we would like to see them. This also includes if comparing to previous activities. To send data to us for evaluation, please include the following in an email to [EMAIL="[email protected]"][email protected][/EMAIL]:
  • FIT file(s) from Garmin\Activity folder
    • FIT files from previous activities if comparing same routes

  • GarminDevice.XML from the Garmin folder
  • Subject line of email must use the following format: ‘Fenix 5 Series - GPS 2.24 Evaluation - DATE_ForumUserID_ActivityType’ (ex. "20180823_odsweng_Walk")
Following these instructions will ensure your email and files are delivered and sorted correctly. Lastly, you will not get an email reply unless we need more information from you, but rest assured, the data sent will be evaluated.

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
    10.55 and floor counting observations:

    It seems 10.55 is a lot more picky about not counting floors unless you are continually gaining elevation so that noise during pauses doesn't cause a problem.
    All my experience is with Post 10.00 beta versions.

    My driveway is about 1/4 mile long, and gains 105ft of elevation along the way (yes, winter is no fun). It really is a great test platform for floor counting. If I start at the bottom, and march my way up non-stop, I get 9-10 floors consistently with all versions on the Fenix 5 so far (except for the Vivo Active 3, which would count 3, but that is why I have a Fenix 5 now). If I take the dog with me, and she stops and sniffs things, it breaks up the pace. With her I get quite a few less floors counted, usually around 5. Before 10.55, having the dog with me made no difference. It appears the criteria for counting a floor and moving have gotten a little too stringent or touchy in my opinion in this release.

    My best guess is as follows: Any noise in the elevation that counts as a descent also resets the floor elevation increment. Example 10ft of climb + actively stepping are needed to count as a floor. If you pause for a moment, and the elevation reading declines in the slightest, the increment for a floor is reset. You could have been at 9ft, just about at a full floor, then you stop or slow, then noise in the reading resets the increment to 0ft and you loose the floor. So as changes have been made to give better immediate accuracy to elevation (allows more noise through), it has made the floor counting much more sensitive and less reliable on counting.

    I have also observed this on hikes when a climb levels for a bit, and then continues up, the floor counts are lower than before.

    I think this should be reviewed by Garmin, as it is not really a bug so much as it is a feature implementation issue. Personally I hate walking stairs (boring!), but I like setting a goal for elevation gain per day that only the floor counter reveals on these products that isn't within an activity.
  • Former Member
    0 Former Member over 6 years ago
    Feedback and question.

    On the GPS update to v2.24. Not sure if it tracks more accurately, but traces on map look better and difference compared to my bike computer has reduced a bit (20% better match). Need more sample data to be sure. What improved is the wait time to get reception (green GPS status).

    Question. Do anyone know/understand the 'new logic' behind the intensity minutes calculation?. E.g. today was the first day of the week. I did a bike ride of 1hr. 36' on HR zone 3 and 25' on zone 4. Reviewing the day stats, I've only achieved 36' of intensity minutes. It used to count double, but not sure when did this change or if this is a bug on the logic.

    Thanks in advance for any feedback!
  • Please take a look on this:

    Settings:
    Im using 10.55 os version, with gps 2.24 and my watch is f?nix 5 – Sapphire Edition. I've reseted this watch 4 times until now.
    Data recording mode is Every Second.

    Tracks:
    GPS https://connect.garmin.com/modern/activity/3017877387
    GLONASS https://connect.garmin.com/modern/activity/3017904298
    GALILEO https://connect.garmin.com/modern/activity/3017931882
    ULTRATRACK https://connect.garmin.com/modern/activity/3017961087

    Comment:
    One lap distance is about 6km. All activities displays wrong distance, but if you download gpx file and open it in external app - then distance becomes more accurate. What is strange - Ultratrack is the best one. On other gps modes signal was losted a lot of time.

    Any ideas?


    Very strange?
    Who would have thought " ultratrack " would have been the best GPS trace by far?!? :--)

  • Very strange?
    Who would have thought " ultratrack " would have been the best GPS trace by far?!? :--)

    None of those recordings are valid. Either speed sensor is faulty or the watch is faulty.
  • Former Member
    0 Former Member over 6 years ago
    None of those recordings are valid. Either speed sensor is faulty or the watch is faulty.


    I am assuming he has a separate speed sensor on the bike? It really is a redundant sensor with the GPS. The likely problem is the ANT+ connection is flaking out, and the Fenix is just not getting good data from the sensor to calculate speed, and therefore cannot calculate a good distance. Why the F5 uses that external sensor data for distance is a little confusing.

    IMHO the GPS on the watch should be used for speed/distance and disable the external sensor. If the GPS software is working properly, there should be no need to use the external speed sensor from the tires, the differences in distance should not be worth the trouble. Especially if the ANT+ connection is not reliable due to local interference (nearby cell phone for example).
  • For me battery life has hugely increased with 10.55 over 10, and I haven't noticed any accuracy issues with GPS+Galileo over GPS+GLONASS with 2.24.
  • Former Member
    0 Former Member over 6 years ago
    10.55 and floor counting observations:


    Yup, just confirmed that 10.55 has quite a bit of trouble accurately counting floors if there is a landing between flights. This seems to agree with my above observations. A small negative-going change in elevation resets the floor counter. Don't swing your arms!

    A continuous climb is fine.

  • At least I get an issue with this beta: I ran a course imported as gmx and left the course. When I was 1km off the fenix 5 rebooted without the connect IQ datafields (Stryd Power and Powerdahboard Plus from Joop). My run was recorded without the power after reboot. Stryd PowerCenter didnt import the run though.
  • I realize that the main discussion of this beta is in regards to the GPS, but can anyone confirm if "Race an Activity" is fixed in this beta? It was broken in the latest FW rollout and some of us users are hoping it might be fixed in this beta. tia