No, normal outdoor run.
Did not have this issue again since. As others reported this thing too, I will keep an eye on it.
Your issue sounds weird too. One common thing is the action button and hence the AWU. Maybe just pure coincidence, maybe not.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Running with the Apple Training app
- Thread starter NME42
- Start date
- Sort by reaction score
No, normal outdoor run.
Did not have this issue again since. As others reported this thing too, I will keep an eye on it.
Your issue sounds weird too. One common thing is the action button and hence the AWU. Maybe just pure coincidence, maybe not.
Annoyance/Bug with Action Button.
According to - https://support.apple.com/en-gb/guide/watch/apda005904ef/watchos
Press again/during an active (running) Workout marks a Segment. This is GOOD. Useful when running ad-hoc intervals that want to easily see post workout.
HOWEVER - if you're running a structured workout (with steps etc), the behaviour of the button changes so that pressing it 'skips to the next step'. This is also good, as it enables to cut short recovery periods if it happens to be convenient based on where you are.
But, if you run "past the end" of a planned structured workout, where the Activity then just continues as an Open Workout, the behaviour of the Action button gets broken, and instead of reverting to "Mark a Segment" (now there are no more steps to skip), it becomes a PAUSE/RESUME button...this is obviously a pointless function, as Action+Side carries the Pause function.
The use case for this for me is where I've ran and completed a structured progressive Workout, which I've programmed, and then I want to roll straight into what will be some ad-hoc intervals, I should be able to just hit the Action button and have segments marked "beyond the end of a structured/planned" workout? Surely?
According to - https://support.apple.com/en-gb/guide/watch/apda005904ef/watchos
Press again: Perform a secondary action based on the selected workout.[I]Press the Action button and side button together:[/I] Pause.Press again/during an active (running) Workout marks a Segment. This is GOOD. Useful when running ad-hoc intervals that want to easily see post workout.
HOWEVER - if you're running a structured workout (with steps etc), the behaviour of the button changes so that pressing it 'skips to the next step'. This is also good, as it enables to cut short recovery periods if it happens to be convenient based on where you are.
But, if you run "past the end" of a planned structured workout, where the Activity then just continues as an Open Workout, the behaviour of the Action button gets broken, and instead of reverting to "Mark a Segment" (now there are no more steps to skip), it becomes a PAUSE/RESUME button...this is obviously a pointless function, as Action+Side carries the Pause function.
The use case for this for me is where I've ran and completed a structured progressive Workout, which I've programmed, and then I want to roll straight into what will be some ad-hoc intervals, I should be able to just hit the Action button and have segments marked "beyond the end of a structured/planned" workout? Surely?
This doesn’t seem to be the case - every time I run under a highway through a tunnel the pace and everything screws up shortly - it also screws the map.
Last edited:
Another example is the Chicargo Marathon (haven't been running it myself). It known for screwing up GPS signal because of the bridges, tunnels and tall buildings so your distance it known to be off on the watch compared to other marathons.
If it didn't use the GPS for distance/pace, it would screw up the map yes, but not the distance/pace
If it didn't use the GPS for distance/pace, it would screw up the map yes, but not the distance/pace
It’s used, but it’s not the main source.
If the gps is completely cut (as it occurs when it crashes), you continue to get distance and speed (including in tunnels)
GPS is helping to recalibrate the distance continuously (and if the signal is super bad, it has a bad influence on this calibration), but is not necessary (you was able to track a workout with a series 0 with no gps)
Yeah remember the S0 days and did go for runs without my phone once in a while. I would suspect Apple to have updated the system and use of GPS chips since the S0 though
How's GPS not the main source?
When there's any kind of GPS hiccup/outage, you can immediately spot that already during the run - the pace/distance become wildly inaccurate. It's exactly what some of us experienced in spring 2023, examples can be found in this or the previous thread. (Look for screenshots with a dotted path in the map.)
Anyway, came here to ask about something different. There's this new close-all-3-rings badge but for whatever reason, my count is very low (18 now, should be a 4-digit number) and keeps decreasing. Anyone saw something similar?
When there's any kind of GPS hiccup/outage, you can immediately spot that already during the run - the pace/distance become wildly inaccurate. It's exactly what some of us experienced in spring 2023, examples can be found in this or the previous thread. (Look for screenshots with a dotted path in the map.)
Anyway, came here to ask about something different. There's this new close-all-3-rings badge but for whatever reason, my count is very low (18 now, should be a 4-digit number) and keeps decreasing. Anyone saw something similar?
Yeah I had the same errors with GPS and the dotted path and it INSTANTLY started ruining the current pace - remember it was with beta software I think and often during custom runs. Had it a couple of times during intervals and pretty bad it screws up the pace when you are running at high speed
My close-all-rings was also totally bad in the start - but I think somehow fixed itself (don't know how) so maybe it's also a server thing?
Would you remember how long it took? It's not super important - I haven't even noticed that till last week or so 😃 - but now that I know about the bug, it's bugging me of course. But if all it needs is waiting a bit longer, I guess I can ignore it happily for now...
Don’t remember for sure actually - maybe a week or two. Did remember I rebooted booth devices a couple of times
I’m closing in on 2.250 for all circles
Ok so the all-circles issue was finally resolved with the 18.3.2 update. I'm apparently only on 1739 but well, better than the single digits it's been showing lately 🤓
In the Workout app select Outdoor Run/Preferences/Alerts/Time
