No 3rd party app, simply the native Watch workout app. So the smoothing wasn’t really smoothing I’m afraid 😂
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.
Runners beware WatchOS 10 Beta 4
- Thread starter 6SpeedPourover
- Start date
- Sort by reaction score
Done a little bit of GPS dev work before (but not much). My understanding is that the watch will be the primary GPS unit, but if it completely loses GPS, it should switch to the phone (should). The developer/app doesn't get control of this, or even know when it's happening - it happens at system level, and all the app can do is request GPS position and get it. It doesn't know if it was the watch or phone.
It also doesn't use both together. So carrying your phone will only help if the watch is completely out of GPS. It doesn't appear to use both phone and watch together.
The Apple Watch 7 (and 1-8, inc SEs) are all single band GPS. The Ultra is dual band, so should give much much better accuracy - especially when around buildings, trees and heavy cloud cover.
It also doesn't use both together. So carrying your phone will only help if the watch is completely out of GPS. It doesn't appear to use both phone and watch together.
The Apple Watch 7 (and 1-8, inc SEs) are all single band GPS. The Ultra is dual band, so should give much much better accuracy - especially when around buildings, trees and heavy cloud cover.
Don’t think so. My understanding is that AW uses GPS from a connected iPhone all the time, not just when the watch has no GPS signal. This changed with AW8, SE2 and Ultra, they never use GPS data from an iPhone.
See here: https://www.dcrainmaker.com/2022/12...pendency-shift-on-series-8-ultra-se-2022.html
How are you verifying this? As a developer I can tell you that information isn’t exposed in an API. I’m genuinely interested in knowing as I have a concept app that would benefit from this.
iPhone 13pro gives me wonky tracks. AW does not.
I am a developer too. As far as I know, no API to see the source of location data. Bad thing, proposed that plus an option to select source or configure. Feature request declined.
It’s a problem in a beta version of the operating system. The current Watch OS 9 doesn’t suffer by this bug, does it? In general, a beta is expected to be buggy - that’s the purpose of beta testing, to find issues. Those people who can’t live with such serious bugs shouldn’t use a beta and should wait for the regular release.
Bug fixes take time - you don’t want to break something yet more seriously by releasing a fix too hastily.
It's so incredibly bad. It's not even an intermittent GPS loss, it just stops recording sections/intervals entirely.
This run was made of 3 intervals (8min work -> 5min recover -> 8min work) and it completely skipped the 3rd interval. When Uploading to Strava or Intervals.icu, it's missing 8 minutes and calculates a far faster pace than it was.
This run was made of 3 intervals (8min work -> 5min recover -> 8min work) and it completely skipped the 3rd interval. When Uploading to Strava or Intervals.icu, it's missing 8 minutes and calculates a far faster pace than it was.
Seems to be unpredictable. I’ve had no issues this week but this morning my 12km (open run with manual segment markers) recorded distance and pace correctly, but with ZERO GPS or segment data.
Last run on Beta 4 today… I’ll update this evening and try beta 5 tomorrow.
Fitting that on today’s run I got literally ZERO location data. My usual 10k route, no changes at all. No location at all. Just one dot on my map where I started. Hopefully B5 is better. Good riddance to B4.
Fitting that on today’s run I got literally ZERO location data. My usual 10k route, no changes at all. No location at all. Just one dot on my map where I started. Hopefully B5 is better. Good riddance to B4.
I ran intervals (5 run, 3 walk, 8 run, 3 walk, 5 run) with Beta 5 and the results today were flawless.
Great! The public beta is finally out, I’ve installed it and will hopefully see some improvement too.
Earlier this week (i.e. with PB2 / beta 4), when running via one of my usual routes, I checked the watch shortly after the first kilometer, to see how’s the pace going. Well it was going all wrong as the watch lost gps for a bit - and when it caught up, it added extra 350-400 meters 🤦♀️ so, pace like Kipchoge, riiight… - interestingly, it was an Open Run.
Today’s run (pre-update too) was much better - several very small gaps but no noticeable impact on the pace. Open Run as well. So it’s not just buggy but also inconsistent 🤦♀️😀
So I’m curious about tomorrow’s outcome - planning just an Open Run but as those suffered by the bug too (though not to the point when e.g. half of the run was missing), at least I’ll be able to compare. And, planning some longer tempo intervals for the weekend - the GPS should better work properly then, as that training session is supposed to look good in my training log! 😂
Run of 6km in an interval of 2km in the forest. GPS got lost in two sections - 4-5m.
The rest of the route looks exemplary.
The topic seems to be solved.
But let's still check
The rest of the route looks exemplary.
The topic seems to be solved.
But let's still check
Amazing - this issue have kept me off the betas entirely for the first year in quite a while. My running is the most important part of my Apple Watch usage at the moment, so no real reason to risk it
PB 3 (should be equivalent of Beta 5), Open Run, 12 km: several very small gaps, one longer.
While running at a constant pace, I’ve noticed that the pace on the watch keeps declining (actual pace could have been around 5:45-6:00/km, displayed pace went to 8:00, 9:00 and kept slowing down). I stopped running, paused the run on the watch, waited about half a minute and resumed the run (& unpaused the watch workout), the GPS caught up but I lost about 100 m I think.
So, it’s not fixed just yet… 😐
While running at a constant pace, I’ve noticed that the pace on the watch keeps declining (actual pace could have been around 5:45-6:00/km, displayed pace went to 8:00, 9:00 and kept slowing down). I stopped running, paused the run on the watch, waited about half a minute and resumed the run (& unpaused the watch workout), the GPS caught up but I lost about 100 m I think.
So, it’s not fixed just yet… 😐
Are you asking me? Of course I’ve reported it, quite some time ago, I’ve mentioned it here back then.