> 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/using-the-platform/device-details/device-top-app-consumption.md). # Top App Consumption **Top App Consumption** is the second of the five sections beneath a device's details. It shows which apps drew the most battery during each unbroken stretch of activity — a cycle — in the seven days before the device's last check-in, one tab per cycle. To reach it, open a device from the Devices [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab and scroll down. ## Why this screen matters When a phone does not last a shift and its battery is healthy, an app is often the reason. **Top App Consumption** ranks the apps by how much of a full charge each used, cycle by cycle, so you can see whether the same app is at the top every time the phone is busy. If it is, the fix is in the app or its configuration, not the battery. Compare with [Battery Consumption by App](/amie-advanced/using-the-platform/batteries-overview.md#battery-consumption-by-app) on the Batteries screen to see whether the same app leads across the fleet. ## Before you start **Top App Consumption** covers the seven days ending at the device's last check-in, not the last seven calendar days. It shows data for the device whose page you are on; the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header has no effect on it. ## Screen layout ![Top App Consumption: one cycle tab and its consumption table.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-75306187ddc4e3dff4cf5ff79a19b85721d3875c%2Fdevice-top-app-consumption.png?alt=media) ### Heading **Top App Consumption** with a bar-chart icon and a **?**. ### Cycle tabs A row of tabs, one per cycle, each labeled with the date and time the cycle began — for example **Sep 18, 6:12 AM** — and, where the cycle's start or end fell outside the week, the suffix **(partial)**. The most recent cycle is selected when the section loads; earlier cycles are to its left. A cycle is one unbroken stretch of activity. The device periodically reports the apps currently consuming battery: while something is running, each report lists apps and their consumption; when consumption falls away, the device sends an empty report. A cycle runs from the first report after an empty one to the last report before the next empty one. A busy day can produce several cycles; a device sitting idle produces none. The figures shown for a cycle are its final changed reading: the last report in the cycle whose contents differed from the report before it. Later reports that merely repeated the same figures are ignored, and the cycle's displayed end is the time of that reading, which can be earlier than the cycle's last report. When the device reported no app consumption in the seven days before its last check-in, the section reads **No app consumption data for this device.** ### The selected cycle A line beneath the tabs reads start, an arrow, end and duration, for example **Sep 18, 6:12 AM → Sep 18, 2:47 PM · 8.6h**. The duration runs from the cycle's start to its final changed reading, in hours to one decimal place, or in whole minutes (never less than **1m**) when under an hour. A partial cycle adds, in amber, **Partial cycle — start or end wasn't fully observed in this window.** Below it, a table with a colored square and three columns, ordered from the highest consumption to the lowest. The table scrolls if it is tall. | Column | What it shows | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Package** | The app's package name — a technical identifier of the form `com.example.app`. Hover over a name to see it in full | | **% of Full Charge** | The app's consumption as reported at the cycle's final changed reading, as a share of a full battery charge — a percentage to one decimal place, cut off rather than rounded, so 12.37 shows as **12.3 %** (the screen prints a space before the sign). It is the figure from that one report; AMIE does not add readings together across the cycle. An app the device reported with no consumption reads **0.0 %**. Values above 100% can occur | | (unlabeled) | A horizontal bar, in the row's color, whose length is the app's consumption relative to the top app in this cycle. The top app's bar is full width | {% hint style="warning" %} TODO: what does a **% of Full Charge** above 100 mean for one app in one cycle? {% endhint %} ## Controls | Control | What it does | | ------------------------- | ------------------------------------------------------ | | Cycle tab | Shows that cycle's table. Tabs to the left are earlier | | Hover over a package name | Shows the full name | There is no date range: the week ending at the device's last check-in is fixed. ## Icons and indicators | Icon or indicator | Meaning | When it appears | | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- | ----------------- | | Bar-chart icon before the heading | Marks the section | Always | | **?** beside the heading | Hover over it for a short description of the section | Always | | **(partial)** on a tab, and the amber note | The cycle's start or end was not observed within the week, so its figures cover only the part that was | Per partial cycle | | Colored square before each package | Tells the rows apart and matches the bar in the third column. Colors repeat after eight rows and carry no meaning | Every row | | Highlighted tab | The cycle whose table is shown | One tab at a time | | Spinning icon in place of the tabs | The data has not loaded yet | While loading | ## What to look for * The same **Package** at the top of every cycle tab. That app is a steady drain on this phone. Open [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md#battery-consumption-by-app) to see whether it leads fleet-wide or only here. * One app taking a large share of a full charge in a single cycle. Check the cycle's duration on the line beneath the tabs: the same figure over 8 hours and over 40 minutes mean different things. * Many short cycles in one day. The phone is being used in bursts; each tab is one burst. [Daily Usage Statistics](/amie-advanced/using-the-platform/device-details/device-daily-usage.md) shows the working day they fall within. * **(partial)** on a tab. Its start or end lies outside the week, so it may cover a few minutes or most of a day that you cannot see. Do not compare its figures with a full cycle. * Cycle times that differ from a colleague's. Tab times are in each person's browser time zone — see [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md). ## Metrics on this screen * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — the seven days are a rolling window ending at the device's last check-in ## Related * [Device details](/amie-advanced/using-the-platform/device-details.md) — the details above this section * [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md) — the **Top app** row shows the same reports on a timeline * [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md) — **Battery Consumption by App** across the whole fleet --- # 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/using-the-platform/device-details/device-top-app-consumption.md?ask=&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.