Fenix 5X - 8.54 Public Beta

It seems this will be the last firmware these dudes are releasing, 2 months and some of this worthless garbage firmware (stable) and 6 weeks and counting for the beta (worst ever, most likely Alpha) This company still havent apologies for such a brownie.
The watch works properly in giving the time, I thought this watch was for much more, so many bugs.

It seems this will be the last firmware these dudes are releasing, 2 months and some of this worthless garbage firmware (stable) and 6 weeks and counting for the beta (worst ever, most likely Alpha) This company still havent apologies for such a brownie.
The watch works properly in giving the time, I thought this watch was for much more, so many bugs.

How do you know that this is the latest firmware
Where do you get this wisdom from?
It look like you are a little frustrated haha

A bit of thoughts on a few posts I've read lately.
The Beta Team is not supposed to answer to the E-Mail reports but they DO when the report is soundly written, accompanied by data in the form of logfile, pictures and videos. Writing a report is a complex thing because one thing is when you spot a bug and another is when you spot it can replicate it and propose alternate solutions. The Betas DO answer when they need more data or clarifications, however, keep in mind they already grab the data via Garmin Express and, in a few remarkable cases, they intervene directly on the watch via wireless connection (if you don't have the proper software you will never notice).

I don't need to remark upon the insane choices that the company took with the Fenix5 model because the results are apparent to whomever reads the forums and the FB groups but I've seen several reports on FB and directed the users straight to the Beta DEVs' email. They confirmed they answered to their reports on the following day (and posted the answer right away).
Also keep in mind that every beta needs weeks to stabylize, that we are not given the benefit of a bugpost and can only assume it's the internal QA team that takes care of the stuff we send... which explains why they don't need to answer.

With the HW faults, the damage control policy (explanations for problems they are NOT allowed to give you) and 90% of the open beta members having no idea on what the watch is supposed to do and why it acts in a certain manner, I assume that out of hundreds of reports per week, only some are really worthy of investigation and this has to match with the development priorities so that more often than not, a report is either given a delay status or forces the slanting of other priorities behind.

If you consider each new feature has a high potential of messing up with existing stable features you understand why it takes so long some times to press on, however, the changelogs are consistent towards a long list of fixes and a few new feature improvements every time. That must go along with the policy which is to release a new model every 1 or 2 years and Garmin can't just sell the same watch it sold the previous year without anything new. I suppose we all agree the standard should be to promise less and deliver MOST of what's promised with the watch at hand, but if they keep doing things this way it will hardly ever happen.

The situation is only further aggravated by incompetent, dishonest and completely out of line localized tech support who put the blame on maps and even on the beta patches themselves "forcibly installed" as they say. Whether this behavior is criminal or not it will be for public prosecutors to say but surely they will answer to me soon enough in a court of law.

So, just saying, the QA and the Beta DEVs are the ones who are going to be always undermanned and underfunded while having to cope with the tragic (sometimes tragicomic) mistakes done by other departments. Like every major choice and even minor choices ALWAYS cascade on top of the QA and the Beta DEVs.

I'd say their work so far has been outstanding, considering the situation. The distance accrual algorithm they built, just to point out an example, is the state of the art and if you have experience with other companies and how their beta teams work you'll come to the conclusion that this particular department, while could be made to work better, is still the best on the market right now.

Be patient, it's what comes with the Beta programs everywhere.

The watch works properly in giving the time, I thought this watch was for much more, so many bugs.

You sure? Have you checked it against a real watch? Mine loses some seconds every day, so it needs daily GPS fix to be able to keep track of the time fine enough.

You sure? Have you checked it against a real watch? Mine loses some seconds every day, so it needs daily GPS fix to be able to keep track of the time fine enough.

Dude, you are totally right, my apologies, I just check the time and it is wrong for a few seconds, unbelievable, this is worst than I thought to be.

45 days with this beta.....come on!!!!

45 days with this beta.....come on!!!!

It is like i said in some earlier post: fenix5x will have the same faith like fenix3HR.From now on, firmware for fenix5x will be less and less, like 1 update to 3 months or more.

I have faced with new saved activity synchronization problem.

F5X with Beta 8.54 connected to PC via UAB cable ( Window 10 64 bit).

Synchronization via Garmin Express was broken in 2-3 secs after the manual start.

:mad: I had to import fit file manually :-( https://www.screencast.com/t/cq6GVX6pICE :mad:

:mad: Here it is the video of this problem - https://prostobzor.com/files/Fenix5x-Beta8-54-sync-bug.mp4 :mad:

I have faced with new saved activity synchronization problem.

F5X with Beta 8.54 connected to PC via UAB cable ( Window 10 64 bit).

Synchronization via Garmin Express was broken in 2-3 secs after the manual start.

:mad: I had to import fit file manually :-( https://www.screencast.com/t/cq6GVX6pICE :mad:

:mad: Here it is the video of this problem - https://prostobzor.com/files/Fenix5x-Beta8-54-sync-bug.mp4 :mad:

Seems to be a problem of your fit file ... works here. I did have that using a data field called fat burner ...