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
Not in the near future, but at some time I do plan to revisit the sensor functionality and will probably add it then.
However it probably won't be until after I have improved the navigation and added the ability to create custom activity types, both of which will be a lot of work.
I would need to investigate to have an idea of how difficult shortcuts would be. I used that area of watchOS when I added support for the action button last year, and that was far more difficult to implement than I expected for simply detecting when a button had been pressed.
Part of the problem was that there was no documentation on the action button at the time, so supporting a well-documented feature like shortcuts now probably wouldn't be as bad. However my experience with the action button means that I am in no hurry to look into that area of watchOS anytime soon. Sorry about that.
Hello, first of all, thank you for this wonderful app. I have a question/issue regarding the app and Stryd footpod.
I have tried it yesterday for the first time, paired in the WorkOutDoors app and the sensor data was being read just fine during my run. But after the run I discovered that data for vertical oscillation written from WOD to Apple Health contained mostly values around 7-8cm but also more than 2000cm on many occasions, which is obviously totally incorrect. And it messed up my average to the point that now it seems than I run like a kangaroo
.
I have not tried to use the Stryd app on the watch itself yet (as I really like the WOD and I don't want to stop using it) so I am not sure if this is something to do with the WOD app or my Stryd unit is faulty. Is there anybody else using this app with the Stryd footpod having similar issue? Can this be a bug in the app? Thank you
PS: I have found a message in this thread here that this should be fixed in the future WOD version somehow, was it? I have the version 5.2.7 installed on my watch.
I have tried it yesterday for the first time, paired in the WorkOutDoors app and the sensor data was being read just fine during my run. But after the run I discovered that data for vertical oscillation written from WOD to Apple Health contained mostly values around 7-8cm but also more than 2000cm on many occasions, which is obviously totally incorrect. And it messed up my average to the point that now it seems than I run like a kangaroo
.I have not tried to use the Stryd app on the watch itself yet (as I really like the WOD and I don't want to stop using it) so I am not sure if this is something to do with the WOD app or my Stryd unit is faulty. Is there anybody else using this app with the Stryd footpod having similar issue? Can this be a bug in the app? Thank you
PS: I have found a message in this thread here that this should be fixed in the future WOD version somehow, was it? I have the version 5.2.7 installed on my watch.
Last edited:
And I also found the answer (I overlooked it, sorry for that) so now it all makes sense and it is quite sad they are unable to provide the help. But I hope they will help you out eventually.Hello, first of all, thank you for this wonderful app. I have a question/issue regarding the app and Stryd footpod.
I have tried it yesterday for the first time, paired in the WorkOutDoors app and the sensor data was being read just fine during my run. But after the run I discovered that data for vertical oscillation written from WOD to Apple Health contained mostly values around 7-8cm but also more than 2000cm on many occasions, which is obviously totally incorrect. And it messed up my average to the point that now it seems than I run like a kangaroo
I have not tried to use the Stryd app on the watch itself yet (as I really like the WOD and I don't want to stop using it) so I am not sure if this is something to do with the WOD app or my Stryd unit is faulty. Is there anybody else using this app with the Stryd footpod having similar issue? Can this be a bug in the app? Thank you
PS: I have found a message in this thread here that this should be fixed in the future WOD version somehow, was it? I have the version 5.2.7 installed on my watch.
I am not holding my breath! However no-one has mentioned that problem for over a month, so I had hoped that the workaround that I included in the latest version of WorkOutDoors had fixed it.
Is the WOD watch app up to date for you (v5.2.7)? Apple usually don't update the watch app when you update the iPhone app, which is very annoying. To check go to the Settings on the watch app and tap More and then scroll down to the bottom. Do not trust the version of the iPhone app because, as I say, Apple often do not update the watch app when the iPhone app is updated.
If the watch app is not v5.2.7 then please go to the App Store app on the watch and install it from there.
If the watch app is up to date then please could you email the wkt file for that workout to info@workoutdoors.net. To do this tap the Export button 3 times quickly. I will see if I can spot what strange values I am still not ignoring.
Hello! I'm having a problem, maybe a bug, for some weeks since the Always On support update I guess. I set double and triple tap do interact with map (for zoom in/out) since I use the crown to change screens, and it used to work fine. But this configuration is not working anymore, I spent sometime looking o the shortcut settings and it looks all right to me. Has anyone face this problem too?
Attachments
Sorry that is a bug in the current version. It doesn't handle shortcuts for zooming so you can only use the crown.
I fixed it a while ago in the code, so it should be ok in the next version of the app, which will probably be released early next week (in time for when Apple release watchOS 10.1, because otherwise everyone's times will disappear!).
Hi @cfc I just upgraded to a new iPhone and migrated my data without issues. I then was prompted to pair my watch 8 to the new phone.
I opened the WOD app on the iPhone and can see all my workout history. However when I open WOD on the watch, there is no history and all of my preferences / screens are gone.
Is there a way to restore please?
I opened the WOD app on the iPhone and can see all my workout history. However when I open WOD on the watch, there is no history and all of my preferences / screens are gone.
Is there a way to restore please?
You can send the data from the iPhone app to the watch app by going to the Settings tab and tapping File Management and then "Send Yesterday’s Watch Settings", "Send Screens to Watch” and “Send Interval Schedules to Watch”.
If you want then you can also send routes or workouts individually. They can’t all be sent at once because they are too large.
Thanks @cfc. FYI sending yesterdays settings kind of worked. Showed the right workouts on the Home Screen but the screens are still different to what is in the WOD app. See example cycling screen screenshots. Different on watch vs what’s on phone. (Phone data is correct
Attachments
Hello,
I have read that, as is logical because of its complexity, you plan to wait several months before releasing a version with navigation, which will include numerous functions such as turn-by-turn, ... but using your app for hiking I think if there could not be a simpler intermediate phases.
I mean, the etrex or oregon navigators from garmin are and have been reference in hiking and biking without needing to do much more than what WoD is already able to do in some ways. Moreover, Coros during the first versions and until recently has not had turn by turn and has served to make a niche for itself.
In the end, what the solutions do is:
- Identify position on the track and detect away from the track: This is already done by WoD.
- Paint track on offline map: WoD does it wonderfully.
- Track statistics and accumulated effort. Wonderfully done
- Identify position on altitude graph with zoom. On the phone, this is already done. It is to move it to the watch, and allow to zoom on the graph.
- To have remaining distance information: remaining distance, remaining elevation gain ... I understand that it is the most complicated of the previous points from what I have read.
I say it to try to help you and simplify the roadmap. I think that the evolutions in WoD can be gradual because small things bring a lot. Other more complex things like turn by turn, can be fine, but it has not been and is not in many leading products in the market.
As said, your app is incredible. Waiting for new releases
I have read that, as is logical because of its complexity, you plan to wait several months before releasing a version with navigation, which will include numerous functions such as turn-by-turn, ... but using your app for hiking I think if there could not be a simpler intermediate phases.
I mean, the etrex or oregon navigators from garmin are and have been reference in hiking and biking without needing to do much more than what WoD is already able to do in some ways. Moreover, Coros during the first versions and until recently has not had turn by turn and has served to make a niche for itself.
In the end, what the solutions do is:
- Identify position on the track and detect away from the track: This is already done by WoD.
- Paint track on offline map: WoD does it wonderfully.
- Track statistics and accumulated effort. Wonderfully done
- Identify position on altitude graph with zoom. On the phone, this is already done. It is to move it to the watch, and allow to zoom on the graph.
- To have remaining distance information: remaining distance, remaining elevation gain ... I understand that it is the most complicated of the previous points from what I have read.
I say it to try to help you and simplify the roadmap. I think that the evolutions in WoD can be gradual because small things bring a lot. Other more complex things like turn by turn, can be fine, but it has not been and is not in many leading products in the market.
As said, your app is incredible. Waiting for new releases
I plan to revisit the sensor functionality at some time in the future and add water temperature and various other sensors. For example radar sensors on a bike, outdoor temperature sensors etc. I will also support reading cycle sensors at that time (at the moment the app can connect to them and write the data but not read via watchOS). I may also investigate the Apple weather data at that time and decide whether that would cost too much or not.
However, as usual, other features are higher priority at the moment. Sorry.
Note that the green compass will not appear until you have moved from the start (otherwise it does not know where to point), so it is not something that you can check when stationary. Could that explain it?
Ideally I would release the navigation functionality in stages, and would do exactly as you describe by adding the "following" functionality first.
However each of the navigation features that I am considering will require substantial changes to the data stored in a route file. So I don't want to radically change the structure of the file and then change it again. In an ideal world I would determine the structure in advance and make it flexible enough and backwards compatible enough to handle all future changes, but things rarely work like that.
It may be that after I have implemented the "following" functions then I feel it is ok to release a version with just them in, but at the moment I am planning to make all the navigation changes in a single release. It will take a long time but hopefully not as long as this year's rewrite for the always on display!
I have just released the latest version (v5.3.4) to the App Store. It now supports the Smart Stack and also has a workaround for the time not appearing when using watchOS 10.1. I am expecting watchOS 10.1 to be released later today, which is why I am releasing this version now.
I have used a phased release, which means that it is gradually released to people who have automatic updates, but you can manually download from the App Store if you want.
If the watch app is not updated when you update the iPhone app then you need download it from the App Store on the watch as well. To check go to the Settings on the watch app and tap More and then scroll down to the bottom. It should say v5.3.4
Support for the Smart Stack meant rewriting all the complications as well so hopefully there aren't any problems with them. The upside is that the app now supports the large complication used by some watch faces.
The Smart Stack and the large complication both show metrics from the most recent workout (with a tiny map if it was outdoors). However you will need to do a workout with the new version for those details to appear.
Currently it is not possible to configure which metrics are shown, but I will probably improve that in the future.
I will probably release another minor version this year if Apple allow apps to use the double tap gesture. If so then I will make it one of the possible shortcut gestures. However I haven't yet heard anything about whether that will be possible.
Otherwise my plan now is to focus on navigation improvements.
I have used a phased release, which means that it is gradually released to people who have automatic updates, but you can manually download from the App Store if you want.
If the watch app is not updated when you update the iPhone app then you need download it from the App Store on the watch as well. To check go to the Settings on the watch app and tap More and then scroll down to the bottom. It should say v5.3.4
Support for the Smart Stack meant rewriting all the complications as well so hopefully there aren't any problems with them. The upside is that the app now supports the large complication used by some watch faces.
The Smart Stack and the large complication both show metrics from the most recent workout (with a tiny map if it was outdoors). However you will need to do a workout with the new version for those details to appear.
Currently it is not possible to configure which metrics are shown, but I will probably improve that in the future.
I will probably release another minor version this year if Apple allow apps to use the double tap gesture. If so then I will make it one of the possible shortcut gestures. However I haven't yet heard anything about whether that will be possible.
Otherwise my plan now is to focus on navigation improvements.
FYI, same problem is still here for me too, but I haven’t kept mentioning it to you because I already have a few months ago. The problem persisted through even a watch and phone upgrade. And the readings are problematic every single run without exception. I imagine the problem is still there for many if not most or all next gen Stryd Pod users, but those who would report it to you by and large already have.
A fun detail about the problem if it helps you investigate why your work around isn’t working: if I auto upload the run to runalyze using Healthfit, the bad readings remain in runalyze. But I get around this by manually exporting the fit file and uploading to runalyze through a browser, and then the numbers are fixed.
Apologies for not reporting the problem to you more often. I certainly didn’t intend to communicate with my silence that the problem was fixed. Is there anything I can do to help with debugging this particular issue?
Last edited:
Hi all
Looking forward to using 5.3.4. I downloaded the new app on the iphone and also reset my iphone and apple watch, but for some reason, WOD (on the watch) is showing 5.2.7. On the iPhone I am on 5.3.4. What is the best way to force update the app on the watch?
Looking forward to using 5.3.4. I downloaded the new app on the iphone and also reset my iphone and apple watch, but for some reason, WOD (on the watch) is showing 5.2.7. On the iPhone I am on 5.3.4. What is the best way to force update the app on the watch?
I will have another go at working around the ground contact and vertical oscillation values from Stryd at some some time in the future but at the moment I am focussed on watchOS 10.1.
If I can't work around it then I am tempted to just remove ground contact and vertical oscillation from the data received from Stryd. It would be better not to have the data than for it to not be correct. Or maybe get those metrics from watchOS even when using Stryd for other metrics.
However the number of emails that I get from people using Stryd has dropped massively in the last year (since watchOS 9 added power, ground time and vertical oscillation), so it is lower down my priorities these days. Sorry about that.
If the watch app is not updated when you update the iPhone app then you need download it from the App Store on the watch (not the one on the iPhone).