Related
Options

Running cadence shown as half of steps/min after 19.20 update

FahadUsman
over 3 years ago

I have Fenix 6s Pro, and recently (most likely after 19.20 update) I have noticed that during running acitvities the watch shows cadence as half of what it usually shows. For example it shows 85 instead of usual 170. However after completing the activity, it shows correct cadence in garmin connect app. I have noticed this both with and without the HRM chest strap. Did anyone else also notice something similar?

  • 0 over 3 years ago in reply to lj50

    I looked back at my first run with Stryd and the Stryd Power IQ data field in May 2019. With the run recorded by my 5X+ the IQ cadence was wrong all the way back then.

  • 0 over 3 years ago in reply to lj50

    I agree it is a nuisance and frustrating.

    Good question. We provide the Connect IQ tools to interested developers. The developers then write Connect IQ APPS and they must maintain their APPS and update them as needed. The Connect IQ developers may not always realize there is an issue unless their user base reaches out to them to let them know through the Contact Developer option on their APP page. As software constantly evolves, the Connect IQ developers will update their APP.

  • 0 over 3 years ago in reply to Garmin - Chris

    Chris, with respect, that isn't an answer tomy question. 

    These apps reported cadence correctly pre 19.x. And if you backdate to 16.70 then they report correctly again. So the change was introduced by Garmin. 

    My question was whether you advise developers of changes prior to making them, or do you just rely on the “frustration and irritation” of your customers leading them to contact app developers to point out that Garmin has changed something and as a result there is now “an issue”.

    As much as I appreciate you taking time to reply, if I’m honest, your answers are coming across as deliberately evasive which I don’t think should be the tone you’re aiming for. 

  • 0 over 3 years ago in reply to lj50

    No. We do not contact the developers. The Connect IQ developers may not always realize there is an issue unless their user base reaches out to them to let them know through the Contact Developer option on their APP page.

  • 0 over 3 years ago in reply to Garmin - Chris

    This thread should be move to the CIQ Bugs however would correct but where in the ConnectIQ API document mentions the Activity.Info.currentCadence is 1/2 the actual value.   

    The Activity.Info.currentCadence is providing the wrong value 1/2 the value that is available to the Sensor.Info.Cadence.

    Sensor.Info.Cadence is correct.

     The CIQ libraries are separated from the the watch firmware, so what you would observe in the base datafields would be different than the CIQ datafields.

    If you are unaware of CIQ, I suggest to send to the CIQ team  . 

  • 0 over 3 years ago in reply to Garmin - Chris

    Ok, so to be clear: Garmin does not think it should advise developers of apps that run on its software to make them aware in advance of changes that may affect the features and functions those apps provide to Garmin’s customers. 

    I, for one, would suggest you revisit this policy. There is a world of difference between “not always realising there is an issue” and “Garmin have effectively broken the application without warning”. I also repeat that I think it is disingenuous of you to phrase your replies in such a way as to give the viewer the impression that the app and its developer have caused "the issue”.

    Thank you again for taking the time to reply. 

  • 0 over 3 years ago
    FahadUsman said:
    I have noticed that during running acitvities the watch shows cadence as half of what it usually shows.

    This issue is also discussed in the ciq forum

    https://forums.garmin.com/developer/connect-iq/f/discussion/274158/has-the-currentcadence-handling-changed

    According to the outcome in this thread it's odd only with ciq sdk 3.2.6 . I guess devs have to fix this only for this sdk 3.2.6 .

  • 0 over 3 years ago

    Same issue here. The cadence is halved on the watch while running, but it shows up correctly (as least seems to be) in Garmin Connection. I assume its an app / dev issue. I hope there will be updates from developers soon to resolve it. 

  • 0 over 3 years ago in reply to stockae92

    This is a bug in the FW, has been ID'ed as such and allready fixed in the 6.33 beta firmware for the va4 and venu.

    From the va4/6.33 change log:

    • Fixed an issue were cadence values were halved in Connect IQ data fields

    Please don't blame the CIQ app developers, as it's not their bug.