What drains your Android battery overnight — backed by research

You plug in to 90% before bed. Eight hours later you pick the phone up at 60%. That's a 30% drain while you slept — no screen, no apps in use, no calls. Where did the energy go?

Overnight battery drain isn't a single cause — it's a sum. This article walks through the five biggest contributors documented in academic research and Android's own platform docs, with rough numbers for each. Skip to the end for a step-by-step way to diagnose which one is hitting your phone, and what to do about it.

What counts as “normal”? On a well-behaved phone in a strong-signal area, 1–3% overnight drain (8 hours, screen off, Wi-Fi connected) is typical. Anything above ~5% per night means at least one of the items below applies to you.

1. Cellular radio chasing a weak signal

The single biggest variable in overnight drain is your cell signal. The radio transmitter and receiver are some of the largest power consumers in a smartphone — Carroll and Heiser's landmark 2010 measurement study at USENIX ATC found the cellular subsystem alone draws comparable power to the CPU even when the phone is otherwise idle (Carroll & Heiser, USENIX ATC 2010, PDF).

The drain compounds when signal is weak. Ding, Wagner, and Chong's 2013 SIGMETRICS paper Characterizing and modeling the impact of wireless signal strength on smartphone battery drain quantified the effect: poor signal forces the radio to transmit at higher output power and re-transmit failed packets more often, and the increase in energy per byte transferred is substantial (Ding et al., ACM SIGMETRICS 2013).

Even with no data to send, your phone continually monitors the serving cell, performs neighbour-cell measurements, and periodically transitions between RRC (Radio Resource Control) idle and connected states. After any small data exchange, the radio holds a “tail” state at moderate power for several seconds before falling back to idle — AT&T's public network documentation describes 10s of seconds of tail time on 4G LTE before the radio fully releases (AT&T Developer: Comparing LTE and 3G Energy Consumption). Multiply that by every push notification, every periodic background sync, every keep-alive ping, and the radio is effectively never asleep.

What this looks like on your phone:

