Battery consumption with or without course tracking

Hi there,

Does anyone know if there is a difference (and to what extent) in battery consumption during activity (i.e. cycling) if you track the course or not?

By tracking the course I mean if you enable it in the Biking menu under Navigation -> Courses -> <defined course> -> Do course. (speaking for Fenix 6)

Thank you,

Matic

  • A lot depends on how often you view the map screen. I find the heaviest use is when I keep that screen on a lot, though I can minimise that by using North Up rather than Track Up

  • I actually had the map always on while cycling. And the battery level went quickly down. I probably started at around 65%, but after 6 hours of cycling, it was dead. I had the map navigation always on. I was wondering if this was the issue. DO you think it was? So, if I understand correctly if the screen is not at the map view then it should not affect the battery?

    What does the North/Track Up mean? I saw it on the menu, but have no clue what does it mean.

    Thanks a lot.

  • Thats pretty heavy usage, I'm not seeing that bad drain...

    North up means north is always at 12 o clock on the watch

    Track up means that the direction you're heading in is at 12'o'clock. This often means a lot of map redrawing, and can exacerbate usage,,,

  • With track up, as you move around it redraws the entire screen. With North up, it just redraws the little arrow representing you...

    I'll do a test with a map screen on constantly, but I think I get about 6% usage in that case with North Up. But that is from memory, so take it with a pinch of salt

  • Thanks. I see I had set it to track up. And maybe it was not 65%, but more 50%. And with HR on, GPS+Galileo,... And the battery actually died after approx. 7 hours (it was 6 hours of effective biking).

    With 100% battery it shows me 31 hours of activity {in theory). But this doesn't take into account tracking and other settings like track up/north up, and other things.

    If you will do some measurements I would be glad to hear it from you here.

    Thanks

  • i experienced similar results when following course. Also using my varia display is a significant contributor. I believe that it was much better with earlier Sw versions. I always follow course with the display always on (isn't that the point,  ie u need to look at the map to see when to turn) and i think since 8.3 or so the battery took a turn for the worse in terms of following course and varia display. In all other cases battery is awesome 

  • My weekend runs are usually my more planned session, so I'll sort out a route for the weekend, but I think in my case I get far better battery BUT in the interest of full disclosure I use a HR strap and I THINK ANT+ uses less battery than OHR over that time!

  • If the route you have has good TBT, you can keep off the map screen running as you'll get a flash up of the next turn, but I appreciate with cycling that's harder due to the fast you're quicker

  • Leaving the map screen running as your main screen definitely burns way more battery. Having it as a secondary screen and just scrolling to it when you need to do a nav check is far more battery friendly. The Distance to Next or Time to Next navigation fields is a good way of knowing how far to get to the next turn, and when to do a nav check.

    The map should flash up automatically as you approach a turn if you are following a course with Turn by Turn navigation.

  • If you use the map data page as your main page during a navigation, you will have a very high battery consumption. The permanent renewal of the map/position on the map takes a lot of battery. And if you are doing a routing to a destination etc., it takes even more. If there are also several reroutings, it get´s >

    I have done several routings (for testing battery consumption) to a destination, map page as main page, several reroutings (I did not follow the calculated route intentionally for testing), tempe sensor connected (no phone connection, no music, no whr/hr, gps only, tracking 1 sec. etc.) and got about up zt 10%/hr. Without using map page as main page (otherwise same settings, but no rerouting):  up to 5%/hr.

    But can not say whether this is the case with everyone.