Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
tsk tsk - and still not a real runner 😁
True. Maybe the next 30 years of running make me one. But maybe not. The last 30 were not successful either. :D

Btw, long before Garmin released their first watch I tracked my runs with a Nike footpod. Not the one they had a cooperation with Apple and their iPods. Years before they sold a very big footpod together with a watch. Excellent battery life and very stable. ;-)

Good old times. Back then we made the distinction between runners and joggers based on if you are able to run 10k sub 40 and not on what watch you wear or not. :D
 
Last edited:
  • Like
Reactions: quarq and Zelegorm
True. Maybe the next 30 years of running make me one. But maybe not. The last 30 were not successful either. :D

Btw, long before Garmin released their first watch I tracked my runs with a Nike footpod. Not the one they had a cooperation with Apple and their iPods. Years before they sold a very big footpod together with a watch. Excellent battery life and very stable. ;-)

Good old times. Back then we made the distinction between runners and joggers based on if you are able to run 10k sub 40 and not on what watch you wear or not. :D
I started tracking with the iPod + Nike kit first - before that no tracking of speed or anything so was a pretty big shift for me. After that jumped on the dedicated Nike+ Watch

IRG2GSJXFQ24NV4CHZNWLNG5JI.jpg


again pretty big upgrade and from there Apple Watches so haven't been in the Garmin camp - and as long as I don't qualify for UTMB I don't really need longer GPS-active battery life than the Ultra series can handle.
 
  • Like
Reactions: Zelegorm and NME42
I started tracking with the iPod + Nike kit first - before that no tracking of speed or anything so was a pretty big shift for me. After that jumped on the dedicated Nike+ Watch

View attachment 2472550

again pretty big upgrade and from there Apple Watches so haven't been in the Garmin camp - and as long as I don't qualify for UTMB I don't really need longer GPS-active battery life than the Ultra series can handle.
Cool.

My Nike footpod was at 1999 or so. I did not find any photos on the web, Google finds tons of Nike+ stuff though. My sensor was so big it had a AA battery (or two, can’t remember) inside.

Before that, I had measured and marked road segments and entire courses with my bike and a very basic bike „computer“.
 
  • Like
Reactions: Zelegorm and xDKP
Seems Garmin is burning down right now. This message is on all their forums, Fenix 8, 7, Epix, etc:

Bildschirmfoto 2025-01-28 um 14.36.08.png


No updates delivered, seems to have started out of the blue.

Great software quality.
 
  • Wow
Reactions: xDKP
Seems Garmin is burning down right now. This message is on all their forums, Fenix 8, 7, Epix, etc:

View attachment 2476726

No updates delivered, seems to have started out of the blue.

Great software quality.
Certainly not good. Maybe it's good I returned the Fenix and got the Instinct 3, lol.

Not nearly as critical, but speaking of bad software, why does my weather widget always revert to not displaying any data on my AW?
 
Certainly not good. Maybe it's good I returned the Fenix and got the Instinct 3, lol.

Instinct 3 is also affected once the faulty satellite data is delivered:


Good luck!
 
  • Like
Reactions: xDKP
That’s the great garmin software quality. At least the battery life is still good on some devices. Mine is still not good if not shocking bad 😂
 
  • Like
Reactions: xDKP and NME42
That’s the great garmin software quality. At least the battery life is still good on some devices. Mine is still not good if not shocking bad 😂

Don’t be so harsh. At least workouts without GPS seem to work for some users. Also better for battery life.
 
  • Haha
Reactions: xDKP and Zelegorm
Instinct 3 is also affected once the faulty satellite data is delivered:


Good luck!
Mine is fine. Just tried to start an activity and no issues. Garmin pulled the faulty GPS cache file.
 
  • Like
Reactions: xDKP and NME42
A true „Adventure Watch“.
Glad that your watch is working.
Ah! Now I get the point with the true adventure watch. And remember. Only for real sports people out there. 🤣 In the meanwhile I am still running and biking with my AWU with 30k runs and 80k last week + biking. With real health functions and stable software 😎. Back to the topic: Way too expensive for the short battery life and weak and inaccurate functions. Sorry garmin
 
  • Like
Reactions: xDKP and NME42
And remember. Only for real sports people out there. 🤣 In the meanwhile I am still running and biking with my AWU with 30k runs and 80k last week + biking.

Me too. Did three workouts today: cycling, running and strength training. Flawless recording with my AWU2 and no adventure. Boring life of a health-oriented leisure sports guy, yawn.
 
  • Like
Reactions: Zelegorm
So what’s the cause?

The same cause it was a four years ago when this happened: The satellite pre-cache file (also called the CPE or EPO file). Basically, that’s the file that the GPS chipset uses to more quickly find GPS satellites. In a world before pre-cache files, it would take 20-60 seconds. Now, it takes 1-3 seconds. Think of it like a cheat sheet for the sky/satellites.

That file gets updated on your watch every few days, and generally goes stale within a week. However, if a bad version of the file gets delivered, then chaos can ensue – as we saw a few years ago, when it impacted far more than just Garmin, but also Suunto, Polar, Wahoo, COROS, and others on the Sony chipset at the time. In the case of back-then, this resulted in offset GPS tracks, rather than instant restarts of the watch. While your watch only receives a new file every few days, new CPE files are generated by the server daily, and thus the variability on whether or not your watch has the offending file or not.

