Real Life Battery Performance

So, yesterday I did 75Km race and used my F5X with the following:

Software 2.9, GPS/GLONASS, 1 Second Recording, Navigation against a course, Map page on mostly on, HRM Run belt paired.

The race took me 8:40 and the battery levels on my F5X went from 98% to 5%!

This makes the watch almost completely unusable for ultras over 75K. Might be because of the map page but there's not much point in paying the extra if you can't use it I guess.

Anyone else seen this type of performance? I was expecting to have around 40-50% left when I finished!

D.
  • I raced 50 miles last weekend. 1 sec Recording, GLONASS on, navigating the course with watch in Course mode. 10:30hrs, had 39% left. My buddy had his in smart recording and NO navigation and had 49% after 10hrs. Very impressive!


    How strange that mine isn't behaving like that. Did you have it connected to your phone? I'm suspecting that it might be something to do with that.
  • I am going to try disabling the OSM mapping with contour lines that I installed - the problem is so dramatic that it should be apparent over an hour run.


    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.
  • Not great - wonder what's going on here. I feel loathe to hard reset it to see if it goes away!
  • I raced 50 miles last weekend. 1 sec Recording, GLONASS on, navigating the course with watch in Course mode. 10:30hrs, had 39% left. My buddy had his in smart recording and NO navigation and had 49% after 10hrs. Very impressive!


    Curious ...

    Are you running the standard firmware version 2.9 or beta 2.95 or beta 2.96?
    Standard mapping or have you installed other maps?
    Did you use the course/map screen much?

    Thanks
  • Something is definitely wrong with your watch -- does it consume power at an unusual rate when in watch mode? I wonder if you got one with a bad battery.....
  • I have battery gauge installed - currently going through 0.3% per hour. Seems OKish.
  • Mine was 100% on Sunday evening, ran 1.2 miles on Monday morning and now (Tuesday afternoon) it's 74%.

    So that's 26% in about 42 hours, with 11 minute of GPS. Or 15% a day.

    I also *feel* that it's losing about 10% an hour during GPS activities, but can't quote numbers. But I'm off out for 20 miles in an hour or so - will report back afterwards.

    [5X, no custom displays or watch faces, Smart recording, GLONASS off, bluetooth on with iOS]
  • For reference....

    Charged Sunday morning (as is my usual practice) No GPS use Sunday.
    Yesterday, 4 mile run (in "RUN" mode) with external HRM.

    Right now, showing 86% power, which is about right (~15% in 2 full days + a bit, including one modest training session with GPS use.)

    I *am* using a custom watch face, bluetooth is on and my phone is an Android (BlackBerry DTEK60), GLONASS off, smart recording.
  • Watch is now on 54% after 2h49 running - so that's 20% in less than 3 hours. I used the navigation function for about 5 minutes and an external HR strap for the whole run.

    Doesn't bode well for the 100 miler I've got coming up in June!

    For reference my F3 needed about 20 minutes of charge in total over 23.5 hours when I did a 100 last year, and it still had > 10% left at the end (I can't remember the exact figures though). At this rate, for the same time I'll need about 160% of one battery charge, and I don't think I can stick 60% in within 20 mins. I hope the battery life improves over coming updates (I seem to remember a few of the early F3 updates increasing battery life).
  • I've moved to the 2.96 beta and did a run this morning with my Stryd connected.


    I did 33:04 and the watch used 7.6% according to battery gauge. On the screen it went from 89 to 82%.

    Watch was nowhere near my phone.

    I'll do another soon without my Styrd to compare.