# The Agent Stops Reporting

> Android Devices that go quiet for hours and then report again are usually being suspended by the manufacturer's battery layer. Here's how to confirm it and fix it.

Source: https://docs.applivery.com/en/device-management/android/troubleshooting/agent-not-reporting/  •  Last updated: 2026-09-11

**Key topics:** Ruling out Doze, Manufacturer battery exclusions, Devices marked as inactive, Applivery, Android, Xiaomi, OPPO, Samsung

---

**TL;DR:** A Device that goes quiet for hours and comes back is usually being suspended by the manufacturer's battery layer. Exclude the agent from battery optimization.

A Device reports normally for a while, then goes quiet for most of a day, then reappears as if nothing had happened. Nobody touched it, nothing failed, and it was often sitting on a charger the whole time.

That is almost always the manufacturer's **battery layer** suspending the Applivery agent to save power. Many Android manufacturers add their own power management on top of Android's, and it is far more aggressive: it decides which background Apps get suspended, and the agent is treated like any other App.

## Ruling out Android's own power saving

Android has its own mechanism, Doze, and it is the obvious suspect. It is usually the wrong one.

:::info
**Doze does not apply while the Device is charging.** So if the Device was plugged in and still stopped reporting, Android's own power saving is ruled out and the cause is the manufacturer's layer. This single check separates the two.
:::

## Excluding the agent from battery optimization

The fix is to tell the Device to leave the agent alone. The exact route depends on the manufacturer and on the version of its Android skin, so treat these as a starting point rather than exact steps.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Manufacturer</p></th><th colspan="1" rowspan="1"><p>Route</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Redmi / Xiaomi</strong></p></td><td colspan="1" rowspan="1"><p>Settings → Apps → Manage apps → select the App → turn on <strong>Autostart</strong> and set battery saver to <strong>No restrictions</strong>.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>OPPO</strong></p></td><td colspan="1" rowspan="1"><p>Settings → Battery → select the App → allow <strong>background activity</strong> with no restrictions.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Samsung</strong></p></td><td colspan="1" rowspan="1"><p>Settings → Battery → Background usage limits → check the App is <strong>not</strong> listed under "Sleeping apps" or "Deep sleeping apps".</p></td></tr></tbody></table>

:::warning
**Exclusions can be reverted by a firmware update.** Build them into your periodic checks on affected models rather than treating them as a one-off fix.
:::

For per-brand detail, [dontkillmyapp.com](https://dontkillmyapp.com) is a useful community reference. It is not official documentation, so use it alongside the manufacturer's own settings rather than instead of them.

## Devices marked as inactive

A Device is marked as inactive after 5 days without reporting, so a suspended agent is one of the ways a perfectly healthy Device ends up flagged. See [Device States](https://docs.applivery.com/en/device-management/general-settings/device-states/) for what the status fields actually mean.

If the exclusion is in place and the Device still goes quiet, contact Applivery Support: we can review the agent activity on that Device and confirm whether it is still being suspended.