Fenix 5S/5 Plus - 4.64 Beta Release

Elevation graph in navigation activity is still wrong, i report my previous reporting :

I have noticed that elevation profile page in activity navigation using car, motorcycle or pedestrian routing (not direct routing, even if start altitude is however different from what i see on altimeter widget) is totally wrong, sometimes starts to different elevation from where i start, sometimes the graph is totally no sense: for example if i start from 107m asl and destination is at 257m, the graph is this:

" />">


I don't understand why at some point the graph start to go down if the destination is at 257m asl and i don't understand also why if i'm starting from 107m the graph report 110m, but sometimes also 120m, 130m.... it gives me random numbers...

Sometime, instead the graph result different but i don't know why since i start navigation from the same point and i set destination to the same point; notice that this time it started from 111m even if my altimeter report 107m, maybe routing uses DEM data, i don't know; i do this only a couple of minute later...

" />">

I also noticed that sometimes navigation activity crash when the first text text appear (for example turn right at 150m).

I have noticed that elevation profile page in activity navigation using car, motorcycle or pedestrian routing (not direct routing, even if start altitude is however different from what i see on altimeter widget) is totally wrong, sometimes starts to different elevation from where i start, sometimes the graph is totally no sense: for example if i start from 107m asl and destination is at 257m, the graph is this:

" />">

I don't understand why at some point the graph start to go down if the destination is at 257m asl and i don't understand also why if i'm starting from 107m the graph report 110m, but sometimes also 120m, 130m.... it gives me random numbers...

Sometime, instead the graph result different but i don't know why since i start navigation from the same point and i set destination to the same point; notice that this time it started from 111m even if my altimeter report 107m, maybe routing uses DEM data, i don't know; i do this only a couple of minute later...

" />">

I noticed also that navigation activity crashes when first indicationa ppears (like turn right at 150m)

Can confirm Garmin Pay crash is fixed here and Music is working fine for the moment (in 4.61 was "random" bug for me).

Not so relevant but would be nice to have acces via Hotkeys to Garmin Pay :)

Thank you,

Bugfixes in the music player?!?!? Häääää????
WTF!
Garmin managers and developers are you living in an idiot parallel universe?
No bugfix to all of these essential sports features issues again!
Just another disappointment and bad experience with Garmin!
What an ignorant and customer ignoring company!!!
This watch makes me sick!
Hope Polar will do better so i can finish this ugly experience with garmin watches!
I think i‘ll do another youtube review video warning potential customers of this incredible mess.

Any chance that Garmin will fix all that sensor connectivity mess while the watch is connected to the phone? I thought this was primarily a sports watch and not a music player or wallet.
Garmin, seriously...

If you are complaining about "this thing" or "that thing" that isn't fixed then I would hope you are also getting involved with the beta programme and emailing the [email][email protected][/email] address to note your issues.

I'm not saying this to be snarky or to try and defend Garmin , but the reality is the Fenix 5 series covers a lot different use cases for a lot of different customers, and the issues you are experiencing may only be a problem for only a small number of users. That makes it extremely difficult for Garmin to figure out what is causing the issue unless you get involved, and can make it hard for them to size up how many other users are having the same issue.

I've always found the people who manage the beta channel to be quite helpful.

They should be working on fixing the useless battery fuel gauge and issues like post activity battery drain instead of making less important improvements to music player functionality, initially at least. This is first and foremost a sport watch and if the core functionality does not live up to expected standards there will be lots of disappointed customers.

I already have a ticket open regarding battery drain and many other people have also forwarded their information to support, as a result the fenix beta team should already be aware of the issue.

I do appreciate the improvements they make, however they should prioritize things more effectively.

Does anyone know if it is possible to ONLY replace the GPS update file?
I'm one 4.20 (after beinng on beta's before) and i'm only interested in the update made in the 4.61 beta (also included in this one)

The attached GPS FW (2.23) should improve pace accuracy for running/walking activities and track performance for open water swimming activities.

At the moment i'm not interested in the other changes the beta's may bring.

Bugfixes in the music player?!?!? Häääää????
WTF!
Garmin managers and developers are you living in an idiot parallel universe?
No bugfix to all of these essential sports features issues again!
Just another disappointment and bad experience with Garmin!
What an ignorant and customer ignoring company!!!
This watch makes me sick!
Hope Polar will do better so i can finish this ugly experience with garmin watches!
I think i‘ll do another youtube review video warning potential customers of this incredible mess.

Yes i don't know why they continue to fix these useless things and don't focus on the main features! All this remember me the "improve dog track" feature for Fenix 3!

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%