That´s the reason why i asked.
It´s quite a hassle to delete, reinstall and try to send the old settings of the app to the watch, after a restart.
Hope it will help you!
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
It´s quite a hassle to delete, reinstall and try to send the old settings of the app to the watch, after a restart.
Hope it will help you!
Hello everybody.
I’m a new user to the forum and to the WOD app.
Can I ask if there is a way to push heart rate zone breakdown into iOS Activity app?
When I was using Apple Workout app the track my runs, Activity app will tell me how much time I spent in each heart rate zone.
When I used WOD, I can see the time spent in each zone on WOD, but this doesn’t seem to be pushed to Activity.
Am I missing a setting?
Thanks.
I’m a new user to the forum and to the WOD app.
Can I ask if there is a way to push heart rate zone breakdown into iOS Activity app?
When I was using Apple Workout app the track my runs, Activity app will tell me how much time I spent in each heart rate zone.
When I used WOD, I can see the time spent in each zone on WOD, but this doesn’t seem to be pushed to Activity.
Am I missing a setting?
Thanks.
Welcome to the forums!
Unfortunately I don't think that Apple make it possible for 3rd party apps to use their heart zones. This may change in the future though because zones have only been in watchOS for a couple of months and sometimes Apple take a while to add third party support for new features.
Purchased an AW8 yesterday as well as WOD. Kudos to developer, Ian maybe?
Like Mauki, I was unable to see my "current pace" while running. After finishing the run, I was able to see pace info (avg. and max). My watch was set to use GPS vs. Health as its source. I've toggled it to Health and will see what happens. Heading out to walk dog, maybe I'll get pace info today.
When configuring Screen 1, Tapping Distance shows "requires sensor". I assume this doesn't mean a footpad of sorts. I used GPS as the Source for Distance & Avg. Pace and distances were mapped correctly. Am I missing something.
Thanks,
FH
Like Mauki, I was unable to see my "current pace" while running. After finishing the run, I was able to see pace info (avg. and max). My watch was set to use GPS vs. Health as its source. I've toggled it to Health and will see what happens. Heading out to walk dog, maybe I'll get pace info today.
When configuring Screen 1, Tapping Distance shows "requires sensor". I assume this doesn't mean a footpad of sorts. I used GPS as the Source for Distance & Avg. Pace and distances were mapped correctly. Am I missing something.
Thanks,
FH
Sorry that current pace was not visible. Was the pedometer not working for you either? That is the reason that Mauki used a different source. The pedometer is the default and GPS should only be used a last resort because it is very unreliable for current pace. It should still be visible though so I will see if there is an issue. Health is the second best option (and may become the default depending on the feedback I get, which has been mixed so far).
The "requires sensor" note for distance is a cut & paste error, so please just ignore that until it is fixed in the next version.
Pedometer I will test on my next run, hope this will get me a smooth current pace.
Health is total worse, I can‘t believe that someone use this. Health sucks like GPS setting. (Sorry for that).
Are there serious runners here?
Why a Fenix from 2015 can show an smooth pace with gps and the Apple Watch or WOD can‘t.
Even my Garmin Forerunner 305 from 2010 could display the pace!
I have been running with Garmin devices (a lot of them across the forerunner and fenix ranges) since they are on the market.
Instant (current) pace has never been good. You could use something like 10s averages (with CIQ datafield) which gave a more or less reasonable and stable pace information.
The latest fenix7/epix2 gen is a game changer when it comes to gps quality. I think that Apple could be on the same level with their hardware setup, but might need to fine tune their smoothing algorithms a bit more.
Currently I use WOD with either 10s or 100m averages based on either pedometer or health (last test didn‘t make a difference) and I am happy with it.
But I will play around with instant pace regularly. Still curious about the effect of the smoothing slider. This function could be better explained.
Instant (current) pace has never been good. You could use something like 10s averages (with CIQ datafield) which gave a more or less reasonable and stable pace information.
The latest fenix7/epix2 gen is a game changer when it comes to gps quality. I think that Apple could be on the same level with their hardware setup, but might need to fine tune their smoothing algorithms a bit more.
Currently I use WOD with either 10s or 100m averages based on either pedometer or health (last test didn‘t make a difference) and I am happy with it.
But I will play around with instant pace regularly. Still curious about the effect of the smoothing slider. This function could be better explained.
I ask a Youtuber who use Workoutdoors and he tell me the following.
Hello Markus, I have the same problem with the current iOS version 9.1 that the pace is displayed "offset". In the data fit but. Since it is at the moment no matter with which app you record...therefore problems of the operating system. Have there unfortunately directly also no spontaneous idea
Is that true that is a problem by watchOS?
Hello Markus, I have the same problem with the current iOS version 9.1 that the pace is displayed "offset". In the data fit but. Since it is at the moment no matter with which app you record...therefore problems of the operating system. Have there unfortunately directly also no spontaneous idea
Is that true that is a problem by watchOS?
Therefore I use 3 second pace at my Fenix 3 and it is nearly perfect with gps. It jumps in the area fr9m 2-3 seconds and that is ok.
With using WOD the pace jumps over a minute in a second.
10s is a bit long and it is worse when I use this datafield with Health.
What does the slider do?
Walked the dog ~ 1.4miles. First half of walk, I used the "Walking Workout" module, during the second half, I used the "Running Workout" module. Source was toggled to Health, still no current pace, nor where calories registered. Avg Pace did compute.
Perhaps I have some settings set incorrectly. When configuring Screens: When looking at Pace - what is the difference between Pace (Current) and Pace (GPS), as well as Speed (Current) and Speed (GPS)?
Last edited:
The smoothing slider makes the current pace the average of the last n values, where n increases as you move the slider to the right. By default it is at the far left, which means using the raw value as supplied by watchOS.
It looks like you are missing lots of permissions, so please check that you have given the app permission to see all the health data. To check this go to the Settings app on the iPhone and select Privacy / Health / WorkOutDoors. Make sure that every health setting is enabled (you may need to scroll down to turn them all on).
Also please check that you have given the app permission to use the pedometer. To do this go to the Settings app on the iPhone and tap Privacy and then Motion & Fitness, then make sure Fitness Tracking is enabled and so is WorkOutDoors. Then go to the Watch app on the iPhone and select Privacy and ensure that Fitness Tracking is enabled there.
Average pace is much easier to calculate than current pace. It is just the distance divided by the time, so as long as your distance is accurate then the average pace should be accurate.
Current pace is the pace at an instant. This is much more difficult to calculate, which is why I leave it to watchOS and allow users to choose which watchOS system to get it from. It is difficult because you need to choose a window over which to calculate it and then you divide distance by time for that window. If the window is too short then the current pace can be very erratic because of sensor inaccuracies and if it is too long then it can be less reactive to changes in pace.
The smoothing parameter in WOD allows you to effectively increase whatever window watchOS is using.
It is a trade-off. More smoothing makes the current pace more accurate and less erratic, but it means that it is less reactive to changes in pace. If you are using the average over 10 seconds and suddenly change pace then it will take the full 10 seconds for it to reflect the new pace.
It is a difficult decision to calculate the window over which the pace is calculated, which is why the app leaves it to watchOS. However the smoothing slider does allow you to effectively increase the window, but also make it less responsive.
Would be helpful to know how big „n“ is when the slider is completely on the right side.
Also is it known with what frequency Apple records data? Is it also once per second like Garmin does?
3s pace on a Fenix 3? That was one of the worst watches I ever owned from Garmin. Maybe I had a Monday morning unit…
Also is it known with what frequency Apple records data? Is it also once per second like Garmin does?
3s pace on a Fenix 3? That was one of the worst watches I ever owned from Garmin. Maybe I had a Monday morning unit…
Definetely you had a Monday morning unit…
Use the Fenix 3 since 2015 and they work perfekt. The Fenix shows the pace correct and I run from 10k over 21k, 42k and Ultra with this Watch.
No problems.
And now with the ultra extensive Ultra I can‘t run a competition because I don‘t know how fast I run 😡
Because the Watch, watchOS or WOD can handle this correct.
And pace is the important metric I need.
I‘m really pissed.
I can tell! Your problem is not because watchOS cannot give a good current pace but because a bug in the iOS/watchOS permissions system is stopping you from using the pedometer pace. The pace from the pedometer is the default and is usually fine, but unfortunately you can't use it because the iOS bug is not showing WOD as an option for the Motion & Fitness permission.
The most likely solution to this is to reinstall the iPhone app. Again it is very rare that I have to suggest that (maybe only once or twice a year!), but unfortunately you have tried everything else. The problem is that you will lose the app's data if you reinstall the iPhone app. The usual solution for that is to backup the data to a computer by using Apple's File Sharing and then restore it from there. However you don't have access to a computer.
It sounds like you are angry enough to not care about losing the data in WorkOutDoors so it may be worth reinstalling the iPhone app. If so then uninstall it; reboot both the watch and the iPhone; and then reinstall it. All the workout data is safely stored in Apple's health system so it would still be available in their Fitness and Health apps. You just won't be able to see it in WOD after you reinstall the iPhone app.
If the Motion & Fitness permission is available after the reinstall then the app will use the pedometer pace by default and that may be ok for you. Maybe.
I haven't heard of anyone using a Levo ebike, but if it supports the standard Bluetooth Cycling Speed and Cadence protocol then it should work with the app.
You asked if there were serious runners here but then say you can't complete a long run because you don't know how fast you are going. I'd say any serious runner would know their pace without a watch. I can easily run anywhere between a 5:30min/mi to an 8:00min/mi within 20sec accuracy on feel alone. I come from Garmin watches and instant pace sucked on all of them without setting it to a rolling pace. I use a rolling pace on WOD and don't really care if it's lagged a little because I already have a good idea of what I am running. Even on intervals I find a 3s rolling pace responsive enough.
The maximum smoothing factor is 10. However each source produces data at different frequencies (that can change from version to version of watchOS), which is why I don't specify it in seconds. It's best to just adjust it until it feels right for you. It doesn't affect any of the average pace values.
I have just heard from one of the app's beta testers that Apple have fixed the bug where the action button on the Ultra stops working if you reboot the watch. He has found that it works fine with the latest beta (3) of watchOS 9.2.
Apparently the first time you use the action button after a reboot it takes about 10 seconds to react, but after that it is back to normal, so I guess Apple needed to do some extra processing after a reboot in order to fix the problem.
I only have one Ultra, and I want to keep that on the current release version, so it would be great if anyone else could confirm this?
This means that I can’t release the next version of WOD until Apple release watchOS 9.2 (rumoured to be December), but at least I don’t have to waste any more time trying to fix the problem. I have already spent weeks (possibly months) trying to get the action button working, but I can now focus on the always on display and the navigation improvements.
Apparently the first time you use the action button after a reboot it takes about 10 seconds to react, but after that it is back to normal, so I guess Apple needed to do some extra processing after a reboot in order to fix the problem.
I only have one Ultra, and I want to keep that on the current release version, so it would be great if anyone else could confirm this?
This means that I can’t release the next version of WOD until Apple release watchOS 9.2 (rumoured to be December), but at least I don’t have to waste any more time trying to fix the problem. I have already spent weeks (possibly months) trying to get the action button working, but I can now focus on the always on display and the navigation improvements.