Kcal widget not working correct after update

7710705 2 days ago

After an update on my Fenix 7x sapphire solar i got a issue.

The Kcal widget (the one that shoes active, rest and total kcal plus last 7 days average does not calculate in todays active kcal in the average. Meaning:

It calculates the average of the last 7 days, but sets todays kcal to 0. Regardless of how many active kcals it states, it shows correctly how many is burnt today, but the calculated average has it to zero until the next day. It used to raise the number based on active kcal burnt pr today aswell.

0 trux 2 days ago

TBH, the current state is better than the previous one, because for some strange reason Garmin system is unable to calculate averages over incomplete days (or weeks, months, ...). So for example when they formerly calculated the 7 days average including the incomplete today's data, they simply took the sum of all 7 days and divided it by 7, which, of course, is completely wrong, because if you do that just after the midnight or in the morning (zero or very low kcal), it skews the average significantly (by up to almost 15%). The proper algorithm should convert the elapsed time to seconds, calculate the average per second from the total sum for the 6 complete days + the one incomplete, and only then converting it to the daily average (multiplying the seconds-average by 60×60×24).

Unfortunately, Garmin never implemented the correct way of calculating the averages, and after numerous complaints about the skewed results, they decided for this fast & dirty fix, by excluding today's data completely. Do not ask me why, because calculating the averages in the described way is no rocket science, but apparently Garmin decided differently.

On the other hand, I have to admit that the chosen method makes some sense, and for many users it may be preferable. In this way you see your daily average for the past 6 days, and in the same time you see how far form the average you are today, or whether you already reached it. So, in fact much better than having the original false skewed average.

You can try reporting the issue to the Product Support or suggesting them the proper average calculation method through the Share Ideas | Garmin form, but I am afraid it would need hundreds or thousands of others complaining about it, to make the developers considering the change.