Esper Agent crashing + apps unresponsive on Lenovo IdeaTab (Android 15): contact Esper Support

Android

If your Lenovo IdeaTab running Android 15 is experiencing Esper Agent crashes and unresponsive apps, follow these steps to diagnose and resolve the issue. This guide covers how to check device status, collect diagnostic logs, and test potential fixes.

Before you begin

Gather the following information about your affected device:

Device model (example: Lenovo IdeaTab ZAFR0928US)
Android version (confirm it is Android 15)
Esper Agent version installed on the device
Provisioning method used (QR code or standard provisioning)
Whether the device is in kiosk mode

Step 1: Check device status in the Esper Console

Log in to the Esper Console.
Navigate to Devices & Groups → [Device Name] → Overview.
Check whether the device shows as Online or Offline.

If the device is offline, remote actions will not be available. Proceed to Step 3 to collect logs via ADB instead.

Step 2: Request a bug report from the device (if online)

In the Esper Console, navigate to Devices & Groups → [Device Name] → Actions → Request Bug Report.
Download the bug report when it becomes available.
Open the report and search for crash indicators:

com.esper.Esper Agent (Esper Agent process name)
AndroidRuntime FATAL EXCEPTION (system-level crash logs)

If you find crash logs, note the error details and proceed to Step 4.

Step 3: Collect logs via ADB (for offline or unresponsive devices)

If the device does not respond to remote actions, use ADB to collect logs directly:

Connect the device to a computer via USB cable.
Ensure ADB is installed on your computer. Learn how to set up ADB.
Open a terminal or command prompt and run:

adb logcat -b all > device_crash_log.txt

This captures all system logs. Let it run for 2–3 minutes, then press Ctrl+C to stop.

Optionally, filter for Esper Agent–specific errors:

adb logcat | grep -i "esper\|Esper Agent\|kiosk\|DeviceOwner"

Save the output and review for crash messages related to the Esper Agent.

Step 4: Check the Esper Agent version

Run the following ADB command:

adb shell pm dump com.esper.Esper Agent | grep versionName

Note the version number displayed (example: versionName=6.15.0).
Verify that this version officially supports Android 15 on MediaTek Dimensity 6300 devices. If you are unsure, contact Esper Support with the version number.

Step 5: Test device stability by stopping the Esper Agent (for diagnosis only)

If the device is completely unresponsive and you need to restore basic functionality for further diagnosis, you can temporarily stop the Esper Agent:

Run:

adb shell am force-stop com.esper.Esper Agent

Observe whether the device becomes responsive.
Do not keep the Esper Agent stopped for extended periods, as this removes device management.

Step 6: Test with kiosk mode disabled (for affected devices only)

If you have multiple affected devices, test the following on one unit:

Perform a factory reset on the device.
Re-provision the device using a test Blueprint with kiosk mode disabled.
Monitor the device for 24 hours. If the Esper Agent remains stable and does not crash, the issue is specific to kiosk mode configuration on Android 15.
Share this finding with Esper Support, as it will help narrow down the root cause.

Step 7: Verify the fix

After applying a solution, confirm that:

The device appears Online in the Esper Console.
Remote actions (reboot, fetch device info) succeed.
Kiosk apps launch and run without crashing.

Still need help?

If the issue persists after following these steps, or if you have identified a crash in the Esper Agent logs, contact Esper Support. include:

The device crash logs or ADB logcat output (especially the full stack trace if available)
The Esper Agent version number
Device firmware version (run adb shell getprop ro.build.version.release and adb shell getprop ro.build.fingerprint)
Steps you followed to provision the device and the Blueprint configuration
The number of devices affected