Inconsistent reporting of info.currentCadence across devices (steps in some, revolutions with half the value in others)

info.currentCadence reports to Connect IQ apps steps in some devices and revolutions (or pairs of steps) in others during a Run activity. Even for some devices, the reporting is inconsistent across firmware versions.

The Fenix 6 used to report steps but with more recent firmware reports revolutions, while the Forerunner 735XT continues to report steps. So the Fenix 6 will report a cadence to Connect IQ apps of 90 when the Forerunner 735XT reports 180.

I don't mind either option, but the inconsistency across devices is a pain and leads to many user complaints. It would be great if this could be fixed and all devices reported cadence in the same way. Failing that, even a list of which devices report steps and which devices revolutions when updated to the latest firmware would be useful. I am gradually compiling such a list from users, but it takes time and requires recompiling and updating a new version every time.

From what I have seen, many data fields are affected by this and some have turned to temporary fixes, like letting users choose between seeing cadence or cadence * 2, or (my case) deciding what to show on a device-by-device basis based on what users are reporting their device is doing.