@NeilB23 wrote:
Should be an interesting test & result. I too have experienced exactly what you have so a post test update would great please? (I have switched to Samsung Health on my phone to track runs & cycling)
So, test was completed. These are the exact steps I took.
- Turned OFF all toggles under 'Activities to auto-detect' in the Samsung Health Watch App. These were previously disabled by me when I got the watch last year, but sometime between then and now it seems to have reset. I left 'Alerts' and 'Record location' toggled ON.
- I was unable to turn off the auto-detect workout option in the Samsung Health Phone App even after re-syncing my watch to my phone - it was disabled:
You can see how the toggle is greyed out here
I will come back to this...
- Opened the Samsung Health Watch App -> Record Your Workout -> Workout Out -> Running: 10.00 km. (This is a custom workout that I added months ago and had always previously worked for me. Location and High Location Accuracy toggled ON. Autopause toggled OFF. Guide every 1km. Screen always on OFF).
- Before tapping to start the Running: 10km, I waited for the GPS icon and the HR icon to stop flashing. GPS locked, HR number displayed. I waited another few seconds, then tapped to start workout.
So far, so good. 1km went by... all good! 2km went by... omg is it fixed?! 3km... wait, where's my 3km buzz? I looked at my watch - the workout screen with my pace, cadence etc had disappeared. I was back on my watch face with the little icon of the running man in the bottom of the screen. Test failed.
Throughout the rest of the run he was there on the screen. I didn't tap on it this time as I didn't want to freeze my watch up. I completed my run, thankfully Strava on my phone had tracked it accurately, minus HR and cadence.
I synced my watch to my phone - apparently the workout stopped tracking at 2.43km. At some point the running man icon mysteriously vanished from my watch screen.
In conclusion, it clearly isn't an auto-detect issue from the watch's side - everything was disabled. It's not a GPS/HR lock issue because I waited for that.
What about if it's a phone issue? Have any of you run without the watch connected to a phone and experienced this?
My new theory is that it works until the phone auto-detects a workout (which we seem unable to toggle OFF - @TessM ?) and then the phone tries to sync it's auto-detected workout to the watch, which ultimately results in Samsung Health on the watch crashing as it's already got a workout in progress... Just another theory.
Anyone experiencing this issue whilst cycling? Tomorrow is my rest day for running so I won't be doing another running test tomorrow, but perhaps cycling.
