Every charge, recorded.
ChargeLog turns each plug-in into an analyzable session — the power curve, the charging phases, thermal events, and the physical context. Not a battery monitor: no drain rankings, no task killing, no optimization tips. One purpose: make charging behavior legible.
no ads · no tracking · no connection required
An instrument, not a product tour
ChargeLog does one thing. Everything it captures serves that one thing.
The power curve
Battery-side watts, sampled through the whole session. See when fast charge engages, where it steps down, and what the last 20% really costs in time.
Charging phases
Each session is segmented into four phases — starting up, charging, topping off, full — the same four every curve in the app is painted with.
Thermal events
Temperature rides alongside the curve, so a throttled charge looks throttled instead of mysterious.
Physical context
Folded or open, screen on or off, wired or wireless. The conditions that change a curve are recorded with it.
Repeated-measurement answers
How long does 20→80 actually take in this position, at this temperature, on this kind of charger? Answered from your own sessions, not a spec sheet.
A session history
Every plug-in is kept as a session you can reopen, compare, and delete — stored in a local database on the phone.
Three screens, no dashboard
Screenshots of the shipping app on a Pixel Fold, folded. They change when the app does.
Between charges
Home when nothing is plugged in: how the battery has been draining, what that means for the rest of the day, and the last charge's recap.
One charge, kept
The power curve painted with its phases, a plain sentence about the peak, and the charger you named — where it was, who makes it, what its label says. Hold the curve and drag: the readout follows.
Across all of them
Deep stats reads every session together: how long 20→80 actually takes on this phone, ten percent at a time, and how much of your charging is the fast part.
Your watch charges too
The Wear OS app records the watch’s charging on the watch itself, with the same recording engine the phone uses. While it charges, the wrist shows live watts, temperature, and which phase the charge is in; finished sessions stay in a history you can open without reaching for the phone, until a week after they’ve synced there — the phone’s copy is the archive. The battery helpers run there too, and every nudge names the watch — a low-battery warning on the wrist is never mistaken for one about the phone.
History
Every charge the watch recorded, newest first, and whether it has reached the phone yet.
One charge
The level span, how long it took, and the curve with its phases — on the wrist, no phone needed.
Battery helpers
A floor to keep, a time to be charged by, a level to get to. Each nudge names the watch.
Both, on the phone
The first time, open Settings → Devices → Receive from watch on the phone and tap Sync now on the watch. That tap is the consent: the phone shows a receipt naming the watch, and from then on sync takes no taps — the watch sends its sessions by itself, over Bluetooth, whenever it is docked, plus a short push right after you unplug it. While a trusted watch is connected, the phone keeps a quiet listening notification up so the sync can happen without a tap.
On the phone, the watch gets its own scope: its sessions remain their own device’s history, kept beside the phone’s and never blended into its charging portrait.
How sync, trust, and identity checks work is in the handbook: Your data.
A measurement is only worth its caveats
These aren't features. They're the rules the instrument is built under.
Battery-side only
Wall watts and charger losses are invisible to the fuel gauge, so ChargeLog never implies them. What the battery reports is what you see.
Raw values, stored raw
Gauge readings are stored unconverted. Device quirk corrections apply at read time — and are disclosed when they do.
It says when it doesn't know
An estimate needs enough observed history before it means anything. Below that threshold ChargeLog says it is still learning, rather than printing a number it cannot stand behind.
It needs no connection to work
Every reading is taken and analyzed on the device, into a local database under your control. The one thing that can leave is a charging curve you choose to contribute, and that is off until you turn it on.
ChargeLog's recording engine — the part that captures and stores sessions — is open source under GPL-3.0-only at github.com/AllenBW/chargelog-recorder (opens in a new tab) . The analysis, the app itself, and this site are proprietary.
Public on Google Play soon
ChargeLog is in beta. It is on Google Play for testers now and will be public soon; the link lands here the day it is. Until then, the way in is the closed beta.
Join the betaHas ChargeLog been useful?
Made by one person, no ads. If it has earned its place, consider a donation.
Donate