Hello! I got my Venu Sq 2 less than 6 months ago and, for the most part, I really like it even though it is an older model.
However, it seems to (still) have a bug. I looked into the archives and found that this same bug 1) existed over 5 years ago and 2) the person who posted the problem seemed to get some bad information from the Garmin person who was supposed to be helping her.
Here is the post in the archive from over 5 years ago: forums.garmin.com/.../bug-with-body-battery
Because of settings I've chosen, I need to charge my Venu 2 Sq about every 4 days. This is not a problem as I know I am having it work a little harder so the battery drains faster. The problem is that the past 2 times that i have charged it, when I've taken it off the charger, the HR monitor has stopped working. That means that HR and Stress are not tracked. This is frustrating in itself.
So, the fix to get the HR sensor working at all has been to SOFT reset it (press the A button for a couple of seconds, the screen that includes the power button appears, I press the power button, the garmin shuts off and then I press the A button again for a few seconds which produces the blue triangle and then the HR sensor works again). Kind of a pain in the kiester and I sure hope it doesn't start doing this EVERY time I need to charge it.
The weird thing for me (as also mentioned by the person who reported this same bug over 5 years ago) is that my body battery jumps from where it was when I started charging up about 25 points. So, when I started charging this afternoon, my body battery was at 5 and after I SOFT reset the garmin about 15 mins ago - almost 10 hours after charging, the body battery reading was false... by a lot.
I keep emphasizing SOFT reset because what I describe above is a soft reset. I know this because I read an article differentiating the 3 kinds of resets: www.wareable.com/.../how-to-reset-garmin-watch-7324 I'm NOT resetting default settings and neither was the person who originally made the post reporting the bug.
So, I am now continuing the tradition (?) of reporting this same bug... over 5 years later. It would be great if it could be fixed.