Don’t know about the Garmin pod but Stryd shows both GCT and VO in the workouts with the updated WOD.
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
Unfortunately Garmin’s Running Pod only supports ANT+. It doesn’t support Bluetooth so it is not compatible with the Apple Watch.
If you use Stryd then the watch can connect via Bluetooth and the app will show all the running dynamics that it provides, including those you mention.
Thank you very much for your answer. RDP is cheaper than Stryd, but it's too bad. After pairing the stryd with AW and then moving to the WOD, does the WOD app record information such as ground contact time measured by stryd, vertical amplitude, etc. directly?Or is it recorded separately in the Stryd app?
It is recorded in WOD and can be displayed during the workout and analysed afterwards, just like the other metrics.
Over the weekend I used WOD in map-only mode with a route loaded and my battery was at 50% after 4.5 hours so happy with that. I was cycling so my Wahoo ROAM was recording my ride. I do have a couple of questions using WOD with my AW 7 wifi:
1. Often when I would look at the map, the location arrow was often pointing towards me instead of forward. After several lower and raises of the wrist it would point forward. I have Map Orientation 'Compass' and GPS Arrow Orientation 'Direction of Travel', so I think my WOD settings are correct. Anyone else see this? Does maybe my compass need calibrated, and if so, any suggestions?
2. It started to rain pretty good in the middle of the ride, and I wanted to put my watch in Water Lock mode. I couldn't figure a way to do this while in map-only mode. Is it possible to do this and still see the WOD map? I ended up putting the watch into Water Lock from swiping up using watchOS, but then the WOD map didn't show. My phone was in my bag to keep it dry so couldn't use it.
1. Often when I would look at the map, the location arrow was often pointing towards me instead of forward. After several lower and raises of the wrist it would point forward. I have Map Orientation 'Compass' and GPS Arrow Orientation 'Direction of Travel', so I think my WOD settings are correct. Anyone else see this? Does maybe my compass need calibrated, and if so, any suggestions?
2. It started to rain pretty good in the middle of the ride, and I wanted to put my watch in Water Lock mode. I couldn't figure a way to do this while in map-only mode. Is it possible to do this and still see the WOD map? I ended up putting the watch into Water Lock from swiping up using watchOS, but then the WOD map didn't show. My phone was in my bag to keep it dry so couldn't use it.
The location arrow is calculated from the direction of travel, which requires a GPS history. In map-only mode the app will only keep the GPS on for up to 5 minutes (by default) if you do not use the app. So if you look at the map after 5 minutes of not using it then the arrow direction will reset and the breadcrumb trail will disappear. Could this explain it? If so then you may want to set the "Keep GPS On For" to a longer time than 5 minutes.
There isn't a way to put the watch into water lock from the watch app when in Map Only mode. However you could set up a shortcut gesture to do it, such as quadruple tapping the screen.
So the WWDC keynote was interesting with regards to the built in Workout app. It will be interesting to see if WOD can leverage any of the new metrics (vertical oscillation and ground contact time).
Hopefully. It looks like apps can request them in the same way as other metrics. I have had a look at the watchOS 9 code and running power is also mentioned (as well as being briefly displayed in the keynote), so that is also promising.
These metrics are already implemented throughout WOD (for Stryd) so in theory it shouldn't be difficult to read them from watchOS 9 for people without Stryd.
I have a question about HRV.
I have paired my H10 successfully. I can see my HRV. The average appears in the workout tab.
However, HRV does not seem to be exported in the FIT file? Am I doing something wrong or is there a reason? I'm asking because I'd like to have the data to analyze.
@cfc This is a spectacular app!!!
I have paired my H10 successfully. I can see my HRV. The average appears in the workout tab.
However, HRV does not seem to be exported in the FIT file? Am I doing something wrong or is there a reason? I'm asking because I'd like to have the data to analyze.
@cfc This is a spectacular app!!!
Wow what an eventful WWDC for Apple Watch fitness enthusiasts! I'm the person who recently requested multisport mode, and..guesswhat!
DCRainmaker: Apple Watch Adds Native Running Power & Triathlon Support: All New watchOS 9 Features Detailed
Woohoo! I imagine it will be fairly straightforward for WOD to use Triathlon mode since it will be a native workout function. That's awesome!
Also:
Did the conference shed any light on AOD vis a vis SwiftUI?
DCRainmaker: Apple Watch Adds Native Running Power & Triathlon Support: All New watchOS 9 Features Detailed
Woohoo! I imagine it will be fairly straightforward for WOD to use Triathlon mode since it will be a native workout function. That's awesome!
Also:
- Native running power on the wrist (I'll still use Stryd pod, but still: neat!)
- Kickboard swim detection. This makes me unreasonably happy
- Advanced running metrics
- Dogs and cats in Portrait Faces!
Did the conference shed any light on AOD vis a vis SwiftUI?
Wow running power from the wrist with an Apple Watch would be a game changer. And triathlon mode. Does Apple native workout app having triathlon mode make it easier for you to implement in WOD?
Did they mention about new power safe mode ? I am hoping to boost a little bit battery life for sport usage
Have not seen anything in the presentation and also not in the press release.
Have to wait for the beta reports.
As far as I know the FIT format doesn't include HRV. I think (but am not sure) that it may allow the raw RR intervals to be stored (the times between each beat that are used to calculate HRV), but WOD does not store them because they would take up more memory and I didn't want that for a feature most people wouldn't use. So the app calculates the HRV from the intervals and stores that instead. I may improve it in the future if there is enough demand.
Not yet that I can see, but I am not optimistic. I have resigned myself to rewriting the UI. It will be a lot of work but hopefully worth it in the long run as SwiftUI has a lot of other benefits. I just hope it is possible to do the maps!
Also I suspect SwiftUI will be necessary for the rumoured AR glasses, and I like the idea of writing a version of WOD for them when they appear.
I don't know. Hopefully we will find out later in the week. If it doesn't then it may do in the future as Apple often add functionality to their apps before they make that functionality available to third party apps.
Hi - slightly strange outcome tracking a ride last night... 19.54 miles / 54 mins is correct (also tracked on my Wahoo Bolt), but the GPS data in WOD only has about 3 miles of ride, and then a straight line back to the start/end point.
The export to Strava results in a 2.91 mile ride, although WOD seems to 'know' it was a 19.54 mile ride - and that odd message about -14.08 miles of invalid workout (the Apple Fitness app shows as 19.54 miles / 54 mins with heart rate tracking for the entire 54 mins but only 3 miles or so on the map).
The export to Strava results in a 2.91 mile ride, although WOD seems to 'know' it was a 19.54 mile ride - and that odd message about -14.08 miles of invalid workout (the Apple Fitness app shows as 19.54 miles / 54 mins with heart rate tracking for the entire 54 mins but only 3 miles or so on the map).
That sounds very strange. Please send me the wkt file for that workout and I will take a look. To do that tap the Export button 3 times quickly and send it to info@workoutdoors.net
It is also worth rebooting both the watch and the iPhone in case they have got confused. It sounds like it stopped sending GPS updates but the app uses Apple's distances, which is why it is still correct.
Did you have your iPhone with you on the workout and if not then did you leave it near the start?
Thanks. I have taken a look and I think your Stages power sensor was the cause. It seems to have been constantly reconnecting for some reason, and it looks like that eventually prevented the app from handling the GPS updates. I have never seen anything like it.
The sensor connected 3782 times (instead of the usual once). If you go to the Power tab and change Power to Log then you will see 18000+ log messages about it. This has never happened in all the months of sensor testing, but I never heard of anyone testing with that sensor. Sorry about that. Unfortunately it is impossible to test every make and model of sensor. I recommend not using that sensor until I can look into a fix.
thanks - I was going to report a suspected similar issue with my foot pod - as I could see the 'pace' field alternating between a valid figure and null (empty) with rapidly changing status messages at the bottom of the display when paused (too quick to read, but perhaps something about sensors connecting).
checking the log entry for that run I can see multiple entries for 'Initialising sensor connections' after which the pod is found and then connected over and over - same issue, different sensor.
on the ride the stages crank was connected via ANT to the wahoo unit, with no apparent issues - I've recorded various rides in ismoothrun with a similar arrangement, but WOD is my preferred app ;-) (also with zwift on apple tv - so I don't think the stages unit has any issues with BLE & ANT simultaneously).
I've removed the pairing, power cycled the watch, re-paired and done a short test with the foot pod - showing no issues and a consistent pace data field... seems like a watchOS oddity, although I'd not seen this with ismoothrun previously... but the constant re-connection is probably what caused my previous query about the watch being unresponsive with wrist gestures etc. if it's very busy re-establishing sensor connections ?
at least I know about the log viewer to check again on some more test rides / runs... you did mention you had some updates in the pipeline for the new sensor functionality - hopefully this might address the issue ?