Runners beware WatchOS 10 Beta 4

Some observations from today - finally could do a larger variety of workouts:

1) 2.5 km Open Run - no issues

2) intervals workout 3 x (2 km in a defined pace range + 3 mins recovery):
- two short GPS gaps
- the first gap caused shortening of the interval (added about 200 m so I actually ran only about 1800 m when the interval was marked as finished - i.e. calculated pace became faster than it should have been)

3) intervals workout 4 x (3 km in a defined pace range + 4 mins recovery):
- five short GPS gaps
- distance seems to be correct

4) 2 km Open Run - no issues

The route doesn’t look “wonky”, matches the map fairly accurately in all 4 runs.

Series 7 watch with PB 3.

(I’ll be adding this information & diagnostics to my original bug report via Feedback.)
 
Last edited:
Jana_CZ said:
Some observations from today - finally could do a larger variety of workouts:

1) 2.5 km Open Run - no issues

2) intervals workout 3 x (2 km in a defined pace range + 3 mins recovery):
- two short GPS gaps
- the first gap caused shortening of the interval (added about 200 m so I actually ran only about 1800 m when the interval was marked as finished - i.e. calculated pace became faster than it should have been)

3) intervals workout 4 x (3 km in a defined pace range + 4 mins recovery):
- five short GPS gaps
- distance seems to be correct

4) 2 km Open Run - no issues

The route doesn’t look “wonky”, matches the map fairly accurately in all 4 runs.

Series 7 watch with PB 3.

(I’ll be adding this information & diagnostics to my original bug report via Feedback.)
Click to expand...
So the thought it’s primarily the custom workouts still sticks in this PB. Damn
 
In previous betas the weather complications were completely broken, and the battery was horrendous.