So according to DCRainmaker the cause of this bootloop is a bad CPE file which is provided to all companies using that GPS chipset. This has happened in the past and to more than just Garmin.

Seems really poor form to blame this on Garmin. This would be like blaming Apple for a bug in an Intel chip or when Apple had issues with NVIDIA chips. Everyone in the business has to use subcontractors for certain things in their products.

Now we can reboot our Garmin watches, go back to using them or perhaps we can digress to the alleged forever cancer chemicals in certain Apple Watch bands.

I mean if we want to go there on every little issue I guess we can or we can enjoy using this stuff and realize no software or company bats 1.000.
 
This would be like blaming Apple for a bug in an Intel chip or when Apple had issues with NVIDIA chips. Everyone in the business has to use subcontractors for certain things in their products.
This is not how that works. Garmin delivers a product and is accountable for the product. No one cares who they subcontracted.
Or have you ever heard of an Apple user soldering out an Intel CPU and sending that to Intel?
 
  • Like
Reactions: xDKP
I am not interested in any root cause. Garmin is selling they way too expensive watches. That’s why they have to care. And that’s why they have to be blamed. And my Apple Watch is still running. And my Suunto too. Sorry. Blame on garmin. No one else
 
  • Like
Reactions: xDKP and NME42
So according to DCRainmaker the cause of this bootloop is a bad CPE file which is provided to all companies using that GPS chipset. This has happened in the past and to more than just Garmin.

Seems really poor form to blame this on Garmin. This would be like blaming Apple for a bug in an Intel chip or when Apple had issues with NVIDIA chips. Everyone in the business has to use subcontractors for certain things in their products.

Now we can reboot our Garmin watches, go back to using them or perhaps we can digress to the alleged forever cancer chemicals in certain Apple Watch bands.

I mean if we want to go there on every little issue I guess we can or we can enjoy using this stuff and realize no software or company bats 1.000.
A top quality company is supposed to test before deploying anything …
It’s not a « niche » bug, it combines widespread + main sport watch feature broken.
It’s easy to test as it immediately breaks the GPS on all watches, it’s not a feature that fails in a specific case.
It’s a major fail…

Garmin is lucky to be « just « Garmin, I can’t imagine the scandal if this kind of problem occurred on an Apple device…
 
Last edited:
It’s a major fail…
For me comparable to the Crowdstrike desaster last summer. Faulty config file crashes a multitude of devices.

And also a major security concern for supply chain attacks. Obviously no proper testing and checking what they deliver to their customers and no fault tolerant devices rejecting flawed config files.
 
For me comparable to the Crowdstrike desaster last summer. Faulty config file crashes a multitude of devices.

And also a major security concern for supply chain attacks. Obviously no proper testing and checking what they deliver to their customers and no fault tolerant devices rejecting flawed config files.
It’s less critical than crowdstrike, it won’t stop critical computers, it’s just about sport metrics …
But it’s a major fail for such company…
 
It’s less critical than crowdstrike, it won’t stop critical computers, it’s just about sport metrics …
But it’s a major fail for such company…
Don’t underestimate that. The Garmin watches are internet connected devices. One could do a lot of bad things with them if compromised.
Sure not as much as with a PC but still enough.
 
A top quality company is supposed to test before deploying anything …
It’s not a « niche » bug, it combines widespread + main sport watch feature broken.
It’s easy to test as it immediately breaks the GPS on all watches, it’s not a feature that fails in a specific case.
It’s a major fail…

Garmin is lucky to be « just « Garmin, I can’t imagine the scandal if this kind of problem occurred on an Apple device…

Are you and others seriously going to claim there have been no Apple bugs or issues that have caused their devices to go into a boot loop?

A basic Google search simply shows that not to be true.

Garmin responded to this in a couple hours. The non-corrupted file was uploaded to their server. A hard reboot and sync solved it. If a device had not started a GPS activity there was never a problem and it was updated in the background.

I’m sorry but I own tons of Apple gear and to claim they’ve never had a need for a quick security patch, that their devices can never experience a boot loop and that all their software comes out with zero issues is just pure trolling and a lie.
 
Garmin is lucky to be « just « Garmin, I can’t imagine the scandal if this kind of problem occurred on an Apple device…
Exactly that’s the case. Garmin outage on their service so many times. The customers doesn’t even care. All those software bugs. It’s crazy how bad Garmins service is. The other way round it would be never ever a „small“ thing. And again: The main reason is here the utopia prices for those watches. Not acceptable at all
 
  • Like
Reactions: NME42
I had been holding out for a new Fenix but with today’s silly pricing I’m thinking the AW Ultra would be a better choice. Think I’m done with Garmin. Let’s hope Apple don’t take a leaf out of Garmins books and have silly pricing for the AWU3, what’s your thoughts on all this?

Tbh if I could get a discount on the AWU2 when the 3 comes out I’d bite the bullet.
I didn't recognize the term AW Ultra, and the answer I got, "Andy Williams", is probably not what you're referring to :) Now I know it's Apple Watch.
 

Attachments

  • AW Screenshot 2025-01-28 at 4.30.03 PM.png
    AW Screenshot 2025-01-28 at 4.30.03 PM.png
    309.9 KB · Views: 33
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.