Fenix 5/5s Plus - 6.57 Beta Release

Hello Fenix 5/5s Plus users,

We have new beta software ready for your upcoming adventures!

Fenix 5S Plus: https://www8.garmin.com/support/down...s.jsp?id=14333
Fenix 5 Plus: https://www8.garmin.com/support/download_details.jsp?id=14331

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.

6.57 Change Log Notes:
  • Fixed several minor issues with music.

Please note, the beta updates released on these forums are not suitable for APAC region devices.

Please send all bug reports to [EMAIL="[email protected]"][email protected][/EMAIL], and indicate which model of the fenix 5 Plus series you have in the subject line.
  • Former Member
    0 Former Member over 6 years ago
    And still no firmware release for APAC devices fixing power spiking issues, rendering the device useless for those of us attempting to pair with a power meter.

    Support have now lied to me and tried to claim a firmware version for APAC devices was available to fix this issue, yet when pushed for a link, have not been able to provide one. Sadly it seems my only option at this point is to go straight to Fair Trading and seek a refund.

    Appalling behaviour from Garmin Support. All they do is lead you on.
  • Former Member
    0 Former Member over 6 years ago
    Well.. we all see from the updates in the past year, that Garmin is MAINLY trying to fix music bugs - which by the way we learned, they seem to never be able to fix.
    It get's more and more evident, that Garmin software developers are tinkerers instead of professionals.
    Same applies to management and support.
    A fish rots from the head down.
  • I don't give a **** about music bugfixes, I think that there are more important things to fix...
  • I don't give a **** about music bugfixes, I think that there are more important things to fix...


    Well.. we all see from the updates in the past year, that Garmin is MAINLY trying to fix music bugs - which by the way we learned, they seem to never be able to fix.
    It get's more and more evident, that Garmin software developers are tinkerers instead of professionals.
    Same applies to management and support.
    A fish rots from the head down.


    Given the current pace of beta updates (and the lack of a release to the stable channel) there are mulitple devs working on different branches. The music bug fixes you're likely seeing could be related to the complete device crashes that some users have had while running with music, btw, which is a pretty important thing to fix before a stable release.

    I am on the current stable, and I don't get any power spikes with my power meter, have never had a crash, etc. But those are real issues, and there are likely devs working on those branches separately. That's how agile development works, you don't have every dev working on the same thing. If the music fixes are quicker, then those devs are finishing, and submitting pull requests. The beta channel receives an update. Meanwhile other developers will work on bigger issues. It's possible that there have been sprints with internal alpha release updates that have attempted to address other underlying issues as well, but they don't get past QA and regression testing. Hence we see a branch with more minor updates.

    It is telling that the stable channel hasn't received an update in several sprint cycles. They're working on more stuff behind the scenes than what we're seeing.
  • Former Member
    0 Former Member over 6 years ago
    @reginalb Over a year without fixing/focusing/reacting to essential bugs that are absolutely no rocket science?... weak excuse...


  • No rocket science. Well Mr. Forerunner, if you're such a master programmer maybe you should offer your services to Garmin so we can all profit from your excellence :) :)
  • Former Member
    0 Former Member over 6 years ago
    No rocket science. Well Mr. Forerunner, if you're such a master programmer maybe you should offer your services to Garmin so we can all profit from your excellence :) :)


    Sure... just send me the sourcecode!
  • @reginalb Over a year without fixing/focusing/reacting to essential bugs that are absolutely no rocket science?... weak excuse...


    I think you're exaggerating the situation. There are definitely situations that cause crashes, but I promise you that they are edge cases. This is exemplified by the many users that have literally never experienced a crash (such as myself). Even the power spikes, I use a Powertap C1 power meter and have never seen a power spike. If you want a device with zero bugs, you need to get a simpler one. There have been Garmin devices that have lived in a perpetual state of Beta (I've owned a couple myself), but the Fenix 5 Plus seems pretty darn stable to me. If you're on a stable release, that is. I can't speak to the Beta channel. I use the Fenix as my reliable device of record, so I don't mess with the beta.
  • I don't give a **** about music bugfixes, I think that there are more important things to fix...


    well I definitely don't agree with that myself, this is one thing I care about them fixing since it is really buggy yet I use it a lot, I don't really have a problem with anything else, but each to their own