Questions about Widgets / Watch face / HR

Hey, just want to get something confirmed.
As far as i got it, you cant actually show/meassure the actual HR in a watch face, you can just read out the last value from the history?
But on the other hand, when you make a widget you are abel to get the actual HR ?

Stiebsi

Your suspicions are 100% correct.
On a watch face you get a historical value roughly every 2 minutes, whereas on a widget it is almost real-time.

Watch faces have a lot of limitations in order to conserve battery power. The main difference between a widget and watch face is that a widget does not display forever and eventually times out to the watch face in order to conserve battery. A watch face displays more permanently, therefor the restrictions on it.

but when / where is the HR history getting created? And is it possible to change anything of that.
With that i mean time between 2 value, as well as any code that it uses to process the value from the sensor, becuase i have a strange feeling that the values in hte history are a bit off.
Or is this all hard coded somewhere ?

The data is being saved by the FW, at the same intervals used for 24/7 HR. Each reading does have a timestamp.

Note that getHeartRateHistory() is only available on watches with a WHR

becuase i have a strange feeling that the values in hte history are a bit off.
Or is this all hard coded somewhere ?

It is the perception that the historical value is incorrect, because by the time you read the value of the watch face, and you compare it to the widget, the reading is already old. So the widget's reading could be 2 minutes newer. A lot can change in 2 minutes regarding your heart rate, so it is impossible to verify the correctness of the reading.

As Jim said, it is the same as that used by the widget. So if your perception is that the widget is correct, then so will the reading on a watch face be. You just can't verify it because of the intervals that the FW update that.

No that exactly is my problem, the widget is off :) so i was looking in a way to fix it myself as the garmin support isnt very helpfull at all :)

But as the readings come from the FW itself , i guess i ahve no chance doing so

No that exactly is my problem, the widget is off :) so i was looking in a way to fix it myself as the garmin support isnt very helpfull at all :)

But as the readings come from the FW itself , i guess i ahve no chance doing so

I would love to hear more about "the widget is off" part. Please let us know the device and what this issue is. :)

I use a Vivoactive HR and I have not found that there are any issues other than the odd spike or drop in HR values. Overall .. it is pretty stable.

I got the fr235 and at the moment i have the 5.07 beta running on it.

when i use it during running or any time i actually have an activity running, i get perfectly fine values. except for some spikes sometime.
but somehow the rest HR widget is off. when i actually switch from the watchface to the widget, it takes a few seconds to get my right HR, but as soon as i switch back to a Watchface, the resting HR starts to drop.

My real resting HR is around ~110 , ya i know its high and the HR widget isnt really concipated for a 3 digit number anyway... :)

But now as soon as i switch away from the HR widget, the HR that gets recorded in teh history starts to drop, significatnly, to values around 95-100,
wich makes no sense to me. as the sensor seems to work during activitys just fine, maybe a bit slow, but who cares about that.

Now how is that sensor working when im on my watch face that it somehow get wrong values ? somehow when im not in an activity, or in th widget, the Sensor does not work right.
Maybe there is a hardcoded max value for resting HR, the sensor trys to reach.... or some other hard coded algorythm that makes no sense.

So somewhere in this background 24/7 meassurement there seems to be an error.

Maybe you guys know where to look at.

Stiebi