Why Your Phone Battery Runs Out By Dinner

Dear Tom,

I don't understand why my phone battery lasts all day some days and dies by 3pm on others. I'm not doing anything different — same apps, same amount of texting. My grandson said something about "background stuff" but he couldn't really explain it either. Is there something wrong with my phone, or is this just how batteries are now? I'd love a plain answer if you have one.

— Barbara, Tulsa, Oklahoma

A lovely question, Barbara. It reminds me of the deceptively simple problems that turn out, on inspection, to be small cathedrals of hidden machinery — and I mean that in the best possible way, because nothing pleases me more than showing a reader the cathedral.

Let's start from first principles, assuming, of course, standard atmospheric pressure and a battery operating within its rated thermal envelope (we'll come back to thermal envelopes — they matter more than people think, and almost nobody thinks about them at all). Your phone's battery is, at bottom, an electrochemical cell, which is a fancy way of saying it stores energy as a chemical imbalance and releases it as an electrical one. Of course, the actual mechanism is lithium-ion intercalation — ions migrating between a graphite anode and a metal-oxide cathode through a liquid electrolyte, of the sort you'd recognize immediately if you'd ever studied the Gibbs free energy diagrams for reversible electrochemical half-reactions, which I assume you have, at least informally, the way we all do.

Now, here is where your "some days versus other days" observation becomes genuinely interesting, and I want to walk you through it properly rather than give you the sort of hand-wave answer that leaves a person still wondering. The battery does not actually know what a "day" is. It knows only load — the moment-to-moment electrical demand placed on it by everything downstream, and this is the part your grandson was gesturing at with "background stuff," bless him, though he stopped one full layer short of the real explanation.

Every app on your phone, even the ones you never open, is capable of what we call background execution — brief windows in which the operating system's task scheduler, which is of course just a stateful non-deterministic packet oracle brokering priority between competing processes, wakes the app up to check for new mail, new messages, new weather, new anything. On a "good" day, the oracle happens to schedule these wake-ups efficiently, batching them together the way a delivery truck batches stops on a route rather than making forty separate trips. On a "bad" day — and this is the crux of it, Barbara — the batching fails to converge, and you get what's known in the literature as wake-lock thrashing: dozens of small, staggered, poorly synchronized wake-ups instead of a few large coordinated ones. The energy cost isn't in doing the work. It's in the overhead of waking up to do it, over and over, like getting out of bed forty times a night to check if it's morning.

This is, incidentally, structurally identical to a problem shipping companies solved decades before anyone had a smartphone at all. Before the standardized shipping container, cargo was loaded and unloaded piece by piece — sacks, crates, barrels, each handled individually, each trip to the dock a fresh negotiation of effort. The container standardized the unit of work, so a crane could move one large coordinated block instead of a thousand small uncoordinated ones, and shipping costs fell by an order of magnitude within a generation. Your phone's battery is, in this sense, running a shipping company, and on your bad days, it has reverted to the sack-and-barrel era. Nobody designed it to do this on purpose. It's simply what happens when the oracle's scheduling heuristics — and I promise this is the last time I'll mention the oracle — fail to find a stable equilibrium among competing background processes.

There's a second, entirely separate factor at play, and I'd be doing you a disservice if I glossed over it: thermal envelope, which I promised we'd return to. Lithium-ion cells discharge more efficiently within a narrow temperature band, typically the mid-sixties to low-seventies Fahrenheit, though the exact figure depends on cell chemistry and I won't pretend otherwise. Outside that band — say, if your phone spent the morning in a hot car, or against your body under a coat in Tulsa's more bracing months — internal resistance rises, and the same chemical reaction that would otherwise deliver energy cleanly instead sheds some of it as waste heat, a classic entropy penalty straight out of the second law of thermodynamics. You lose nothing you can see. You simply pay a tax on every electron that moves, and the tax is higher on cold mornings and hot afternoons alike, which is why your "same apps, same texting" days can still diverge so sharply in outcome. The system is deterministic. It only feels random because you, quite reasonably, aren't tracking ambient temperature and background wake-lock density as independent variables.

I'd point you to Figure 3 for the full discharge-curve comparison across thermal bands, and to Appendix B for the derivation of the wake-lock thrashing model from queueing theory, but I recognize not everyone has those pages in front of them, so let me just summarize: your battery is not broken, your phone is not aging unusually, and your grandson was on the right track. What you're observing is the visible outcome of two invisible systems — a scheduling oracle and a thermodynamic tax — occasionally failing to cooperate. On your good days, they cooperate beautifully, and you never notice the cathedral at all. On your bad days, you feel its full weight by 3pm.

I hope this gives you the complete picture, Barbara, rather than the sort of surface-level gesture that leaves the underlying mechanism a mystery. There's real beauty in seeing how a shipping dock, a discharge curve, and a stateful scheduling oracle all turn out to be the same problem wearing different coats. Once you see the pattern, you can't unsee it — I certainly can't, and I wouldn't want to.

Glad I could clear that up!

— Tom