I have issues with the app 'rowing after the software update. It doesn't show the speed anymore (on the watch when recording and in the connect app). Also distance per stroke doesn't work.
I have issues with the app 'rowing after the software update. It doesn't show the speed anymore (on the watch when recording and in the connect app). Also distance per stroke doesn't work.
You don’t need a pc. Just log on your garmin connect account with Firefox, chrome, safari, on your phone or tablet…
On the top left corner you should have a square dedicated to your venu2
you should have something saying ‘join the beta version’
here is a screenshot made on an iPad (sorry it’s the French version)
I've just enrolled on the beta program, but its still saying 10.18 is the latest available version. Does it take a while for the beta updates to become available after enrolling? Is it still possible to install beta updates manually?
connect it via cable to a PC and Garmin Express... it will immediately install the new Beta
I did that, but it changed nothing. I did not get the beta version. However, we now have a new version, will test it tonight for the rowing app. thanks!
WOULD YOU PLEASE SO KIND SOMEBODY AND TRY THIS FINALLY!!!! If you start a SUP activity (no need to be a real SUP activity, just start it with a GPS) then you see the same "AVARAGE_DISTANCE_PER_STROKE" datas on the watch's screen just before you stop and finish the activity than on the Connect after saving???
No need to yell! Jeez, we are all just users, no paid staff. Anyway, the issue for rowing was solved with the latest update. I don’t have time to look at my watch during rowing, so I do not know if the values change between workout and saving and viewing on the mobile app. Sorry, I can’t be of help. I don’t really see the summary of the workout on my watch. Not like I could with the vivoactive.
I don't think I asked too much, it is just a simple test for anybody. This is what community for to help each other. Otherwise if more people notice and comment to Garmin it maybe they fix this, because I'm sure this is a SW bug and not only my watch is affected.
And not only Avarage_distance_per stroke is problematic, the current and the interval distance_per_stroke are either.