To get the 'best' HRM reading from this 10 minutes, or the reading from the last 10 minutes, or 0... and maybe even updating based on the HRM event.
But the best way would be to use the new clock_info module instead as this handles it properly now, and we can keep it updated if we spot issues like this in the future.
It seems many clocks report HRM and use this pattern:
But this returns the best HRM in the last 10 minutes - so it won't update for between 0-10 minutes.
Probably what's needed is really:
To get the 'best' HRM reading from this 10 minutes, or the reading from the last 10 minutes, or 0... and maybe even updating based on the HRM event.
But the best way would be to use the new
clock_info
module instead as this handles it properly now, and we can keep it updated if we spot issues like this in the future.Affected:
lcars
advcasio
cassioWatch
entonclk