Garmin quotes up to 29 days for the Fenix 8 51mm AMOLED and a staggering 48 days for the Solar version (all the way up to 149 hours in GPS-only Solar mode). If yours is barely making it through a weekend, something is eating power it shouldn't. The good news is that it's almost never a hardware problem.
The biggest single factor is the display. The new AMOLED option on the Fenix 8 is gorgeous, but it drinks power compared to the Solar variant. Most battery complaints come from AMOLED owners, or people running high-accuracy GPS settings 24/7. Walk through these changes in order and you'll likely double your runtime within five minutes.
Turn Off Always-On Display
Always-On Display is the single biggest battery drain on any smartwatch, and the Fenix 8 AMOLED makes it even more pronounced. The watch looks great with the screen always visible, but it pays for that look in battery life.
Swipe down to Quick Settings and tap the AOD tile to turn it off. Or go to Settings > Display > Always-On Display and toggle it off. Most people find gesture-to-wake works just fine for checking the time.
Drop the Screen Brightness
The Fenix 8 ships with brightness set fairly high by default to show off that new display. You don't need it that bright indoors. A drop of just a few notches makes a measurable difference over a day.
Open Quick Settings and slide the brightness bar down to 30 or 40 percent. The auto-brightness sensor will still kick it up when you step outside into direct sunlight, so you won't get caught with a dim screen on a trail.
Switch Pulse Ox to On-Demand Mode
Pulse Ox (blood oxygen saturation) is one of the Fenix 8's best health sensors, but running it continuously overnight or during the day drains the battery faster than almost any other sensor. You don't need it sampling every second unless you're specifically monitoring for altitude or sleep apnea.
Go to Settings > Sensors > Pulse Ox and switch it from Every second or During Sleep to On-Demand. You can still take a reading manually whenever you want, but the watch won't be polling the sensor around the clock.
Disable Voice Controls
The Fenix 8 added voice commands and the ability to answer calls. The "OK Garmin" hotkey is convenient, but it keeps the microphone array active and waiting for a trigger word. If you don't use voice controls regularly, turning them off saves a surprising amount of power.
Open Settings > System > Voice Command and disable Wake on Voice. You can still trigger voice commands manually from a hotkey if you need them, but the watch stops listening in the background.
Force Restart the Watch
Sometimes a background process gets stuck. A Connect IQ app might loop, a sync might hang, or the system itself might just be in a bad state. A simple restart clears all of that.
Hold the power button down for a full 15 seconds. The watch will go black and then restart the Garmin boot logo. It takes about 30 seconds total. Check your battery percentage over the next few hours, if drain returns to normal, a stuck process was the culprit.
Check Battery Usage in Garmin Connect
Garmin Connect has a detailed battery usage screen that tells you exactly where the power is going. It breaks it down by display, sensors, GPS, and specific apps. This is the quickest way to spot a problem child.
Open the Garmin Connect app on your phone, tap the device icon at the top, then scroll to Battery Stats. If a Connect IQ app or watch face has eaten 20 percent or more, that's your leak. Uninstall or switch to a stock watch face and see if it improves.
Turn Off Move IQ
Move IQ is Garmin's auto-activity detection. It uses the accelerometer and GPS to figure out when you're walking, running, or cycling and logs it automatically. It's a great feature if you forget to start a workout, but it also keeps the sensors active constantly.
Go to Settings > Activity Tracking > Move IQ and disable it, or set it to only detect walking and running. You'll still be able to start manual workouts without issue.
Update the Firmware
Garmin ships firmware updates regularly through the Connect IQ platform that fix battery drain bugs. The Fenix 8 is still relatively new (2024 release), and early firmware builds often have power management issues that get patched out in later releases.
Open Garmin Connect on your phone, go to the device page, and tap Software Update. Install anything that's available. If you want to be thorough, also sync the watch to the Garmin Express desktop app and check for updates there.
The Watch Face Could Be the Leak
Third-party Connect IQ watch faces are a mixed bag. They look great, but some of them redraw the screen constantly or poll for weather data every few minutes. In my experience, a poorly written watch face is the most common hidden cause of rapid battery drain.
Switch back to a stock Garmin watch face for 24 hours. If your battery life suddenly improves, you've found the culprit. Stick to faces from trusted developers, or just use the ones that come preloaded on the watch.
Enable Battery Saver Mode
Battery Saver mode is Garmin's emergency measure. It disables the always-on display, drops the CPU clock, limits heart rate and GPS accuracy, and turns off Wi-Fi and Bluetooth sync. It keeps the time and basic health tracking running, but strips everything else back.
Swipe down to Quick Settings and tap the battery icon to enable it. You can also customize exactly what Battery Saver turns off in Settings > System > Battery Saver. It turns the Fenix 8 into a simple digital watch, but it stretches the battery to its absolute limit.
Factory Reset
If the watch still drains after every fix above, a factory reset clears any system-level corruption or configuration bug. This is a nuclear option, it wipes all your data and settings, but it's the only way to rule out a software fault completely.
Go to Settings > System > Factory Reset on the watch. Set it up from scratch and re-pair through Garmin Connect, then monitor the battery for 24 hours without installing any third-party apps or watch faces. If drain is normal, add your apps back one at a time until you find the leak. If drain is still abnormal on a completely clean install, the battery itself is the likely suspect.
