This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cadence is halved during a run since 6.10

Since updating to 6.10 on Friday anytime during a running activity, my watch seems to be halved for cadence IE it should be 170 but instead says 65. I went back to using my Vivoactive 3 since its hard to run with it that wrong, but my wife has a 4s and had the same issue this morning after she updated yesterday ( worked fine on older software on Saturday, updated a day early ). When she finished her activity (cadence isnt as important to her), she noticed it was fine in the app.

I did some googling and i plugged it into my PC, made sure everything was even more up to date, reset and wiped all settings on it ( which was fun itself, thought i bricked it ) and reset it up from scratch except it looks like the software didnt reset to an older version. Anyone have the same issue or have anyway to roll back the software version to 5.80 where it seemed to work?

Doug

Top Replies

All Replies

0 ovekvam over 3 years ago

I haven't been looking at the cadence on the watch face when running after installing 6.10, but the cadence looks perfectly normal on the graphs in the training logs. Do you have screenshots of your graphs? Or is it only an issue with live values on the watch face?

0 sensovision over 3 years ago

Hey Dough, I'm referring to cadence during runs myself and although I've number of different issues with 6.10 I don't have the issue with cadence, at least so far, which is weird. It seems to show the correct one for me. I wonder if you're using foot pod with the watch? as I know that some may show only halved results.

0 6477596 over 3 years ago in reply to ovekvam

its only an issue with the live values on the watch face during a run. the graphs show up fine

0 6477596 over 3 years ago in reply to sensovision

no foot pod, just the watch. i'm also using the single field IQ face for running, I'll have to try one with the regular default.

0 sensovision over 3 years ago in reply to 6477596

yeah, maybe datafield is the culprit, in fact my Cadence datafield which I've bought previously stopped logging any data for walking, so i removed it. Maybe yours have issues after the update too as Garmin changed API or something.

0 gwonke over 3 years ago

I have the same issue. Using the MapIT datafield. Haven't tested this with the normal Garmin datafields yet.

0 6477596 over 3 years ago in reply to gwonke

It looks like its the custom datafield, i tested with regular garmin datafields and it works so thats a lifesaver! i personally contacted the developer to let them know, i guess they may all have to change it?

0 sensovision over 3 years ago in reply to 6477596

thanks for testing it, I'll do the same for the datafield I've used.

0 BenjaminH over 3 years ago

Hey everyone, thanks for bringing this up! Just wanted to let you know that I have created a bug report on the Garmin Developer forum for this issue, which can be found here:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/halved-cadence-values-after-update-to-6-10-for-ciq-datafields-on-vivoactive-4-4s

Hopefully it will get rectified soon! If not, I'll update MapIT within the next few days. I am just wary of quickly updating to correct the cadence values, only for Garmin to also change it on their side and then the datafield again gives the wrong values. I'll repost any updates from the bug report to here as well.

Cheers,

BenjaminH

0 albifac91 over 3 years ago

Same problem! 6.10 update is the worst ever. Completely full of bugs