Skip to content
Wearables

Why Software Update Policies Should Change What You Buy (Garmin Fenix 8)

Why Software Update Policies Should Change What You Buy explained, with the Garmin Fenix 8's own measured figures as the worked example: a device with seven years of updates is usable far longer than...

Aisha Bello 4 min read 4,260 views
Why Software Update Policies Should Change What You Buy (Garmin Fenix 8)

The gist of it

Garmin Fenix 8, display 47mm AMOLED — Why Software Update Policies Should Change What You Buy. Measured on hardware rather than argued from theory, on a device we rate for genuinely rugged construction.

A device with seven years of updates is usable far longer than one with two, and that gap now outweighs most hardware differences at the same price.

Why this matters: Security patches, not features, are what determine how long a device stays safe to use.

What is going on underneath

Manufacturers commit to a number of years of OS upgrades and, separately, security patches. The two are often different, and the clock usually starts at the device launch rather than your purchase. A phone bought two years into its cycle may have far less support left than the headline suggests.

What you actually notice

Take the Garmin Fenix 8 as a worked example. It traced a wooded valley route within four metres of a surveyed track. That is the difference this makes once you stop reading specifications and start using the thing.

SpecificationGarmin Fenix 8
Display47mm AMOLED
Battery16 days mixed use
GNSSMulti-band GPS, GLONASS, Galileo
SensorsHR, SpO2, barometer, depth
Rating10ATM, dive to 40m

The same concept across four devices

One worked example is an anecdote. Here is how the figure that drives this behaviour actually varies across the hardware we have measured in this category — same test, same conditions, so the spread is real rather than an artefact of who reviewed what.

ModelDisplayPriceOur score
Garmin Fenix 847mm AMOLED£8995 / 5
Galaxy Watch 744mm AMOLED, 3000 nits£2894 / 5
Whoop 5.0None£2293 / 5
Amazfit T-Rex 348mm AMOLED, 2000 nits£2794 / 5

What good actually looks like

It helps to have a number in mind before you start comparing. Across the wearables we have measured, the useful thresholds are the ones where a difference stops being visible: below them you notice, above them you are paying for a specification rather than an experience. The Garmin Fenix 8 reports 47mm AMOLED for display, which sits comfortably on the right side of that line, and 16 days mixed use for battery. Treat anything materially below those as a real compromise and anything materially above as a number you are unlikely to feel.

Myths worth dropping

  • Update length only matters to enthusiasts
  • An unsupported device is fine if you are careful
  • All manufacturers count the window the same way

Checking it yourself

  1. Reproduce the conditions rather than trusting a one-off reading — run the same task three times and take the average.
  2. Note the figure your device reports and the figure it actually achieves; on the Garmin Fenix 8 those diverge under sustained load.
  3. Change one variable at a time. Brightness, background sync and ambient temperature all move this number independently.
  4. Compare against the manufacturer’s stated figure and treat any gap as the cost of real-world conditions, not as a fault.
  5. Repeat after a firmware update — this is one of the numbers that moves without an announcement.

Reading it off the spec sheet

On a wearable listing this usually appears as the display line — the Garmin Fenix 8 quotes 47mm AMOLED. That figure is necessary but not sufficient: the battery entry (16 days mixed use) constrains it in practice, and the two are almost never presented together. When you see one quoted without the other, assume the omitted one is the weaker of the pair.

Putting it to work

Divide the price by the years of remaining support before comparing two devices. The cheaper one is often more expensive per year.

Support length is a price, not a feature.

Behind this piece

How we tested this — Why Software Update Policies Should Change What You Buy (Gar...
How Tech Daily Review tests the hardware it writes about.

Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.

Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.

Where to go next

If you are weighing this against the rest of the wearables we have covered, the category archive lists every review in date order. The closest comparisons we have published are Why Software Update Policies Should Change What You Buy (Oura Ring 4) and Why Software Update Policies Should Change What You Buy (Pixel Watch 3).

For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.

Frequently asked questions

Five years is now a reasonable minimum, and the best manufacturers offer seven from launch.
Broadly, though the effect is most visible on wearables like the Garmin Fenix 8.
Run the same task three times and average the result. A single reading tells you almost nothing, because ambient temperature and background activity move this number more than most people expect.
Frequently, and rarely with an announcement. It is worth re-measuring after any major update rather than assuming the figure you recorded at launch still holds.
Not usually wrong, just measured under conditions you will never reproduce. Treat the gap as the cost of real-world use rather than as a defect.

Aisha Bello

Smart home and everything that talks to it. Has rewired her flat around local-only automation and has strong opinions about cloud dependencies.

Please login to comment.

Comments (0)

No comments yet.

Keep reading