Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Don't spend any more time on this. It's nothing but an apparently harmless annoyance. Well, harmless except for the fact that my inability to figure it out is a bit frustrating.
This morning I'm doing my usual 10K bike ride. At about 1.5K I'm doing about 21 Kph when the watch announces "resume". That's it. No "pause". So strange.

I promise. No more on this.
 
Hi @cfc Ian,
I hope you have a nice day.
no pressure at all, just asking if you’ll manage to release the new beta with navigation already, or maybe provide a temporary one since the old one’s deadline is approaching.
Could we maybe squeeze the FIT import into the next beta?
😁
Thanks a lot.
robert
 
Hi @cfc Ian,
I hope you have a nice day.
no pressure at all, just asking if you’ll manage to release the new beta with navigation already, or maybe provide a temporary one since the old one’s deadline is approaching.
Could we maybe squeeze the FIT import into the next beta?
😁
Thanks a lot.
robert
The plan is to release the navigation beta before the current beta expires in a few weeks. It won't have the FIT import though (at least not for schedules; it will allow routes to be imported in FIT files).
 
Geeze, I hate to bring up another problem that is probably my fault.

Delay in Heart Rate Readings When Running​


This on an Ultra 1, OS 11.4, WorkOutDoors 5.5.4, 75 year old male.

I recently returned to running after a hiatus of several years due leg and back problems. I'm starting out very slowly with just 1k per day until I figure out if my body can handle it. I cycle instead.

It seems that when I do a running workout heart rate monitoring doesn't begin until minutes in to the workout. Yesterday it was after four minutes; two minutes today.

But, when I cycle heart rate monitoring starts right away.

I wear my watch on my left arm, face up, no tattoos with the strap one notch tighter than normal when I workout.

Is there some setting on either the watch or the app that I've messed up?

IMG_1051.jpeg


Running



IMG_1050.jpeg


Cycling
 
Geeze, I hate to bring up another problem that is probably my fault.

Delay in Heart Rate Readings When Running​


This on an Ultra 1, OS 11.4, WorkOutDoors 5.5.4, 75 year old male.

I recently returned to running after a hiatus of several years due leg and back problems. I'm starting out very slowly with just 1k per day until I figure out if my body can handle it. I cycle instead.

It seems that when I do a running workout heart rate monitoring doesn't begin until minutes in to the workout. Yesterday it was after four minutes; two minutes today.

But, when I cycle heart rate monitoring starts right away.

I wear my watch on my left arm, face up, no tattoos with the strap one notch tighter than normal when I workout.

Is there some setting on either the watch or the app that I've messed up?

View attachment 2509489

Running



View attachment 2509490

Cycling
It is much more difficult for a watch to read HR when running rather than cycling. The movement of the arm and also possibly the jarring from your feet on the ground make it harder to beam light into your wrist and analyse the resulting reflection.

As a result it is best to allow the watch to get a lock on the HR before you start moving. If you press the 3 dots next to running and then tap Open Workout then you will see a big green start button and also the HR at the top of the screen. This allows you to wait for the watch to get a lock on the HR before you tap the button to start the workout.

It is also worth warming up before doing this because the resulting increased blood flow makes it easier for the watch to detect HR.

If that doesn't work then you may want to try the watch on your other arm in case the blood vessels are more conducive to getting a reading (maybe larger; closer to the surface; better positioned for the sensor etc).

Otherwise I recommend using an external heart rate chest strap monitor. These detect HR electronically rather than optically and are much more reliable.
 
  • Like
Reactions: Buadhai
As a result it is best to allow the watch to get a lock on the HR before you start moving. If you press the 3 dots next to running and then tap Open Workout then you will see a big green start button and also the HR at the top of the screen. This allows you to wait for the watch to get a lock on the HR before you tap the button to start the workout.
That worked. Thank you.

IMG_1065.jpeg
 
Is there a way to set up completely different alerts for an interval schedule and a generic run? Example: 2 days ago I ran a 10 minute warm up, then 6x1 min hill intervals with 2 minute recovery each time, and a 5 minute cool down. I had to turn off my heart rate zone and mileage alerts because they kept causing the interval alerts to be delayed or not happen at all (audible alerts, the haptic alerts worked perfectly). Once I turned those off, no issues at all. Then today I go for a normal easy run and forgot to turn those alerts back on until 10 minutes in and had to do it while running. It'd be really nice to have alerts configured differently for each thing where I didn't have to manually change them.