This seems improved in Dev Beta 5 (i think it's 5. Whatever the latest is). The battery is now acceptable. Not as good as before, but acceptable. Weather complications are working fine again.
 
I haven't had any issues with any types of runs for over a week now. Had one run last week just not have any data on the map except my start point, but that has happened once or twice in the past. My path on the map isn't perfect, and I had one section on my run last Friday go off by nearly a block and act like I ran through multiple buildings, but other than that it's been about as good as it was before beta 4 came out.
 
Yeah I think we can safely call this one resolved for now. I ran 18 miles yesterday through trails and roads with no gaps at all.
 
6SpeedPourover said:
Yeah I think we can safely call this one resolved for now. I ran 18 miles yesterday through trails and roads with no gaps at all.
Click to expand...
And you ran the Custom runs? From what I read it seemed like it was only during the custom runs for some reason
 
First run with the PB today. Not the new from yesterday but the one from last week but terrible!

First my 15K was split into warm up and intervals and cool down. After just over half way, I just paused the run to answer my wife on a text via dictation and when going back into the workout app it made a load screen and after that an error when trying to resume the workout and just ended the run - DAMN IT!!

Started an open run and finished the distance but 2K from home it ran out of power (started with 19% which would never have been an issue for 15K normally)

Hopefully the beta from yesterday will fix it but dang
 
I don't think this is 100% resolved. I did 3 runs this week. All 3 were open runs. Whilst the GPS route was fine, looking at the elevation screen during the run, it had chunks of missing elevation data. Strava filled this in using its own map knowledge. I think this is mostly resolved, but not completely.
 
IMG_1590.png

Had a long run this Saturday out and back the same way. It had some tough intervals and I looked at the watch during those quite a lot to make sure I hit those speeds.

At some point - not long - it suddenly just upped the seconds per kilometre and not the distance like I was standing still - then boom it snapped back on.

Now I can’t guarantee it hasn’t been doing this without me noticing on WatchOS 9 but I have never seen it.

Clear on the map it lost connection for a while
 
xDKP said:
And you ran the Custom runs? From what I read it seemed like it was only during the custom runs for some reason
Click to expand...

Maybe some others said that about custom runs, but I definitely had issues with all types and I'm pretty sure I clarified that at some point. I almost never do open runs, but before this improved I had serious problems with distance goal runs and custom interval runs.

And in response to others saying that it's not fully resolved, I think it's important to remember that GPS data isn't always going to be perfect. I've been running with AW for years with 3 different models of watch. Some runs show map data well, and some don't. It could be that a run was cloudy, under a lot of trees, or something just didn't work right randomly. I've had a few runs here and there show that I ran straight through the wall of a 10 story apartment building. It happens. The issue is when you lose significant data for the majority of a run for multiple runs in a row.
 
xDKP said:
At some point - not long - it suddenly just upped the seconds per kilometre and not the distance like I was standing still - then boom it snapped back on.
Click to expand...
I’ve seen it several times too (latest today - 12k Open Run, several short gps gaps but actually not where the problem happened). I’m quite sure it wasn’t happening on version 9, as I often run with a set pace range and audio notifications - so I would most certainly have noticed.

I haven’t managed to find any reliable steps to reproduce, it’s intermittent but super annoying. I think it’s usually happening with an Open Run; at some point the distance stops increasing and the pace continues dropping, no matter what your actual pace is. Maybe it would have caught up itself but I got too nervous - I stopped running, paused the workout, waited a bit, unpaused and continued running, and shortly afterwards the pace showed correctly again.

One of the symptoms is messed up pace in the impacted segment (as well as overall pace), but also the overall distance. After syncing today’s run to Strava and using the Correct Distance feature to recalculate the distance, it turned out that the Watch stole about 300 meters from me! 😐

I think this is yet a bit different from the bug with Custom runs & missing elevation/gps data; having said that, I wasn’t able to find a pattern just yet, to be able to file a bug…
 
Meh. Lost at least a quarter mile of a 6 mile run today. Huge gaps missing in my first mile. Haven’t updated to today’s beta release yet on the watch so it’s still from last week’s release.
 
Jana_CZ said:
I’ve seen it several times too (latest today - 12k Open Run, several short gps gaps but actually not where the problem happened). I’m quite sure it wasn’t happening on version 9, as I often run with a set pace range and audio notifications - so I would most certainly have noticed.
Click to expand...

I never had any discrepancies with watchOS 9. As I usually run the same set of courses week over week, I would have noticed.

Please open a ticket and send Apple the recorded track. Only two weeks to go until release. :(

 
Jana_CZ said:
Maybe it would have caught up itself but I got too nervous - I stopped running, paused the workout, waited a bit, unpaused and continued running, and shortly afterwards the pace showed correctly again.

One of the symptoms is messed up pace in the impacted segment (as well as overall pace), but also the overall distance. After syncing today’s run to Strava and using the Correct Distance feature to recalculate the distance, it turned out that the Watch stole about 300 meters from me! 😐
Click to expand...
Mine did catch up, but on my map it shows a direct line and not the correct curved path - so if it would do it when turning a corner or something it would be more messed up.

Haven't tried the Correct Distance feature - might look into it if I see this again :)

Developer Beta out yesterday so hopefully a public as well with some bug fixes.
 
NME42 said:
Please open a ticket and send Apple the recorded track. Only two weeks to go until release. :(
Click to expand...

I’m struggling with describing how/when it happens. As I myself work for an IT company, I’m aware how important the steps to reproduce are - devs can’t reliably fix something that’s random and not reproducible. But I’ll try.

xDKP said:
Developer Beta out yesterday so hopefully a public as well with some bug fixes.
Click to expand...
Yes PB is out, I’m just downloading it. I have some longer intervals training scheduled for tomorrow so I’ll see if the bug manifest there - though it’s gonna be a Custom Run… some more Open Runs will follow in the next few days so we’ll see.
 
Jana_CZ said:
I’m struggling with describing how/when it happens. As I myself work for an IT company, I’m aware how important the steps to reproduce are - devs can’t reliably fix something that’s random and not reproducible. But I’ll try.


Yes PB is out, I’m just downloading it. I have some longer intervals training scheduled for tomorrow so I’ll see if the bug manifest there - though it’s gonna be a Custom Run… some more Open Runs will follow in the next few days so we’ll see.
Click to expand...
My issue was with custom as well. Looking forward to try this out. I have open run Thursday and Friday and a long intervals Saturday
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top