Excessive background battery drain (Andriod)

[juliuswms]

What happened?

On Android, the app consumes a lot of battery in the background (~22.1% battery with 15 minutes of screen-on time). This makes daily-use and stress testing impractical.

Steps to reproduce

1. Install app
2. Keep it running in the background

App version

0.9.21+52

Platform

Android (APK)

Phone model and OS version

Samsung Galaxy S22, Android 16

Which band?

WHOOP 4.0

Screenshots

From looking at the code and with the help of DeepSeek I was able to understand that after the App starts, the BLE Connection is opened indefinitely. Pulling the heartbeat very frequently (10s) and pulling the banked data from the WHOOP every 15 min. My guess would be that this constant BLE connection is the reason the battery drain is this high. Maybe with a "Power save" option it could only connected every 15 min, pull the banked data and close the BLE Connection again (I guess this would come with the downside of not being able to use the Double-Tap on the WHOOP to eg. skip a song. Seeing that that would require a constant connection).
I also understand that power optimization at the start of a project like this one is not as much of a focus as new features but for me it makes daily driving this App kinda hard.

Quick checks

• The official WHOOP app is not also connected to this band
• I've searched existing issues for this

[gerageragarza-prog]

Algoritmo de reconexión (backoff exponencial acotado) — el que preguntaste

ReconnectBackoff.kt (implementación completa, 35 líneas, fácil de portar a C):
https://github.com/ryanbr/noop/blob/main/android/app/src/main/java/com/noop/ble/ReconnectBackoff.kt
ReconnectBackoffTest.kt (casos de prueba, útil para validar tu port a ESP32):
https://github.com/ryanbr/noop/blob/main/android/app/src/test/java/com/noop/ble/ReconnectBackoffTest.kt

Cliente BLE principal (Android) — cadencia de offload, power saving, uso del backoff

WhoopBleClient.kt (7790 líneas — usa view_range en tu editor si lo clonas, es grande):
https://github.com/ryanbr/noop/blob/main/android/app/src/main/java/com/noop/ble/WhoopBleClient.kt
Constantes de cadencia de offload (línea ~682-687, BACKFILL_INTERVAL_MS / LOW_BATTERY_BACKFILL_INTERVAL_MS):
https://github.com/ryanbr/noop/blob/main/android/app/src/main/java/com/noop/ble/WhoopBleClient.kt#L682-L687
Uso del backoff exponencial en el flujo de reconexión (línea ~7227):
https://github.com/ryanbr/noop/blob/main/android/app/src/main/java/com/noop/ble/WhoopBleClient.kt#L7227

Lógica equivalente en iOS/Mac (Swift) — por si tu Edge algún día también corre companion en Apple

BLEManager.swift (contiene el didFailToConnect con la misma fórmula min(60, 3 * 2^(n-1))):
https://github.com/ryanbr/noop/blob/main/Strand/BLE/BLEManager.swift

Power saving / aplicación de preferencias (Android)

AppViewModel.kt, función applyPowerSaving:
https://github.com/ryanbr/noop/blob/main/android/app/src/main/java/com/noop/ui/AppViewModel.kt#L1048