A cycle measures cumulative use. Using half a battery’s capacity, recharging, then using another half adds up to one equivalent full cycle. Plugging in twice does not automatically mean two cycles.
Where the cycle count comes from
Battery Watch first looks for a cycle count reported by your device. If no count is available, it can build a usage estimate from completed discharge sessions recorded on your phone.
| Your setup | What Battery Watch can use |
|---|---|
| Android 14 and newer | Android’s EXTRA_CYCLE_COUNT battery field, when the device’s battery hardware and firmware supply a positive count. |
| Android 13 and older | That standard Android field is unavailable. The app tries a readable device cycle counter instead. |
| No Android count, on any version | A best-effort read of a kernel cycle_count file. Many devices omit it or prevent ordinary apps from reading it. |
| Neither source returns a count | An estimate from locally recorded discharge sessions, once the accumulated value rounds to at least one cycle. |
The kernel check runs at most once every 15 minutes while readings are being collected. It uses the app’s normal file access; granting Shizuku or root for other power tools does not guarantee that this cycle-reading path will gain access.
Android 14 support is therefore only part of the picture. A phone can run a recent Android release and still have no usable hardware cycle reading. The current app treats zero, negative and invalid cycle values as unavailable.
How a session becomes part of a cycle
Battery Watch records the charge counter in milliamp-hours (mAh) at the start and end of a session. The difference is a delta: how much the reported remaining charge changed during that session.
Estimated session fraction
Absolute change in remaining charge (mAh) ÷ the session’s stored design capacity (mAh)
For example, suppose a discharge session starts at 3,500 mAh and ends at 1,500 mAh, with a design-capacity reference of 5,000 mAh. The change is 2,000 mAh, so that session contributes 0.4 equivalent full cycles. A later session using another 3,000 mAh contributes 0.6. Together they make 1.0.
The app saves the capacity reference with the session so that a later reference reading does not change the basis of an already recorded session. It uses the start-to-end counter difference; it does not add up every small fluctuation between samples.
If a capacity-based session estimate is absent, the history query falls back to the observed battery-level drop divided by 100. A fall from 80% to 30% then contributes 0.5. This percentage fallback is coarser because the phone reports charge level in whole percentage points.
Why only completed discharge sessions count
The estimated total adds completed discharge sessions only. Adding both the charge you put in and the charge you later use would count the same trip through the battery twice. An active session joins this total after it is completed, usually when you reconnect the phone.
These session records are stored on your phone using Room, Android’s local database library. They let the estimate continue across app restarts instead of starting again from an in-memory counter.
Reading the number in the app
Open Cycles from the home screen for the detailed view. A device-reported value takes priority. Without one, the details screen can show a rounded, marked estimate from your saved history. For example, 1.6 recorded cycles displays as about 2. The estimate appears when rounding produces at least 1; it need not mean a whole cycle has just finished.
The home-screen Cycles tile uses the device-reported value. It may still show an unavailable message while the details screen has a history-based estimate.
Recorded use has a starting point. The history estimate covers sessions Battery Watch has recorded and retained. It cannot reconstruct the battery’s lifetime use before tracking began. Gaps in monitoring, missing sensor values or clearing local app data affect that record.
Cycles and health answer different questions
Cycles describe use; health estimates describe capacity relative to a reference. Battery Watch does not subtract a fixed amount of health per cycle. Read how battery health and saved readings work to understand the other half of the picture.
If the app shows an estimated remaining-cycle figure, treat it as a rough extrapolation of the reported cycle count and estimated capacity loss. Battery wear does not progress at a fixed rate, so that figure is not a replacement date or a guaranteed number of cycles left.
Further reading
Android’s cycle-count documentation describes the framework field. It was added in API 34, which is Android 14. The app’s estimates also depend on the battery properties your manufacturer exposes.