F7 Series - lack of Feature Update compared to FR x55/x65

2529455 said:

lets lay our facts out so that they're clear.

• The Fenix 7 and 7 Pro have not received all features offered on the Fenix 8
• Some (not all) people have developed an assumption that devices 1 or 2 generations old would continue to receive the majority, if not all of the features on the latest devices
• Garmin have never made a claim that they will backport features to older devices
  

Let's go over the facts:

• The Fenix 7 Pro and Epix Pro stopped receiving feature updates roughly 18 months after release.

• Garmin has backported new features to cheaper Forerunner models but not to the Fenix 7 or Epix series.

• Users have repeatedly asked about this discrepancy.

• Garmin has not provided any response, despite seeing these questions, and has even locked several threads on the topic.

• Since Garmin has never explicitly promised to backport features, this means users have no way of knowing how long their devices will be supported by meaningful feature updates.

My conclusion from above mentioned is what I said before:

• It is important for users to know about this Garmin's practice since it is obviously intended behavior.
• If Garmin had a fair update policy, they wouldn’t need to avoid the discussion.

2529455 said:

The only fact here seems to be that you and a number of other customers are upset about not having their assumptions met. I hope we can both agree on that.

There are many more facts in this thread, from my and other people's posts but you are still trying to dismiss them as you are trying to dismiss the key fact that caused all this mess, so let's repeat it:

Vizi said:

this thread is not about hunches, it is about actual lack of feature updates. 

Just so that we are clear. 

7376265 said:

Just got my Fenix 7pro and now this? It feels like we've been completely abandoned. Garmin, this is NOT how you treat customers who invest in your premium products.

Exactly my point. 

I suspect the Fenix ​​7/Pro branch has a manufacturing defect that they haven't been able to fix through software and their constant failed firmware.
I've been tracking the different firmwares and there's no way I can get a correct measurement on my runs (compared to a Suunto Vertical).

17.28 loss of -200m
19.41 loss of -130m
20.16 loss of -450m
20.22 loss of -400m (left hand)
20.22 loss of -210m (right hand)

The bug has been reported and according to Laurie, it will be included in the next version. But it's been over 15 days and nothing has happened. They just posted that an engineer doesn't have it in their update path and that only one user (me) had reported it (with so many forum posts about incorrect distances, it seems absurd to me).

So, if they don't want to update with new functionality (when even older models are getting updates), they don't even want to fix problems with the watch. (15 days for a detected critical patch seems absurd to me), customer service is somewhat rude, and it's obvious the watch has a defect that makes it unaffordable to continue releasing more patches.

The problem is how we verify it.

Mark_Antony_8 said:

But it's been over 15 days and nothing has happened.

4 days ago beta version 21.04 was released. But those who had problem with measuring distance still have it: forums.garmin.com/.../distance-measurement-inaccurate

Unfortunately, there is no correction in the walking activities, which was where we found the problem :(

Fixed BLE sensor names clearing.
Fixed crash on jump rope activities.
Fixed crash when failing to pair headphones.
Fixed grade not updating.
Fixed pairing with CT10.
Fixed possible crash during long activities.
Fixed possible crash when moving golf pin position.
Fixed sensors not automatically pairing.
Fixed toggling auto broadcast heart rate.

Mark_Antony_8 said:

They just posted that an engineer doesn't have it in their update path and that only one user (me) had reported it (with so many forum posts about incorrect distances, it seems absurd to me).

I have reported it both directly via PM with Garmin-Laurie --AND-- a ticket to support.

My ticket was opened on March 3rd. # 29494388K1

Sean C said:

I have reported it both directly via PM with Garmin-Laurie --AND-- a ticket to support.

This and similar problems (with measuring distance) have certainly been reported by more users.

It is also true that different departments of Garmin do not communicate with each other, so the same bug could have been reported by several people on the Fenix ​​7 forum, several on the Epix forum, others on the Beta Program forum and still others via support.

It's ridiculous, but that's how work is organized at Garmin...

We reported this a month ago, starting with FW 20.16. According to version 20.22, it was fixed.

Given Garmin's way of working, it's very likely that they outsource their development teams (hence the division). I've only seen one software development company that does this poorly (buggy updates, denial of errors, very long deadlines for fixes, bureaucracy): TATA.

It's just that my wife's Forerunner 265 get it while the Fenix 7 Pro that's newer, doesn't. Make that make sense.