Device locked on "Powered by Esper" screen after provisioning: configure Blueprint to enable Android Settings and native launcher access

Android

After provisioning, your device may remain locked on the "Powered by Esper" Esper Launcher screen with limited access to Android Settings and other applications. This happens when your Blueprint is configured with a restrictive launcher and app visibility settings. Follow these steps to regain access to device features and applications.

Before you begin

This issue occurs when all of the following conditions are true:

• Esper Launcher is set as the default launcher on your device
• Android Settings access is not enabled in your Blueprint
• No additional applications have been added to your Blueprint's app list

Your device is correctly enforcing your Blueprint configuration — this is expected behavior. You need to update your Blueprint to allow the access you need.

How to enable Android Settings access

1. In the Esper Console, go to Blueprints and select the Blueprint applied to your device.
2. Open the Esper Settings section.
3. Enable Android Settings access. This will surface the native Android Settings app within the Esper Launcher, allowing you to access device settings, USB configuration, and other system functions.
4. Save your Blueprint changes.
5. Go to Devices & Groups → [Your Device] → Blueprint → Apply to push the updated Blueprint to your device.
6. Wait for the Blueprint to converge. Once complete, you can access Android Settings from within the Esper Launcher.

How to add applications to your launcher

1. In your Blueprint, open the Apps section.
2. Add any required applications (such as Messages, Gallery, or a browser). Applications must be explicitly added to appear on the Esper Launcher home screen.
3. Verify that app package names are correct and that apps are available in the managed Play Store or uploaded as private APKs.
4. Save your Blueprint changes and apply them to your device.

How to restore access to the native Android launcher

If you want users to be able to exit to the native Android launcher and access the full Android home screen:

1. In your Blueprint, locate the Default Launcher setting.
2. Change it from Esper Launcher to your device's Native/Stock Android Launcher.
3. Save your Blueprint changes.
4. Go to Devices & Groups → [Your Device] → Blueprint → Apply to push the updated Blueprint to your device.
5. Once the Blueprint converges, users can press the Home button to reach the native launcher.

Troubleshooting

Blueprint changes aren't appearing on the device

If you've saved Blueprint changes but they're not reflected on your device, confirm that you pushed the updated Blueprint to your device. Blueprint changes are not automatically applied — you must manually converge or push the Blueprint after editing.

Device is offline or unreachable

If your device is offline or was factory reset and removed from the Esper Console, re-provision it with the corrected Blueprint instead of attempting to push updates remotely.

Kiosk lockdown with missing apps

If you want to keep Esper Launcher as the only launcher but certain apps are missing, add those apps to your Blueprint's app list rather than changing the launcher. Verify that app package names are correct and that apps are available in your managed Play Store or uploaded as private APKs.

"Messages can only be used by the owner of the device" error

This error indicates a work profile or device owner mode restriction unrelated to your Blueprint configuration. Contact Esper Support if standard app-addition steps do not resolve SMS access — this may require investigation into your device owner provisioning mode and multi-user restrictions.

Blueprint converge completes but restrictive behavior persists

If your Blueprint converge completes successfully in the Esper Console but your device continues to display restricted launcher behavior with no change, contact Esper Support for assistance.

Still need help?

If you've followed these steps and your device still isn't responding as expected, submit a support ticket with details about your device, Blueprint configuration, and the behavior you're seeing.