After so many revisions, the HR stuck issue is still not fixed.
I am thinking if it is hardware issue now.
For some people it may be; I saw the 66 back on 2.3, but power cycling would solve it until the next time I charged. Haven't seen it again since installing 2.40. Since it is working I didn't install the beta and will probably wait on installing 2.50 for a few days.
If I had a watch that 2.5 hadn't fixed that issues on, I'd be swapping it out at my retailer. Probably just return and rebuy actually, to reset the return window.
I updated to 2.50, and noticed I now have a box outlining my HR readout. Anybody else have this?
Updated mine this morning, and it seems to be sampling HR more frequently/better, but maybe too early to tell.
I have my fingers and toes crossed though :p.
Keep us up-to-date. Increased sampling frequency doesn't seem to be on the list of improvements, but who knows. Since my watch is working fine i think i'm going to hold off a few days before updating.
But why does the update have to change my watch time so I have to go outside and get a GPS lock to reset it. Also calories now seem wrong for the day and the HR trace has disappeared. Looks like another day of messed up readings :-(
