It shows the quality of the software developers working for Garmin as they are not able to solve this issue within 2 weeks (or even more) since it was discovered...
Strava does show the cadence data by the way. I'm using that together with some friends that do not own a Garmin device.
I would say it shows more about their defect priority system if it has not been fixed. I would say this bug is quite low down the list as it is not critical, it does not cause a crash and has an easy work around. Compared to some issues such as not uploading rides and synchronisation issues i think this would not be as serious.
Imagine the outrage on here if they did not fix some of the issues of not uploading workouts, courses because their engineers were fixing an issue to show cadence data that you can get back by toggling a field yourself.
Hello same problem here. I've a fenix 2. I made a comparison between two tax files, one from my fenix 2 the other from a 620. The file from fenix 2 includes <MaxRunCadence> and <AvgRunCadence> tags, It does not include the <RunCadence> tag (which is available in the 620 file). I think this might be at the origin of the missing chart on my F2 detailed activity page. Of course Avg values are there and correctly displayed. My firmware is up to date. Hope it helps.
Hello same problem here. I've a fenix 2. I made a comparison between two tax files, one from my fenix 2 the other from a 620. The file from fenix 2 includes <MaxRunCadence> and <AvgRunCadence> tags, It does not include the <RunCadence> tag (which is available in the 620 file). I think this might be at the origin of the missing chart on my F2 detailed activity page. Of course Avg values are there and correctly displayed. My firmware is up to date. Hope it helps.
