> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/metrics-reference/app-battery-consumption.md).

# App battery consumption

How much of a handset's battery each app used. The handset's operating system keeps this account for every app and the AMIE Agent reports it, so that a handset that does not last a shift can be traced to the app that drained it.

## How it's measured

The handset attributes the battery it uses to the apps that were running, and reports each app's share as a percentage of a full charge: an app at **25.0 %** used a quarter of a full battery. AMIE records the figures the handset reports; it does not measure the apps itself.

Reports come in while the handset is active. When no app is drawing a measurable amount any longer, the handset sends an empty report. AMIE treats each unbroken run of non-empty reports as a **cycle** of activity — a period of use, not a charging cycle. A busy day can produce several; an idle handset produces none.

## How the product shows it

* [Top App Consumption](/amie-advanced/using-the-platform/device-details/device-top-app-consumption.md) on a handset's page lists, for each cycle in the seven days before its last check-in, the apps by **% of Full Charge**. The figure shown for an app is the most recent one the handset reported during that cycle, cut off rather than rounded to one decimal place, so 12.37 shows as **12.3 %**. AMIE does not add an app's readings together across a cycle.
* [Battery Consumption by App](/amie-advanced/using-the-platform/batteries-overview.md#battery-consumption-by-app) on the Batteries overview is a bar chart totalling the reported consumption per app across every battery in the selected time range, up to 15 apps, the largest first.

Apps are named by package name — the technical identifier such as `com.example.app` — not the name shown on the handset.

{% hint style="warning" %}
TODO: the unit of the fleet-wide **Battery Consumption by App** figure — whether it is a percentage of a full charge, milliamp hours, or another measure — is not stated on the screen. Confirm the unit and how a reader should compare two bars.
{% endhint %}

## What it does and does not tell you

An app at the top of every cycle on a handset with a healthy battery is the likely reason that handset runs down. The same app at the top across the fleet is a configuration or software question rather than a battery one. The figures do not say what the app was doing, only what it cost.

## Edge cases

* **Above 100%.** A single app can report more than a full charge in one cycle.
* **0.0 %.** The handset reported the app with no consumption.
* **Idle handsets.** No cycles, so the section on the handset's page reads **No app consumption data for this device.**

{% hint style="warning" %}
TODO: what a **% of Full Charge** above 100 means for one app in one cycle.
{% endhint %}

## Where you'll see it

* [Top App Consumption](/amie-advanced/using-the-platform/device-details/device-top-app-consumption.md)
* [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md#battery-consumption-by-app)

## Related metrics

* [Battery capacity](/amie-advanced/metrics-reference/battery-capacity.md): whether the battery itself is the reason a handset runs down


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spectralink.net/amie-advanced/metrics-reference/app-battery-consumption.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.