No-one has ever reported that, but it is pretty obscure so may not have been noticed. I will take a look when I get time.
Do you see the same when using the internal sensor of the watch?
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
Do you see the same when using the internal sensor of the watch?
Are you a beta tester? The latest bug fix beta contains a fix for an obscure bug with heart rate averages when using some sensors. It was more about fixing an inconsistency in the iPhone app but the fix involved the way averages are calculated by the watch app.
So if you are a beta tester then the fix may be causing your issue and if you aren't then the beta may fix it (in which case please email info@workoutdoors.net if you want to give it a try).
If it's fine for the watch sensor then maybe go back to the release version and see if it is a problem for that with your external sensor.
I’ve got an intermittent issue, no GPS data and an empty fit file after a run.
Scenario is as follows…. If I start a run as I’m leaving my house, the app will seem to function normally tracking distance / time etc. I do notice a “start anyway” message but that goes away and the 321 countdown starts. Once I get home again, the auto complete function doesn’t work and I get an error uploading to Strava. Fit file is empty so I cannot export.
The app seems more reliable if I leave starting the run until approx. 30 seconds after I leave the house.
This makes me think that GPS signal needs to be available before starting my workout, but I thought Apple Watch “caught up” if it doesn’t have GPS at first? Not a big issue in the grand scheme of things, but should I be checking for GPS before staring a run?
I’ve checked all location permissions / health access etc. and all are as expected.
Scenario is as follows…. If I start a run as I’m leaving my house, the app will seem to function normally tracking distance / time etc. I do notice a “start anyway” message but that goes away and the 321 countdown starts. Once I get home again, the auto complete function doesn’t work and I get an error uploading to Strava. Fit file is empty so I cannot export.
The app seems more reliable if I leave starting the run until approx. 30 seconds after I leave the house.
This makes me think that GPS signal needs to be available before starting my workout, but I thought Apple Watch “caught up” if it doesn’t have GPS at first? Not a big issue in the grand scheme of things, but should I be checking for GPS before staring a run?
I’ve checked all location permissions / health access etc. and all are as expected.
It's always worth waiting for a GPS signal but it's not essential. If the FIT file is empty then something else is wrong, usually an issue with the location permission.
There has always been a bug in iOS/watchOS where watchOS loses permissions despite it looking like it has them. This bug seems to have become a lot more common since watchOS 10. The fix for this is to disable the permission, reboot both devices, and then enable it again. This nudges iOS into sending the permission to watchOS.
The problem in your case is that a permission issue that would mean that you would never get a location for any workout, but your issue varies from workout to workout. However I can't think of any other thing to try, so I recommend disabling / rebooting / enabling.
If that doesn't work then please could you send the wkt file for that workout to info@workoutdoors.net and I will take a look. To do this tap the Export button 3 times quickly.
Sorry if this has been posted before.
I’ve just done a mountain bike ride of approx 2hr 20min using WOD with the always on display on my Ultra. End the end of my ride the battery warning was coming on. I’ve never seen this kind of battery drain before. Note that I did have cellular turned on but with the maps downloaded. I also received a 2 min phone call in the middle of the ride. I was riding with my watch only and so no iPhone to piggy back off. Is it possible that the vibrations of a rough track are triggering the raise to wake and fully lighting up the screen? Do you have any power saving suggestions other than low power mode, which switches off the AOD and reduces gps pings?
Thanks
I’ve just done a mountain bike ride of approx 2hr 20min using WOD with the always on display on my Ultra. End the end of my ride the battery warning was coming on. I’ve never seen this kind of battery drain before. Note that I did have cellular turned on but with the maps downloaded. I also received a 2 min phone call in the middle of the ride. I was riding with my watch only and so no iPhone to piggy back off. Is it possible that the vibrations of a rough track are triggering the raise to wake and fully lighting up the screen? Do you have any power saving suggestions other than low power mode, which switches off the AOD and reduces gps pings?
Thanks
That sort of battery drain won't be due to WorkOutDoors. Even if the screen was constantly on due to raise to wake then an Ultra would last a lot longer than that. Also, excessive raise to wake is much more common with activities like paddling which involve more arm movement. I have never heard of it with mountain biking, but it may be possible.
My guess is that something was wrong with your watch, so I recommend rebooting it before using the app again. It could be that watchOS had got confused, or another app has gone rogue.
You could also look at the log for that workout by going to the final tab in the iPhone app and changing GPS to Log. There should be a message at the bottom of the log telling you how often the screen was active (including a percentage). I checked my mountain bike rides and usually the screen is only active for 2% or 3% of the time for me.
Also if you type "battery" into the "Contains Text" field then you should see battery log messages that show how quickly the battery dropped during the workout, which may help to see if it dropped suddenly (maybe around the phone call) or evenly during the workout.
Thanks for the advice and the very speedy reply.
The log tab is very useful of such information and I had no idea it was there. It turns out that my screen was active for 21 %, which seems quite high. I do ride with the water lock on as a wet sleeve has ended my ride previously. Can the water lock affect the screen waking times? Also of interest was that I only started with 65% despite grabbing my watch of the charger before the ride. Not sure what happened there but I’ll consider it a one off and monitor following a reboot.
Thanks again.
The log tab is very useful of such information and I had no idea it was there. It turns out that my screen was active for 21 %, which seems quite high. I do ride with the water lock on as a wet sleeve has ended my ride previously. Can the water lock affect the screen waking times? Also of interest was that I only started with 65% despite grabbing my watch of the charger before the ride. Not sure what happened there but I’ll consider it a one off and monitor following a reboot.
Thanks again.
The screen being active for 21% is very high and definitely explains the battery usage, especially if you only started with 65% battery and finished with about 10%. I know that kayakers who don't disable raise to wake generally only get a couple of hours with pre-Ultra watches, which is consistent with what you got with 55% of an Ultra charge.
Raise to wake and touching the screen will still activate it, even if water lock is enabled. Disabling raise to wake should help if it is the motion that is causing the screen activation, but if it is a wet sleeve constantly tapping the screen then I don't know how to avoid that. As far as I can remember no-one has ever mentioned that before from a battery point of view. I suspect it is one of those issues that are hard to get around with a touch screen watch.
Will you still take a look at the issue? Seems like the calculation of the average heartrate goes wrong on the notifications when using an external sensor. The average is displayed correctly in the app after the workout is finished.
Did you try it with the latest release version? I suspect it may be an issue in the beta. Thanks.
Well 251 pages read through.. and a week of testing WOD…. and I am sooooo impressed. Great work Ian, and hope you are able to continue working on this for many years to come. It’s a must have app.
I am sure there are more functions, powers under the hood I am yet to find, but did wonder if there is any possibility to have some sort of iPad version, rather than just iPhone? Reason being I find it hard to read/manage everything on a smaller iPhone screen, getting old eh?! Appreciate that this probably isn’t possible given that the link is between iPhone and watch.
I am sure there are more functions, powers under the hood I am yet to find, but did wonder if there is any possibility to have some sort of iPad version, rather than just iPhone? Reason being I find it hard to read/manage everything on a smaller iPhone screen, getting old eh?! Appreciate that this probably isn’t possible given that the link is between iPhone and watch.
Congrats on reading the whole of this thread - that must have taken a very long time!
An iPad version is very unlikely. Sorry about that. As you have guessed the inability to connect the iPad to the watch is the main obstacle because it means that an iPad app would not be able to configure the watch app or analyse the workouts that it produces.
Even if it could connect to the watch then an iPad version would be a lot of work and probably not worth it unless it was requested a lot. Maybe I will implement it one day in the future, but it is not in my short to medium term plans.
It would become more likely if circumstances force me to rewrite the iPhone app in Apple's latest coding language (SwiftUI), as they did with the watch app. SwiftUI makes it easier to write an app that works on both the iPhone and the iPad, so if I had to do that then I would probably consider writing an iPad version at the same time. However at the moment the likelihood of Apple allowing the iPad to connect to the watch and also the iPhone app needing to be rewritten is very low.
Thanks for the reply. 251 pages - yes took a bit of time and had to break it into manageable chunks, 5 pages at a time. But to be honest way too many posts about where is AOD, and now navigation, but your repeated patience in reply comes through in spades. Sainthood there!!
No problem about an iPad version, I completely understand. If it is on the long term/never never list then that is good enough for me. I did have to laugh at myself even asking for it, given that the watch screen is even smaller than the iPhone.
I'm still partly mystified by the lag in updating at the end of a series of swimming lengths. At the end of my swim session I now wait as suggested, for the length counter to catch up (maybe a minute or so) and then wait a few minutes longer hoping for the actual distance to update. But this never seems to update, leaving me still a length short when I end the session, despite the watch displaying the correct length count. Am I STILL too impatient?
@cfc
I have a problem with my cadence sensor.
As my battery was drained I put a new one in. The sensor is recognized by WOD, see settings. But when I start a cycle workout, WOD does not find the sensor.
I have already deleted and reconnected several times, but nothing works.
Have I perhaps set a setting incorrectly?
I have a problem with my cadence sensor.
As my battery was drained I put a new one in. The sensor is recognized by WOD, see settings. But when I start a cycle workout, WOD does not find the sensor.
I have already deleted and reconnected several times, but nothing works.
Have I perhaps set a setting incorrectly?
Attachments
Last edited:
Are you using the latest version of watchOS (v10.2)? There were swimming distance issues with earlier versions of watchOS 10, which Apple fixed in 10.2.
Is the sensor maybe paired to something else? Possibly watchOS, which can now be paired with cycling sensors.