Android

Using ESPL on Android — what to watch for

Step sync and permissions are where people get stuck — read these first

A rundown of the friction points Android users hit with ESPL. Behavior can vary by device, Android version, and manufacturer — treat what's below as general checkpoints rather than literal steps.

01 / Key Points

Four things Android users should know first

You don't need to memorize specific menu paths. Keeping these four in mind avoids most of the friction.

  • Allow health-data integration

    To read your steps, ESPL needs permission to integrate with your Android's health-data manager (Google Fit / Health Connect, etc.).

  • Mind battery optimization

    On Android, battery optimization can affect how apps behave. If steps stop syncing, excluding ESPL from optimization sometimes helps.

  • Notification permission

    If notifications are turned off, you won't get ESPL announcements or challenge-related alerts. Grant the permission as needed.

  • Manufacturer-specific battery management

    Some device makers ship their own battery management (autostart permission, background restrictions, etc.) on top of Android's. These can affect app behavior.

02 / Steps Tracking

Notes on step tracking

ESPL reads steps from your Android device's health data. How health data is managed varies by Android version and device (Google Fit, Health Connect, etc.).

As long as you follow the in-app prompt and grant read permission for the integration shown, steps will sync without issue.

03 / Permissions

Notes on permissions and device settings

On Android, background activity is restricted to save battery. That can affect step intake and notifications.

In general, in your device's “Settings”, check these for ESPL:

  • Excluded from battery optimization
  • Notification permission granted
  • If needed, autostart permission granted

04 / Common Issues

Common issues

  • Steps aren't syncing or updating

    First, check your health-data integration settings (Google Fit, Health Connect, etc.) and confirm ESPL is allowed to read health data.

    Also check your device's “battery optimization” settings and confirm ESPL is excluded from optimization.

    If that doesn't fix it, please reach out to support with your device, Android version, and manufacturer.

  • The app keeps getting killed in the background

    Battery optimization or manufacturer-specific battery management (autostart restrictions, etc.) is often the cause.

    Adding ESPL to the allowlists under “apps”, “battery”, and “background” settings on your device can improve things.

  • Should I use Health Connect or Google Fit?

    Health-data management differs across Android versions and devices. As long as you grant the permission shown by the in-app prompt, you'll be fine.

    If both are installed, behavior may vary by environment — please contact support if you need clarification.

How iPhone differs (for reference)

  • Where health data lives

    On iPhone it's consolidated in HealthKit (a standard app). On Android, it depends on the version and device.

  • Battery optimization

    Android tends to apply tighter background restrictions, so battery optimization has more impact than on iOS.

  • Manufacturer variation

    Android devices add manufacturer-specific battery management, so even at the same Android version behavior can vary by device.

If you can't resolve it, please reach out via the contact form (sharing your device, Android version, and manufacturer makes investigation faster).

Next

What to read next