S-Patch app appearing to terminate during Esper Agent activity: ECG BLE data transmission interrupted on Lenovo K11 (investigation inconclusive — contact Esper Support

Android

If your S-Patch cardiac monitoring app is disconnecting from your wearable ECG device when Esper is active on your device, this article explains what's happening and how to help us diagnose the issue.

What you should know

We've identified reports of the S-Patch app (package com.wellysis.accurkardia.accurkardia.mobile) losing Bluetooth Low Energy (BLE) connectivity to paired ECG devices during or immediately after Esper activity. This has been observed primarily on Lenovo K11 devices, though it may occur on other Android devices as well.

Our investigation has not yet identified a root cause. The issue may be related to resource contention during active Esper operations, or it may be caused by factors outside Esper's control. To help us determine what's happening, we need diagnostic data from your device at the exact moment the disconnection occurs.

How to capture diagnostic data

The most important step is to collect a bug report immediately after you notice the S-Patch app has disconnected. Delayed reports will not contain the data we need to diagnose the issue.

1. When you notice the S-Patch app has stopped transmitting ECG data, note the exact time.
2. Go to Esper Console → Devices & Groups → [Device Name] → Overview → Request Bug Report.
3. Submit the bug report request right away.
4. Wait for the bug report to complete.

For more details on collecting bug reports, see Logs and Bug Reports.

How to verify your S-Patch configuration

To rule out app-level restrictions, check the following:

• Foreground service: Confirm with your app provider that S-Patch is configured to run as a persistent foreground service with a visible notification. This provides Android OS-level protection against background termination.
• Background restrictions: Go to Esper Console → Devices & Groups → [Device Name] → Blueprint → Compliance Policy → App Permissions / Power Management and verify that no battery optimization overrides or background app restrictions are applied to S-Patch.

How to reproduce the issue in a controlled environment

If the disconnections happen during active Esper sessions, try this:

1. Open Esper Console → Devices & Groups → [Device Name].
2. Start a remote viewer session on the device.
3. While the session is active, initiate a Bluetooth data transfer from your ECG wearable via the S-Patch app.
4. If the connection drops, immediately request a bug report from the Esper Console.

Capture the exact time the connection fails so you can share it with Esper Support along with your bug report.

Still need help?

If your S-Patch app continues to disconnect, or if you need help interpreting your bug report, contact Esper Support. provide:

• Your device serial number
• The exact timestamps when each disconnection occurred
• The bug reports collected immediately after each failure
• A description of what Esper activity (remote session, bug report collection, etc.) was happening when the disconnection occurred