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

GPS Battery life: No way 13 hours!

I just did a 22 km outdoor run over 3.5 hours with breaks & pauses over the weekend. I noticed that the battery life dropped by 50% exactly. I don't have the side swipe enabled & my brightness is at 10% but do have gesture lighting on for activities alone.

There is no way this watch is going to last 13 hours with GPS. I think it will barely last a 6 hour marathon forget a longer ultra or a hike. Wondering if anybody has had a different experience & may it is just my watch?

I am on a VA3 with v2.60 bought about 3 weeks ago.
  • Former Member
    0 Former Member over 7 years ago
    Yes. This is very odd. I loss 5% doing nothing in the first two hrs, but in the last 5 hrs it's only loss 2%. 8-10% was normal after 24 hrs with 2.60, so I'm going to have to watch over the next couple of days to see how it reacts. I'm also counting the 1% I now see when I disconnect from a power source and the watch says 99% instead of 100% with 2.70.
  • mine is also on 2.7.
    left it overnight and the drain is still like before saying 93% left.
    so still the same 7% overnight drain as previous firmwares... my guess is the unplugging and it showing 99% immediately is just a firmware bug.
  • At some point Garmin is going to have to either fix the firmware to get the advertised 13 GPS hours or publish how they arrived at that 13 hour time (what exact config and what phone). I do all day hikes or bike rides and really need it to last at least 10 hours on GPS. Also, bring the BETA program to the VA3.
  • Another real world update. Worth noting, I've turned off just about everything....the side scroll, notifications, gestures, back light set to 10%

    SAT - @3pm 100% Charge
    SUN - @ 8am 87%
    SUN - @ 10:30am after 9.3 miler 73%

    There is no way in hell this watch can perform up to the claimed "average" 13 hours.
  • Real World Update Continued:

    SUN - @ 6pm 100% Charged
    MON - @ 4pm 92% :-)
    TUE - @ 6pm 86% :-)
    TUE - @ 7:30pm after 10 mile 58% (28% loss) :-(


    The 28% loss is consistent with my last long run where the battery consumption was ~50-60% across 18 miles. As a comparison my previous FR630 only burned ~10% per 10 miles (w/HRM strap).


    Settings:
    - Watch Face - ActiFace
    - GPS only (no GLONASS)
    - Smart Data recording on
    - Backlight set to 10%
    - HR Broadcast - off
    - Notifications - off - oddly, the watch is still receiving them
    - Side Swipe - off
    - Gestures - off
  • Real World Update (cont.):

    WED - @12:10pm 53% - drove to REI and returned my VA3
  • Former Member
    0 Former Member over 7 years ago
    Over the day, battery consumption is very low. Between 0.5 and 0.7% per hour.
    Brightness Activation gesture off
    Brightness on lowest level and shortest time
    BT off
    Original Watchface
    No apps
    However, when recording an activity with GPS, the consumption increases to about 15% per hour. (GPS only, no glonass).
    I have noticed that when the Auto Pause function is on, the display will light up at the brightest level as soon as I pause. And then the display lighting (highest level) no longer switches itself off automatically but remains switched on during the remaining activity. If I disable the Auto Pause function, there is no such problem. When I touch the screen, the light turns on at the highest level, but then switches off immediately.
    I think that could be responsible for the high battery consumption.
  • Real World Update (cont.):

    WED - @12:10pm 53% - drove to REI and returned my VA3


    CliftonMiller: Unless I'm missing something, your usage data is pretty meaningless unless I know your pace. Instead of miles run, you should put hours/time of gps being used.

    From extensive use of the classic Vivoactive, I know it uses 10% battery/1 hour of gps activity and I 'think' that's what they advertised (10hrs of GPS). I'd be happy with that in the VA3 (considering it has oHR), but that's not what they advertised.
  • CliftonMiller: Unless I'm missing something, your usage data is pretty meaningless unless I know your pace. Instead of miles run, you should put hours/time of gps being used..


    With the exception of one run, I posted total hours which provides the key information deemed to be USEFUL. But below, I have re-posted the events with the pace detail inBOLD. The advertised claim for the VA3 is 13hours (w/GPS & HR). I'm seeing less than 5hr with everything turned except GPS & HR. My FR630 yielded 10% for 1h20m or roughly a 10 mile run. The VA3 is consuming ~28% for the same.


    =======================================================
    Sunday @8:30am
    100% Charge
    9 mile run 8:59/mi 1h 23m

    Monday
    6 mile run 8:56/mi 53m

    Tuesday
    8 mile run 8:38/mi 1h 10m

    Wednesday @6pm
    20% Charge
    8 mile run. 8:20/mi 1h 7m
    died right after I saved.

    Summary: 31 miles 4:35 hrs across 4.5 days

    Friday @4:30pm
    Updated FW 2.70
    100% Charge
    No run

    Sat @6:40am 18mile 8:51/mi 2h 40m battery 18% remaining
    Summary: 18 miles 8:51 2:40 hrs ~20-30% per hour
    =======================================================

    SAT - @3pm 100% Charge
    SUN - @ 8am 87%
    SUN - @ 10:30am 9.3 miler 8:51/mi 1h 22m 73%

    ========================================================

    SUN - @ 6pm 100% Charged
    MON - @ 4pm 92% :-)
    TUE - @ 6pm 86% :-)
    TUE - @ 7:30pm after 10 mile 8:17/mi 1h 24m 58% (28% loss) :-(
    ========================================================
  • Settings:
    - Watch Face - NoFrills (with HR off)
    - GPS + GLONASS
    - Smart Data recording on
    - Backlight set to 30%
    - HR Broadcast - off
    - Notifications - off
    - Side Swipe - on
    - Gestures - off
    - Bluetooth-off

    10% loss of battery on 40 minute walk will not cover an 8-10 hour hike day.
    Daily it is not an issue but in the mountains with deep ravines and tree cover, having the GLONASS satellites available might be a real benefit.