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.
Apps WorkOutDoors: New workout features
- Thread starter cfc
- Start date
- Sort by reaction score
Have you configured watchOS to start WorkOutDoors for the action button? Sometimes it seems to be necessary in order for the app to receive notification of it being pressed during a workout and sometimes not.
I guess you have tried rebooting the watch? Otherwise I don't know what to suggest. Sorry.
So I found a bug where I go to group my Workouts by Month, but then after a while the grouping is cleared and everything is listed by default again.
Or you can just uncheck "show climb screen" and even when the climb starts continue displaying your route screen
That is not a bug. The app only keeps the workout filter criteria whilst it is running. If the app is restarted by you or by watchOS then the criteria will not be remembered. So my guess is that watchOS restarted the app for some reason.
I like how, during a climb, my setup shows the climb profile instead of the route profile, keeping everything else constant.Or you can just uncheck "show climb screen" and even when the climb starts continue displaying your route screen
Try rebooting your watch. The app just asks watchOS to speak so if it takes a while then it may be busy and need restarting.
I have heard of many audio issues over the years but none have been related to the type of alert. They either work or don't work, often randomly. If it was a problem with watchOS then it could be random. If the issue is reproducible after rebooting then please send me wkt files for the workouts where it doesn't happen and where it does happen.
To do this tap the Export button 3 times quickly and then email to info@workoutdoors.net
After I installed watchOS 26.1 (RC) the voice message have been better then before. Of 8 runs, 7 have been perfect. One run the 1 km voice message came after 1.92 km, but the 2 km and all km after was working fine. It was like it got stuck in a que
Strange Heart Rate Issue
This on an Ultra 1 OS 26.1 WOD 6.2.5
Low Power Mode is enabled for workouts, but Fewer GPS and Heart Rate Readings is not.
Note that I think this is a Watch problem and not a problem of WOD.
This is how I start all workouts:
- Select the workout type
- Open the workout on the START screen
- Wait for a heart rate measurement to appear in the small space at the top
- Start the workout
FWIW, I'm 76 years old and a 5K workout is about all I can manage these days.
I've attached a screenshot. Any ideas as to what's going on here?
Anyone else seeing this or, as usual, is it just me?
Am I the only one who thinks that intervals/schedules should be a tab and not a setting ?
The heart rate not updating is a common issue with the sensor, especially if it is cold. It is getting better each year, so I think the hardware and/or software are improving but it is still a problem for many people.
Apple have some hints on how to help here: https://support.apple.com/en-us/HT207941#heartrate. I have also heard that wearing the watch on the other wrist can help for a few people, maybe because their blood vessels are closer to the surface on that other wrist.
However even these hints don't help for some people and then I recommend using an external heart rate monitor, which work in a very different way. They detect electrical impulses whereas the watch sensor beams a light into your wrist and detects heart beats from the reflections. However the effectiveness of this varies between people (tattoos, deeper blood vessels etc) and is also greatly affected by cold and also by motion. Some people only use an external monitor in the colder months and can get by in the warmer months, but a few people need it all year round.
I am glad that you realise that it's a watchOS issue. I sometimes get people who are convinced it is an issue with the app. I had one just now and I have learnt over the years that it's easier just to tell them how to get a refund for the app rather than waste time trying to convince them that it is out of the app's control.
If there was room for another tab then I would add one for Intervals but there isn't at the moment without making things slightly cramped.
And they are only used by a small proportion of the app's users (mainly very keen runners), whereas the other tabs are of use for many more activities.
I may add more tabs in the future, especially if there is a folding iPhone next year. Judging from the rumours the outer screen will be wide enough for 6 tabs and the inner screen could show many more.
Hi, I haven't been here for a while, but I'm still with Apple Watch. Firstly, @cfc , please absolutely leave Stryd alone. I'm running the first version, currently inductively charged, and surprisingly, it has all the GTC-type indicators correct. But that's just this model. Secondly, if there's any beta version currently available, please add me. Thirdly, I'll write a bit more over the weekend, but thanks again for your work.
It is much harder for the sensor to get a lock when running than when cycling, because the latter is much smoother. When running the footsteps make it harder to pick up the heart beats.
This sometimes results in a phenomenon called 'cadence lock' where the sensor locks onto your footsteps and reads very high until it has locked onto the heart beats. That isn't what you are seeing (it just can't get a lock in your case) but cadence lock has been much more common this year than in the past, so I suspect Apple have changed something.
The first version of Stryd was the only model available when I added support for their footpod, which is probably why it still works. They changed things with more recent footpods but would not help when I asked what had changed a few years back.
Whilst the main functionality (power, cadence, distance etc) still works then I will keep the support in, but if those metrics stop working correctly then I will remove it. Hopefully that probably won't happen because those metrics come from the standard BT protocols rather than Stryd's custom protocol, which carries all the other metrics like GCT, VO etc.
The problems have come because they have changed their custom protocol to add new metrics, which is totally their right. Unfortunately they don't want to share the details of the protocol with me, which again is their choice, and I don't want to spend time trying to work out what has changed every time they add new metrics.
One day I may remove support for the other metrics just to reduce the number of complaints I get from users of the newer models, but then I will probably get complaints from users of the first model like yourself!
@cfc I've used all of Stryd's models, and the first one, which I've had since 2016, is the best for me. Honestly, I'd delete all those data fields with incorrect readings because I think it's better to have nothing than incorrect data. Personally, deleting them wouldn't bother me at all. I remember yourceoids when Stryd wrote to you that the next deadline for an OFP is about six months because they're busy.