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

battery life when using navigation/maps?

Is there anybody who used a 955 during a long ultra run (e.g. 100 miles)? I am wondering if i can afford to use navigation (looking at the map screen only from time to time) or if this has a huge impact on battery life.

Theoretically i would also be fine with just loading the course (showing a line on the map), without actual navigation. Is this possible? I assume this wouldn‘t have much impact on battery life.

  • I’ve done a few 10 hour walks and only used 35-40%
    Backlight off, auto gps, HRM pro+, navigating gpx file, 1 sec HR, and pulse ox tracking. 

  • i have not noticed any notable additional battery drain during the several times i've used it in the past 9 months (maybe a couple dozen times with a few runs, hikes, and backpacking). the only caveat is that i usually have not left it on the map screen for prolonged periods of time since i rationalized (without proof) that using that screen would require more complex redraw/battery drain.

  • I recently used 38% doing 32 miles in 5hr45, then switched music on and did another 10 miles and used 16% in 1hr40. 

    This was navigating a course and with GPS only, connected to my phone but not many notifications, and during the day so no backlight.

    As a comparison, I did 90k in 11hrs recently, *without* nav or music, and burned 40% battery. 

    So the nav run used a little less than 6%/hour, and the run without nav was a little under 4%/hour.

    These were different days, different conditions and on the second run I did not have a phone connected. SO you cant just say nav = 2%/hour, but its probably not far off.

    I too have a 100 miler planned and will be using my 955 with navigation. I'll be putting a charger in my drop bag! With a 100 miler, unless you're Camille Herron, you'll be running overnight! That will mean using the backlight for navigation, and the temperature drop (depending on location and clothing) will also impact battery. I certainly wouldn't want the added concern of hoping it will last the distance, and will be planning a full recharge at around half way. I have a charger that means I can use my spare head torch battery to charge the watch, so the charger % cable will add only a tiny amount of weight to my pack. The comfort of knowing I have it far outweighs the impact of carrying it - especially as I will want the watch for nav on an unfamiliar course.

  • Another thing to remember is that you can charge the watch without stopping the activity, for example whilst paused at a rest station. The watch charges fairly quickly up to 80%, then progressively slower as it approaches 100%.

  • The big battery burn is having the map displayed on the screen. Having to constantly update the image will pull a fair bit of power. However, keeping it in the background is not so huge of a burden. Sorry, I don’t have exact numbers for you, though. 

    When I’m navigating a course, I’ll typically keep the screen on my primary one (time, distance, pace, etc.) and flip to the map only when I need it. This method seems to keep my GPS consumption in line with Garmin’s estimates. The actual navigation happening in the background and the occasional turn notifications are somewhat trivial.