Fenix 5S/5 - 9.10 Public Release Candidate

Hello Fenix 5S/5 users,

We have new beta software ready for your upcoming adventures!

Fenix 5S: http://www8.garmin.com/support/downl...s.jsp?id=11661
Fenix 5: http://www8.garmin.com/support/downl...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.10 Change Log Notes:
  • Version bump System SW to 9.10. *Please be patient as this update may take longer to install than previous versions*
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.
  • Either way i sent an email to the beta team asking them to confirm. With luck they will fix it. Once I understood where you were seeing this, it was reasonably easy to see the issue.
  • Former Member
    0 Former Member over 7 years ago
    Unfortunately this is the price we pay for using the beta. There will be bugs, and not all will be quashed in the next beta. We test so we can report to the beta feedback programme (e.g. the VO2 max bug I had) and help quash them. If it’s an issue, your best bet is to stick to final release versions. Being on the cutting edge means we sometimes get cut by the sharp edges :)
  • the floor counter stopped working for me with fw 9.10. since the update yesterday not a single floor climbed was counted. this morning i climbed 12 floors - on the fenix i get 0 (this happens the first time).
    i know that the floor counter is more of a gimmick than something useful/reliable, but before at least about 50% to 60% of the floors were counted.


    nmyeti, thank you for reporting this problem. i would assume, that the dev team reads this forum/thread and i already reported about this problem in the 9.02 thread.


    AJRykala, you are totally right. i am a developer myself and i know that bugs can happen - even in an official release. but i am really annoyed how the garmin devs are working. they do not seem to even test what they are coding. there are simple ways to test things after changes. i am not working at garmin, but after i download a new firmware or ios app update it takes me less than a few minutes to find serious bugs. i think that the gamin devs could do this as well.
    they add more and more features (which is nice) but do not fix know bugs and issues - they even add new bugs. and they are slooooow. if one of our customers reports a bug, we fix it the same day and release the fix - mostly within hours. for us fixing bugs is priority number one - nothing is worse than knowing about bugs and not fixing them. what keeps garmin from releasing several betas a day? they should look into a bug, fix it and release a new beta - this is better than leaving customers alone with their known bugs.
    and they should release a changelog where they list every bug fixed or change made - not just write stupid things like "version number bumped" (e. g. "number of bugs bumped")...



  • Guys, can someone please check if you can set Auto-lap function for pool swimming activity in 9.10 beta? I seem to have lost this feature after the update. Open water swim is still ok, but pool swim - nope.
  • Guys, can someone please check if you can set Auto-lap function for pool swimming activity in 9.10 beta? I seem to have lost this feature after the update. Open water swim is still ok, but pool swim - nope.


    Same for me. But I am not sure ; Auto-lap function was there in last version.
  • Former Member
    0 Former Member over 7 years ago
    AJRykala, you are totally right. i am a developer myself and i know that bugs can happen - even in an official release. but i am really annoyed how the garmin devs are working. they do not seem to even test what they are coding. there are simple ways to test things after changes. i am not working at garmin, but after i download a new firmware or ios app update it takes me less than a few minutes to find serious bugs. i think that the gamin devs could do this as well.
    they add more and more features (which is nice) but do not fix know bugs and issues - they even add new bugs. and they are slooooow. if one of our customers reports a bug, we fix it the same day and release the fix - mostly within hours. for us fixing bugs is priority number one - nothing is worse than knowing about bugs and not fixing them. what keeps garmin from releasing several betas a day? they should look into a bug, fix it and release a new beta - this is better than leaving customers alone with their known bugs.
    and they should release a changelog where they list every bug fixed or change made - not just write stupid things like "version number bumped" (e. g. "number of bugs bumped")...






    With this new tune up feature, there's going to be problems. Factor in millions of users and multiple devices, and thats a developer nightmare. Now add in the ability for multiple devices to share data and - well I;m glad I'm not a Garmin dev!!!

    With Beta's there are always going to be bugs found fresh because (what is it they say...) "many eyes make bugs shallow"

    I don't think you'll find any large developer able to release multiple beta's a day - Apple don't, MS don't - it muddies the water when it comes to things like multiple device interactions. When the number of users and devices reaches a certain scale a over-zealous beta release schedule is often counter productive. They'll get the reports, prioritise the important ones and schedule those for the final.

    Changelog - yeah I agree with you there
  • \


    nmyeti, thank you for reporting this problem. i would assume, that the dev team reads this forum/thread and i already reported about this problem in the 9.02 thread.




    That may not be the case. The beta instructions clearly state that issues should be sent to the beta team email address. James from the beta team sent me an email overnight. I've asked for permission to share some of his response.

    If you guys have issues, emailing them to the beta team address in the first post is always the best option.
  • Former Member
    0 Former Member over 7 years ago
    That may not be the case. The beta instructions clearly state that issues should be sent to the beta team email address. James from the beta team sent me an email overnight. I've asked for permission to share some of his response.

    If you guys have issues, emailing them to the beta team address in the first post is always the best option.


    Yep. Go straight to the source (pardon the pun lol!)
  • I got permission from James to share what he reported to me about the total distance field

    "Hello Nathan,
    Thank you for emailing us on this subject. This is by design. There were substantial requests asking that non-step related activities not be counted when it comes to distance. A change was made in the software of the device which is why you are seeing these results.

    I am now seeing requests through emails asking this change be reversed. Reversing this change is highly unlikely, but talks are going on to give fenix users options when it comes to recorded distance.

    I hope this answers your questions.

    Thank you
    James"
  • nmyeti, exactly this kind of answer and behavior really makes me angry. as james wrote, this is a substantial change in showing data and results.

    so if you make substantial changes:

    1.) you let the users know about it and explain the reason for this change.

    2.) if users moaned about something and you feel, that the moaning people may be right... you take into account, that all the other people, who did not moan and like this feature for years, like it the way it is. so you keep it as it is and offer an option to change the default behavior.

    3.) you can add another "distance unit": distance by foot and total distance.

    in my opinion DISTANCE IS DISTANCE - no matter how you gained this distance. why the heck should the distance of steps walked or runned be more interesting or important than the distance taken with a bike, crosstrainer or whatever? this is plain stupid and makes no sense.
    i could understand, if they would differ between "total distance walked/steps" and "tatal distance activities". but not adding the distance on a bike, trainer or whatever makes the fenix a runners/walkers watch.
    and by the way: this is a tiny, tiny "if" "else" thing to code which takes less than a minute.


    an example for the same kind of **** answer:

    - one of the latest ios version of garmin connect had a bug. you could not sort the apps (or widgets) anymore in the app.

    - someone asked in the forum why this does not work anymore. a garmin employee aswered, that there is no problem with the ios version and that sorting should work.

    - i told the employee that it does not work in the ios version.

    - he said "oh" and reported it to the devs. after that he wrote, that this is meant to be like that, because you can sort the apps/widgets on the watch. really??? a comfortable and working feature beeing removed because one can sort about 40 apps on the watch??? happy sorting!!!!

    - the next update brought back the sorting feature... of course untested and totally buggy (which it is still).