Real Life Battery Performance

It didn't make any difference - today again 10% for 1hr run. Mix of mapping screen and custom screen with distance to and name of next waypoint.

I did a factory reset. Interestingly this doesn't remove any installed maps.

Run today for 16km and 1.5 hrs and used 12% - so 8% per hour of activity with navigation with beta version 2.96

This is much better after the reset but still only projected to get 12hrs total time.

Hi,
Does the number of ANT+ sensors paired affect the battery ?
Comming from a F3, I see that F5X is consuming much more during an activity.

In my case, I've only done 1 full recharging cycle. I'll take real conclusions after the 10th ...

Hi,
Does the number of ANT+ sensors paired affect the battery ?

Probably it does. But to what extent is difficult to say.

My impression is that the battery drain is ok when the F5X is used only as a watch. However, during activity I think the battery level drops pretty fast.

For reference:
bike ride, 107 km, 4 hours 20 minutes,
battery drop: from 100% to 55%, that is a 45 % drop
GPS: GPS only (no GLONASS), 1 sec recording
ANT+ : external HRM only
Bluetooth enabled and phone connected.
Navigation: none, very little use of the watch and menus etc during the ride, no backlight.
Maps: 3rd party OSM maps loaded and enabled but not in use during the ride.
FW: 2.60 (I have the APAC version)

So for my case it was approx 10% drop per hour.

Now the watch has updated to FW 2.90 and I'll see if that has any impact on battery usage.

Saw a pretty massive drop after a 2:30 run but not sure of the exact charge although I'd charged it a couple of days before.

Last night ran for 30 minutes and burned through 6% battery. So 12% an hour or less than 10 hours GPS run time.

Running beta 2.95 with a Stryd paired as footpod only.

I've lost 3% in the last 15 hours in watch mode, no bluetooth.

I wonder if your Stryd pod is the culprit......

When I did my run at the weekend my Stryd was not paired (or near) and the data field had been removed. My next run tomorrow will be without Stryd/data field so will get an idea then.

You can try this charging process below and see if it improves. Can't hurt it in any case. This was reported back in F3 forums for the same large and fast battery drain issue.

Do a master reset (20s holding 'Light' button), upon reboot plug it in and charge to 100%
Make sure its 100%
Battery drains are more todo with the OS misreading the battery charge and safe gaurds preventing over charging - but the prob is the OS has misread the charge and believes it to be higher than It actually is ( not exactly sure how but its something to do with capacitors), and it disables charging when battery coukd be 1/2 empty ( visually it appears the watch is still under charge but at 100 but behind the scenes charging is off!)
Master reset removes the caching effect and forces a full proper recharge.

From 100'% to 42% for a 10 hour "run"

Last weekend, I "run" (walked) through the alps. I loaded the 5X to 100% before the event.
I used "GPS" tracking (no GLONAS, no ULTRATRAC, no maps). I activated the optical HR sensor and bluetooth as well.

- After roughly one hour, the battery dropped to 92%
- After 10 hours,I realized that the battery dropped to 42%, so I was probably too fast for the watch ;)

Pretty nice...

Best regard, Uli

Even worse tonight - same settings on 2.96 but without my Stryd....ran 34:49 and it went down 8.9% according to battery gauge.

Going to try 3.21 beta.

I'm going to run tonight and will take a pic of the watchface with power level before I start and when I finish; it'll be reasonably short though (~5k) so 25ish minutes, but it does extrapolate in my experience.