This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Body battery issues on Aviator

Ever since I got my aviator (2 weeks ago) the body battery pretty much flat lines at 6 every day and only increases slightly. My driver was increasing 50 to 70 every night. Anyone else have these issues?

0 meste7 over 4 years ago

and WHR is showing good values?

0 crt_hun over 4 years ago

What about the stress metrics? Is it low and Body Battery still not increasing or the stress is high which could explain the behavior.

0 4543228 over 4 years ago

A system/reset to factory will likely cure it but only temporarily. My Aviator exhibited this little foible last night. BB was in the teens and stress was very high. A reset and stress is in single digits and BB now jumps to 70s. Instantly. That says that the watch (which is doing the computing) is recalculating "old" data and giving new values for BB and stress. So, in my case, the data collected and buffered seems like it might be valid but the algorithm to produce BB and stress has a glitch. I also have a Fenix 6 Pro. Behaves the same way. The Marq was doing pretty well until last night (nearly a full charge cycle). Sometimes a power off/power on will do the trick. A reset always seems to work. But it is a pain frankly. You see it mentioned like background noise on the Fenix 6 forum.

0 Crispin_Ellisdon over 4 years ago

Which software version and, in particular, which sensor hub version is the Aviator currently running? Having folllowed things closely on the Fenix 6 side, there were definite improvements made in metrics derived from wrist HR from sensor hub 5.06 and up (furthermore, there may be tweaks in the latest software 9.00 that leverage the improvements in the latest sensor hub software). The reason I ask, is I know the Aviator software updates can lag behind the others.

0 4543228 over 4 years ago in reply to Crispin_Ellisdon

I am sitting at fw=9.0 and hub=5.07. However, I am not confident that the Aviator software load does not ignore certain pieces of the software. My perception is that Garmin software configuration control is a bit loose. Admittedly I come from an environment where rigor is sacred. The truth is I don't know. Ignoring the quantum world, predictability is the golden rule. The system generates the same result (right, wrong or something) every time. For me, and others, this is not the case. Periodically it goes off the rails. I wonder if the bug is in the software that Garmin licenses for this purpose.