Esper Agent crashes on Lenovo Tab K11 Gen2 running Android 16: upgrade to resolve

Android

If your Lenovo Tab K11 Gen2 running Android 16 is experiencing repeated Esper Agent crashes during device configuration or Blueprint application, you can resolve this issue by upgrading to Esper Agent v7.12 or later.

Before you begin

This issue occurs when an older version of the Esper Agent is installed on a device running Android 16. Android 16 introduced API and behavioral changes that require a compatible agent version. Upgrading the Esper Agent will resolve the crashes and allow your device to complete provisioning and Blueprint configuration.

How to verify your Android version

1. On your device, open Settings.
2. Navigate to About Tablet.
3. Verify that your device is running Android 16.

How to check your current Esper Agent version

Check your Esper Agent version using the Esper Console:

1. In the Esper Console, go to Devices & Groups.
2. Select your device by name.
3. Open Device Info.
4. Look for the Esper Agent version field to see your current Esper Agent version.

Alternatively, check directly on your device:

1. Open Settings on the device.
2. Navigate to Apps.
3. Select Esper Agent.
4. Open App Info to view the version number.

How to upgrade the Esper Agent

1. Ensure your tenant has agent auto-update enabled, or contact Esper Support to obtain the latest Esper Agent APK.
2. If you have the APK file, you can push it to your device using ADB or deploy it through your Esper Console device management workflow.
3. Once deployed, allow the upgrade to complete. The device will restart as part of the upgrade process.
4. Verify that the device has updated to Esper Agent v7.12 or later by checking the Esper Agent version field in Devices & Groups → Device Info.

How to reapply your Blueprint after upgrade

1. In the Esper Console, go to Blueprints.
2. Select the Blueprint you want to apply.
3. Choose Apply to Devices/Groups.
4. Select your affected device or device group.
5. Complete the Blueprint application.

How to verify the issue is resolved

After applying the Blueprint, confirm that:

• The device completes Blueprint application without crashing.
• Your device appears as Online in Devices & Groups.
• Your device shows as Compliant in the device details.

If the issue persists

If you continue to experience crashes after upgrading to Esper Agent v7.12 or later, collect offline Esper Agent logs for Esper Support to review:

How to collect and pull Esper Agent logs

1. Install ADB (Android Debug Bridge) on your computer.
2. Connect your device to your computer via USB cable.
3. Enable USB debugging on your device:
   • Open Settings.
   • Navigate to About Tablet.
   • Tap Build Number seven times to enable Developer Options.
   • Go back and open Developer Options.
   • Enable USB Debugging.
4. On your device, tap the Device ID field 5–6 times. You should see a "Fetching logs" message appear.
5. On your computer, run the following command to pull the logs:

   adb pull /storage/emulated/0/Download/dpc_logs.zip <local_destination_path>

6. Save the dpc_logs.zip file and submit it to Esper Support along with a description of the issue.

Still need help?

If you've completed these steps and your device is still experiencing issues, contact Esper Support. Be sure to include your device name, current Esper Agent version, Android version, and the dpc_logs.zip file if you collected it.