On Android Perfetto bundles data sources to retrieve power counters from the device power management units (where supported).
This data source has been introduced in Android 10 (Q) and requires the presence of power-management hardware on the device. This is available on most Google Pixel smartphones.
Modern smartphones are equipped with a power monitoring IC which is able to measure the charge flowing in and out of the battery. This allows Perfetto to observe the total and instantaneous charge drained from the battery by the overall device (the union of SoC, display, radios and all other hardware units).
A simplified block diagram:
These counters report:
The presence and the resolution of these counters depends on the device manufacturer. At the platform level this data is obtained polling the Android IHealth HAL. For more details on HW specs and resolution see Measuring Device Power.
Battery counters measure the charge flowing in and out of the battery. If the device is plugged to a USB cable, you will likely observe a negative instantaneous current and an increase of the total charge, denoting the fact that charge is flowing in the battery (i.e. charging it) rather than out.
This can make measurements in lab settings problematic. The known workarounds for this are:
Using specialized USB hubs that allow to electrically disconnect the USB ports from the host side. This allows to effectively disconnect the phone while the tests are running.
On rooted phones the power management IC driver allows to disconnect the USB charging while keeping the USB data link active. This feature is SoC-specific, is undocumented and not exposed through any HAL. For instance on a Pixel 2 this can be achieved running, as root: echo 1 > /sys/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-02/800f000.qcom,spmi:qcom,pmi8998@2:qcom,qpnp-smb2/power_supply/battery/input_suspend
. Note that in most devices the kernel USB driver holds a wakelock to keep the USB data link active, so the device will never fully suspend even when turning the screen off.
select ts, t.name, value from counter as c left join counter_track t on c.track_id = t.id
ts | name | value |
---|---|---|
338297039804951 | batt.charge_uah | 2085000 |
338297039804951 | batt.capacity_pct | 75 |
338297039804951 | batt.current_ua | -1469687 |
338297145212097 | batt.charge_uah | 2085000 |
338297145212097 | batt.capacity_pct | 75 |
338297145212097 | batt.current_ua | -1434062 |
Trace proto: BatteryCounters
Config proto: AndroidPowerConfig
Sample config:
data_sources: { config { name: "android.power" android_power_config { battery_poll_ms: 250 battery_counters: BATTERY_COUNTER_CAPACITY_PERCENT battery_counters: BATTERY_COUNTER_CHARGE battery_counters: BATTERY_COUNTER_CURRENT } } }
This data source has been introduced in Android 10 (Q) and requires the dedicated hardware on the device. This hardware is not yet available on most production phones.
Recent version of Android introduced the support for more advanced power monitoring at the hardware subsystem level, known as “Power rail counters”. These counters measure the energy drained by (groups of) hardware units.
Unlike the battery counters, they are not affected by the charging/discharging state of the battery, because they measure power downstream of the battery.
The presence and the resolution of power rail counters depends on the device manufacturer. At the platform level this data is obtained polling the Android IPowerStats HAL.
Simplified block diagram:
Trace proto: PowerRails
Config proto: AndroidPowerConfig
Sample config:
data_sources: { config { name: "android.power" android_power_config { battery_poll_ms: 250 collect_power_rails: true # Note: it is possible to specify both rails and battery counters # in this section. } } }
See also the CPU -> Frequency scaling data source.