Suunto Vertical 2 General Discussion
-
@Egika
Android
I think it’s because I didn’t finish my workout in Zone 2. I just don’t understand why Zone 2 is a requirement, or rather, I didn’t see that mentioned anywhere in the changelog. -
@masta HR higher than Z1 is required because the lower your starting point, the slower the rate, and no information is gained from that
-
@masta if you end your activity at resting heartrate or just slightly above, there will not be much to measure.
You need a significant enough drop to evaluate a drop. -
@masta Same here. Only two runs since the update but the recovery function worked both times on the watch but nothing showing in the app.
-
@MarkG in android app and with race s you can find it in the workout statistics in the heart rate section.
-
@masta you need to update the suunto app to version 6.8.9
-
@beginson Thanks - only just became available here - I’ve done that now and the app is showing the stat from the previous two runs so all good.
-
@Gunnar Thanks - that’s where I was expecting to see it but an app update has just landed and now it’s there.
-
I’m trying to test the traceback feature. How exactly does the traceback feature work? What are the differences in usage compared to returning to the initial point?
-
@safari
Back to initial point is “direct line as the crow flies”, like bearing navigation.
Track back is taking your “breadcrumb” and make it a navigated route, back. -
@Mff73 Yes, I noticed that it doesn’t base its route on the one I was taking. It redraws the route based on my first pebble point as the crow flies. It’s not really following my imagination. Going back to the first route worked differently.
-
If I end the workout in Zone 2 or higher, heart rate recovery also starts and is subsequently displayed in the app. Everything’s fine. thanks!
-
I charged mine to 100% on Saturday evening, 97% Sunday morning and a 7hr trail run dropped it to 88%. I’m impressed.
What I’m not so happy with is a persistent issue where longer runs don’t seem to sync to the app very well. Most runs I do are two hours or so, sync quickly without issue. Anything 3-4hrs plus seems to cause a problem
The app picks up the watch, syncs everything else but I then get a message saying ‘Problem with last sync, one activity failed to sync’. Then it usually does sync 6-24hrs later. (Still waiting for yesterday’s 18hrs after finishing and numerous attempts).
I’ve tried all the recommended fixes. Does anyone else experience this? I’m beginning to wonder if it’s a Bluetooth fault with my phone but as shorter activities sync without problems and notifications work I’m not so sure. -
@MarkG For me, activities over 9 hours sync normally.
-
@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here.
I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.