Love the app by the way. I've deleted Strava and Nike Run Club since getting it a couple years ago.
 
Is there a way to set up completely different alerts for an interval schedule and a generic run? Example: 2 days ago I ran a 10 minute warm up, then 6x1 min hill intervals with 2 minute recovery each time, and a 5 minute cool down. I had to turn off my heart rate zone and mileage alerts because they kept causing the interval alerts to be delayed or not happen at all (audible alerts, the haptic alerts worked perfectly). Once I turned those off, no issues at all. Then today I go for a normal easy run and forgot to turn those alerts back on until 10 minutes in and had to do it while running. It'd be really nice to have alerts configured differently for each thing where I didn't have to manually change them.

Love the app by the way. I've deleted Strava and Nike Run Club since getting it a couple years ago.
There is a "Regular Notifications" setting in the main Schedules screen on the iPhone. This has No, Auto, Yes options with Auto being the default. When Auto is selected then the app uses the "Enable Regular Notifications" option which is at the bottom of each interval configuration screen.

This means that you can configure it on a per interval basis or over-ride that in the main schedules settings page. So in your case maybe set that main setting to No and you will never hear regular notifications during a schedule.
 
There is a "Regular Notifications" setting in the main Schedules screen on the iPhone. This has No, Auto, Yes options with Auto being the default. When Auto is selected then the app uses the "Enable Regular Notifications" option which is at the bottom of each interval configuration screen.

This means that you can configure it on a per interval basis or over-ride that in the main schedules settings page. So in your case maybe set that main setting to No and you will never hear regular notifications during a schedule.
Oohhhhh perfect. I’ll give that a shot. Thanks!
 
  • Like
Reactions: testcard and cfc
How do you get on the beta? Would love to test the navigation. Currently using goose maps which works pretty well on the watch but comes up with very basic routes, no options for preffering green spaces etc
 
How do you get on the beta? Would love to test the navigation. Currently using goose maps which works pretty well on the watch but comes up with very basic routes, no options for preffering green spaces etc
Thanks but the navigation beta is not ready yet. However it won't do any route generation and will rely on whatever app that creates the route to include the turn by turn directions.

I may add route creation in the future, but only if I can find a way without paying for an online service every time someone creates a route. Or maybe charging more for route creation, which I don't want to do.
 
  • Like
Reactions: rxp and blimundus
Ok thanks

Might have found a bug. Twice now on long hikes around the 3 hour mark the map stops rotating with the compass. I've tried toggling the setting in the app settings to have rotation to be direction of travel back to compass but no joy. The only thing that works is starting a fresh activity
 
Ok thanks

Might have found a bug. Twice now on long hikes around the 3 hour mark the map stops rotating with the compass. I've tried toggling the setting in the app settings to have rotation to be direction of travel back to compass but no joy. The only thing that works is starting a fresh activity
I haven't heard of that. Did you maybe touch the screen and pan the map so it stopped tracking? That would also stop the rotating. To start tracking again tap the icon in the bottom left of the map.
 
Tried that multiple times, scrolling and then tapping the bulls eye in the bottom left. Next time I’ll get a video recorded :)
 
Tried that multiple times, scrolling and then tapping the bulls eye in the bottom left. Next time I’ll get a video recorded :)
Whereabouts was the arrow positioned? If it was in the centre of the screen, instead of slightly below the centre then you may have just switched off rotating by tapping the red compass.

Otherwise try rebooting the watch. That often fixes strange problems that no-one else is reporting.
 
100% sure I didn't press the red compass and toggling tapping red compass, going into settings etc. did nothing to avail it. I'll reboot more often from now, I only tend to reboot after OS updates so it's probably just way too long between fresh boots
 
  • Like
Reactions: cfc
Hi Ian - a bug that has been bugging me for a while. I often run with podcasts and have an alert every 1km to let me know pace, distance etc. Often on the first alert the podcast is 'ducked' but the audible alert is not triggered (I get the haptic and screen). The problem is the podcast never get's unducked and therefore the podcast is super quiet. This generally gets fixed at about the 1.8km mark where I get the original 1km voice alert and the podcast returns to normal volume. Sometimes it takes up to 3km and I get multiple alerts banked up and read at once.