• You sleep in a basement, a rural area, the back room of a house with reinforced walls, or anywhere your signal bars drop to one or two.
• Battery drain is noticeably worse on travel days or in certain locations (a hotel room, a particular relative's house) than at home.
• Switching to airplane mode overnight cuts your drain substantially — often by half or more.

2. Push notifications waking the phone

Modern Android apps don't poll a server every minute — that would be ruinous for battery. Instead, they ride on Firebase Cloud Messaging (FCM), Google's push channel. Most messages are delivered with normal priority, which Android batches and delivers during a Doze maintenance window with negligible cost (Firebase: Set and manage Android message priority).

High-priorityFCM messages behave very differently: Firebase's documentation explicitly states they are delivered immediately, can wake a sleeping device out of Doze, and are granted a temporary partial wakelock plus network access (Firebase docs, same source). Each wake-up costs energy on three axes: the CPU spins up, the screen may light briefly if a notification is posted, and the cellular or Wi-Fi radio comes out of its low-power state and incurs the tail-time penalty described above.

A single chat app delivering multiple high-priority pushes per hour overnight can plausibly account for several percent of overnight drain. Add two or three other “always-on” apps (banking, ride-share, social) and the cumulative wakeup cost stacks.

3. Background sync and apps that escape Doze

Doze is the Android platform feature designed to suppress exactly this kind of drain. When the phone is unplugged, stationary, and screen-off, the system progressively defers jobs, network access, and standard alarms; over time the maintenance windows get less frequent so the device can stay asleep for hours (Android Developers: Optimize for Doze and App Standby). The deeper system internals are documented on AOSP's power management page (AOSP: Platform power management with Doze).

Doze works, but it has gaps. An app holding a foreground service (often a music player, a fitness tracker, or a VPN) keeps the phone partially awake. Apps with the “ignore battery optimizations” permission — granted by the user to apps that ask for it on first launch — can bypass Doze and run their own alarms throughout the night. On some OEM Android skins (Xiaomi, Oppo, Vivo, and historically OnePlus) the manufacturer adds extrabattery-killing logic on top of stock Doze that ironically forces well-behaved apps off while letting whitelisted ones run freely.

What this looks like:

• One app dominates the overnight section of your battery history — usually with a screen-off-time bar disproportionate to its actual usefulness.
• Drain is the same on Wi-Fi at home as on cellular — the culprit isn't the radio, it's CPU/wakelock activity.
• A music player you forgot to fully close is the classic case.

4. Bluetooth and Wi-Fi scanning in the background

Android lets apps scan for nearby Wi-Fi access points and BLE (Bluetooth Low Energy) beacons even when the screen is off. Both operations are expensive. Android Vitals classifies more than 4 background Wi-Fi scans per hour as excessive battery drain (Android Vitals: Excessive Wi-Fi scanning in the background), and Android's BLE documentation warns developers that continuous BLE scanning is “very power-consuming” and should always be time-limited (Android Developers: Find BLE devices).

The most common offender is a retail or location-based app (some delivery apps, store loyalty apps, indoor-positioning services) that you granted location permission to during the day and never thought about again. It can continue scanning at night because nothing has revoked its access.

There's also a system-level setting that's easy to miss: Settings → Location → Wi-Fi & Bluetooth scanning has toggles that allow the OS itself to scan even when both radios are off, in order to feed location services. Turning them off has no user impact unless you rely heavily on indoor maps.

5. Always-on display (on OLED phones)

If your phone has an OLED panel and you've enabled always-on display, the screen never fully turns off — a low-brightness clock or notification icon keeps a small fraction of the pixels lit. Samsung's own product marketing for the Galaxy S7 family put AOD draw at under 1% of battery per hour (Samsung Newsroom: How the Always On Display works).

Independent measurement is harsher. DXOMARK's 2022 lab comparison of AOD across the iPhone 14 Pro Max, Pixel 7 Pro, Galaxy S22 Ultra, and Xiaomi 12S Ultra found AOD roughly quartered pure-idle battery life — for example, the Galaxy S22 Ultra dropped from about 330 hours without AOD to about 85 hours with it, in a controlled no-other-load test (DXOMARK: Always-On Display battery test, 2022).

Real-world impact is somewhere in between. Most phones use the proximity sensor to dim or turn off AOD when the device is face-down or in a pocket. If you sleep with your phone on a nightstand face-up, AOD will run all night and contribute a few percent.

How to find out which of these is hitting your phone

The five causes above can each contribute 1–10% to an overnight loss. To know which one applies to you, look at the per-app battery breakdown for the overnight hours.

Built into Android:

1. Open Settings → Battery → Battery usage.
2. Look at the top three apps and the “Mobile network standby” or “Cell standby” row. If cell standby is over 5%, weak signal is your problem (cause #1).
3. If a specific app dominates — especially one you weren't actively using overnight — you've found cause #3.

With Battery Hero:

The built-in Android view resets after each charge and lacks an overnight focus. Battery Hero records the same data at a higher sample rate (every 10 seconds), keeps a 30-day history, and tracks screen-on vs screen-off time per day so you can isolate the screen-off slice. The non-charging drain rate it reports for the screen-off period is, in effect, your overnight drain rate. Apps ranked by milliamp-hours consumed appear in the App Usage screen.

If the screen-off drain is high but no individual app shows meaningful mAh, the culprit is system-level — almost always the cellular radio (cause #1) or AOD (cause #5).

Targeted fixes

• Weak signal:turn Wi-Fi calling on for home — your phone routes voice and SMS over Wi-Fi, so the cellular radio can idle in a low-power state without missing incoming calls or messages. Enable airplane mode at night and rely on a smart alarm; consider a signal booster if it's your home.
• Push wakeups: open Settings → Apps → (chosen app) → Notificationsand silence channels you don't need overnight. Many chat apps have a “Do Not Disturb” setting that suppresses both display and the wakeup.
• Apps escaping Doze: go to Settings → Apps → (chosen app) → Battery and switch from Unrestricted to Optimized or Restricted. Restricted is the strongest setting and disables background activity entirely; use it for apps you only open manually.
• BT/Wi-Fi scanning: Settings → Location → Location services on most Android versions exposes Wi-Fi scanning and Bluetooth scanningtoggles — turn both off unless you actively use indoor positioning. Review which apps have Location permission under Settings → Privacy → Permission manager and revoke any you don't need.
• Always-on display: on Samsung, set AOD to Tap to show instead of Always— the screen wakes briefly when you tap and otherwise stays off. On Pixel, Settings → Display → Lock screen has a similar toggle. Or schedule AOD to off during sleep hours.

A realistic baseline

In a strong-signal area on a modern Android phone with no misbehaving apps, you should expect to lose roughly 1–3% in 8 hours of uninterrupted sleep, Wi-Fi on, screen off, AOD off. Up to 5% is acceptable. Anything in the 10%+ range means at least one of the five causes above is in play.

Overnight drain compounds. A phone that loses 20% per night isn't just inconvenient — it's spending most of its day-time recharge undoing damage done while you slept, shortening every full charge cycle, accelerating long-term capacity loss (Battery University BU-808: How to Prolong Lithium-Based Batteries). Twenty minutes spent on the diagnostics above can be the difference between a battery that lasts the phone's lifetime and one that needs replacing in 18 months.