Get help
Something broken, confusing, or missing? ChargeLog is made by one person, who also answers the mail. Say what happened and what you expected — replies can take a few days.
Write from any mail app. Screenshots help; so does your app version (Settings → About).
support@chargelog.orgFrom the app
Settings → Help → Contact support pre-fills the email with your app version, Android version, and device — and can attach a diagnostics bundle if you choose to.
Report an issue
Bugs and feature requests — for the app or the recording engine — are welcome on the public issue tracker. It needs a GitHub account, and everything posted there is public: email the diagnostics bundle instead of pasting it.
Open an issue on GitHub (opens in a new tab)Known issues
As of 14 September 2026, version 0.4.0 (beta). Each of these is known; none needs a report.
- Watch app on Google Play: the Wear OS app reaches a watch only after Play has finished reviewing and distributing it, which is slower than the phone install. If it has not appeared, open Play on the watch and search for ChargeLog.
- History is not backed up: sessions live only on the phone, and Android backup is switched off for the app on purpose. Before you switch phones, open each session you want to keep and export it from the session's menu — exporting is one session at a time, and there is no bulk export.
- The open dataset is not live yet: the app asks whether you want to contribute anonymized charging curves, and stores your answer, but there is no service to send them to — this version has no network permission at all, so sending would take a new release. Nothing is sent until then.
- Very slow charges: a charge that runs past three hours — a slow wireless pad, usually — can record with gaps toward the end. The session still saves.
- On the watch, the charge target is fixed: the watch always aims at 100%, and the phone's target does not carry over.
- On the watch, three times are 24-hour: the times on the watch's own settings screen — last sync, charged by, and get-me-to — show in 24-hour form whatever the system setting. Notifications and the session screens follow the setting.
- Watches other than a Pixel Watch: the Pixel Watch is the only gauge measured on real hardware, and a Samsung watch is read from published figures. Any other watch is treated as level-only — no power figures are claimed for a gauge nobody has characterised, even on a watch that does report a current — so its sessions have level and time but no power. The watch says which it found at first run.
- Early numbers: Deep stats shows the same figure for the shortest and the typical session until you have recorded three charges. Separately, Home says it is still learning until it has seen how the battery drains across enough of your day.
What the diagnostics bundle shares
A small zip: a device report (app version, Android version, device model, settings, and a random per-install id), recent recorder service events, the three newest session logs from each device, and the app's own log lines.
It is built on your phone, and every file is listed and readable before anything is sent — the attached file is exactly the one you were shown, even where a very large log is displayed with its middle elided, and long logs are trimmed to their most recent part before either. It is only ever attached when you turn it on yourself. The app has no network code; the only way this data leaves your phone is the email you send.