This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fenix 5S/5 Plus - 4.64 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/down...s.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.

4.64 Change Log Notes:
  • Fixed an issue where the device could crash while using Garmin Pay.
  • Fixed an intermittent issue where the display length during a pool swim could show invalid values.
  • Made several bug fixes for the music player.

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.
  • I am not sure if it was an issue before GPS GW 2.23, but I see in menu -> About "EPO: expired". Does anybody else have this? EPO is some type of A-GPS from Mediatek.
  • That's exactly what I did. I only replaced the GPS FW by putting the corresponding file to the remotesw folder.
    I did it last Saturday because I didn't want to risk my participation in a trail-race :-) Anyway I was tempted by the reports of better accuracy.

    The race went well, I did not encounter an issue with the GPS FW update. The track itself still shows the same multipath-issues as with 2.2 (resulting in track offsets).
    I can't say much about pace because I use a Stryd. Distance was - a bit surprisingly - the same as from Stryd. Other people with Garmins got their usual short-cutting by about 2-4%


    how can i replace only the gps file on version 4.20??
  • I imagine it is like this:

    - They have a live "reported bugs list"
    - They regularly analyse and determine how deep the reported bug may be in the code and estimate time & resources needed to fix it
    - Assign/plan for which bugs to be included in upcoming fw update schedule
    - assign resources to fix the bugs according to this schedule and monitor/manage

    The things fixed in this fw update were probably decided a "long" time ago. So when someone here reports a fire, I don't think they stop all current tasks to concentrate all efforts to put out that particular fire, no matter how loud it is discussed in this forum.
    I don't think the beta team read this forum. At best the moderator reports it and it is added to the bug list without assigning "level of noise or urgency" based on how much we express our frustration here.

    They may also put in easy fixes while they are still working on the more challenging bugs. What would you prefer? Longer time between updates to get the major fixes and letting the smaller bugs continue?

    As others have pointed out, report your case to the beta team directly.
  • how can i replace only the gps file on version 4.20??


    Please allow me to send you to this thread: https://forums.garmin.com/forum/into-sports/running/forerunner-935-aa/1393215-new-gps-2-23-for-phoenix-5x
    They did it even more exotic: they use the 5plus GPS firmware in their 935 ;-) Anyway there is also a short description which file you have to put on the watch.
  • <cut> Longer time between updates to get the major fixes and letting the smaller bugs continue?


    that's a reasonable and well explained way to fix quite everything in IT except in a small detail: bugs that are blocking a "core" activity (e.g. open water swim in a triathlon-focused watch, at the moment useless in 935, broken 2 months ago in an official release, not in a beta...) and made useless an $500 watch MUST go quickly as up as possible in the to-do-list, IMHO. it's frustrating. i have my old reliable 920xt at hand, but a lot of triathletes must train with an useless watch at the moment.


  • Former Member
    0 Former Member over 6 years ago
    I imagine it is like this:

    - They have a live "reported bugs list"
    - They regularly analyse and determine how deep the reported bug may be in the code and estimate time & resources needed to fix it
    - Assign/plan for which bugs to be included in upcoming fw update schedule
    - assign resources to fix the bugs according to this schedule and monitor/manage

    The things fixed in this fw update were probably decided a "long" time ago. So when someone here reports a fire, I don't think they stop all current tasks to concentrate all efforts to put out that particular fire, no matter how loud it is discussed in this forum.
    I don't think the beta team read this forum. At best the moderator reports it and it is added to the bug list without assigning "level of noise or urgency" based on how much we express our frustration here.

    They may also put in easy fixes while they are still working on the more challenging bugs. What would you prefer? Longer time between updates to get the major fixes and letting the smaller bugs continue?

    As others have pointed out, report your case to the beta team directly.


    If that was true, then the situation is even worse than feared!!!
  • When I go into Music/Albums I don’t see my MP3 folders anymore. The watch has made albums using the info that are included into the MP3 files...is this a new feature or a bug?
  • And guys....Garmin has the fastest update system. I have the F5+ Ti for almost a month and in the meantime I have got 4-5 beta updates and 2 finals. Other brands do updates every 3 or 6 months and users are living with bugs for much more time. Garmin launched the beta program with F3 and since then they do a great work. Fenix series are the most complicated sports watches in the market and this is the compromise. Polar and Suunto are much more simple. If you want a more simple watch you can get one. Personally, I don’t pay this amount of money for simplicity.
  • And guys....Garmin has the fastest update system. I have the F5+ Ti for almost a month and in the meantime I have got 4-5 beta updates and 2 finals. Other brands do updates every 3 or 6 months and users are living with bugs for much more time. Garmin launched the beta program with F3 and since then they do a great work. Fenix series are the most complicated sports watches in the market and this is the compromise. Polar and Suunto are much more simple. If you want a more simple watch you can get one. Personally, I don’t pay this amount of money for simplicity.


    haha, who gives a damn about a "fast update system", if core functions stop working and the software is messed up more and more with every single update!?

    OWS stopped working after an update, altimeter stopped working after an update, different things in GC mobile stopped working after an update and many, many more.
    i could understand if there is an update and something was messed up because it was overseen before release. but this has to get fixed with a very quick bug fix release. but here we are talking about multiple functions, which are broken for months now.

    i am waiting for the next official firmware. if major things are not fixed by then, garmin will get back my fenix and i am done with them.
  • Former Member
    0 Former Member over 6 years ago
    haha, who gives a damn about a "fast update system", if core functions stop working and the software is messed up more and more with every single update!?

    OWS stopped working after an update, altimeter stopped working after an update, different things in GC mobile stopped working after an update and many, many more.
    i could understand if there is an update and something was messed up because it was overseen before release. but this has to get fixed with a very quick bug fix release. but here we are talking about multiple functions, which are broken for months now.

    i am waiting for the next official firmware. if major things are not fixed by then, garmin will get back my fenix and i am done with them.


    I think so too.
    Update rate has nothing to do with software quality or focusing on important things.
    The longer this Garmin drama is going on , the more i get the impression that Garmin could have lost core-software/algorithm developers und has no clue how to fix essential bugs.
    (Maybe the developers went over to Polar for the Vantage V? ;) )