This typically gets resolved with a reboot but it is difficult to predict when it will occur. It does happen every week however. I have an original Ultra if that is helpful.
 
Hi Ian - a bug that has been bugging me for a while. I often run with podcasts and have an alert every 1km to let me know pace, distance etc. Often on the first alert the podcast is 'ducked' but the audible alert is not triggered (I get the haptic and screen). The problem is the podcast never get's unducked and therefore the podcast is super quiet. This generally gets fixed at about the 1.8km mark where I get the original 1km voice alert and the podcast returns to normal volume. Sometimes it takes up to 3km and I get multiple alerts banked up and read at once.

This typically gets resolved with a reboot but it is difficult to predict when it will occur. It does happen every week however. I have an original Ultra if that is helpful.
Sorry you are having problems. Unfortunately issues in the audio interaction with other apps have been reported on and off for many years and I have never been able to figure out why. The interaction is mainly controlled by watchOS. The app just says please use Siri to speak this phrase and watchOS does the rest. There are a few option such as volume, speed, accent and interaction mode (Pause is generally better than Duck for spoken word audio like podcasts) but the interaction is performed by watchOS.

It only affects a few people because it is only reported a couple of times a month, but it does seem to happen more with some apps than others. Spotify is the most common culprit.

Hopefully if there is a bug in watchOS then Apple will fix it, or maybe I will find that I am doing something wrong in the code. However I have looked into it so many times over the years that I have given up. My assumption is that it is out of my hands.

Sorry about that.
 
  • Like
Reactions: oboe5150
Hi Ian - a bug that has been bugging me for a while. I often run with podcasts and have an alert every 1km to let me know pace, distance etc. Often on the first alert the podcast is 'ducked' but the audible alert is not triggered (I get the haptic and screen). The problem is the podcast never get's unducked and therefore the podcast is super quiet. This generally gets fixed at about the 1.8km mark where I get the original 1km voice alert and the podcast returns to normal volume. Sometimes it takes up to 3km and I get multiple alerts banked up and read at once.

This typically gets resolved with a reboot but it is difficult to predict when it will occur. It does happen every week however. I have an original Ultra if that is helpful.
I’ve noticed that if Spotify stays ducked, i can raise my watch so the screen activates and it goes back to normal. Might work for you too?
 
  • Like
Reactions: cfc
I’ve noticed that if Spotify stays ducked, i can raise my watch so the screen activates and it goes back to normal. Might work for you too?
I'll give it a try although I'm pretty sure I instinctively do that anyway. I find myself turning the volume up to full while it is still ducked and I can hear it but then when the alerts finally start coming though it tends to blast my ears off.
 
Sorry you are having problems. Unfortunately issues in the audio interaction with other apps have been reported on and off for many years and I have never been able to figure out why. The interaction is mainly controlled by watchOS. The app just says please use Siri to speak this phrase and watchOS does the rest. There are a few option such as volume, speed, accent and interaction mode (Pause is generally better than Duck for spoken word audio like podcasts) but the interaction is performed by watchOS.

It only affects a few people because it is only reported a couple of times a month, but it does seem to happen more with some apps than others. Spotify is the most common culprit.

Hopefully if there is a bug in watchOS then Apple will fix it, or maybe I will find that I am doing something wrong in the code. However I have looked into it so many times over the years that I have given up. My assumption is that it is out of my hands.

Sorry about that.
I've only had this happen on WorkOutDoors so I would suggest there is still some extra logic/protection that you might need to apply to retain control of the sound. For reference, I'm just using the standard Podcast application and am not carrying my phone at the time. I have developed a few speech pathology applications that require access to the microphone and audio output and need to play nicely with system audio so I appreciate it can be tricky to get right. For me, this bug is my only annoyance with the application so I would defiantly appreciate you revisiting this at some point. I'm happy to run beta code and/or capture logs for you if it would help.
 
Hi! Is it possible to set an average pace metric based on elapsed time as well? If not, would it be possible to add that feature in a future update? I was thinking it could be useful in some ultra-racing situations, especially when stopping at aid stations for a few minutes to eat and rest. This could help save battery and minimize GPS errors and additions on this situation. Does it make sense?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.