> For the complete documentation index, see [llms.txt](https://docs.sentiance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sentiance.com/sdk/appendix/android/android-wake-lock-usage.md).

# Android Wake Lock Usage

## Why the Sentiance SDK Uses Wake Locks <a href="#why-the-sentiance-sdk-uses-wake-locks" id="why-the-sentiance-sdk-uses-wake-locks"></a>

The Sentiance SDK delivers contextual intelligence by collecting motion data, like accelerometer and gyro readings, in the background. To achieve this, Android requires the device to remain awake. Wake locks ensure that during short periods of motion-triggered data collection, the device doesn’t sleep, allowing us to deliver accurate insights.

## Google Play Vitals Warning <a href="#google-play-vitals-warning" id="google-play-vitals-warning"></a>

<figure><img src="/files/8Q5cGwgWeQODSHYqbTFR" alt=""><figcaption></figcaption></figure>

Google Play monitors wake lock usage. If more than 5% of users have wake locks exceeding two hours over a rolling 28-day window, a battery usage warning may appear. The Sentiance SDK is designed to minimize wake lock usage. Wake locks are held only when motion is detected, and once data collection completes, the lock is released. As users move, wake lock duration varies, but it remains purpose-driven.

## Our Commitment

We prioritize both user experience and battery life. Wake locks are held only when needed, during motion-based data collection. We rigorously test the SDK to ensure wake lock usage stays within expected, minimal boundaries before release.