Android Settings app not visible on device: enable and publish via Blueprint to restore access

Android

If the Android Settings app is not visible on your managed devices, you can restore access by enabling it in your Blueprint and publishing the changes to your devices.

Before you begin

Verify that:

• You have access to the Esper Console
• You know which Blueprint is currently applied to the affected devices
• Your devices are online or will be online soon (offline devices will receive the update when they reconnect)

Step 1: Find the correct Blueprint

1. In the Esper Console, go to Devices & Groups
2. Select one of the affected devices
3. Check which Blueprint is assigned to it — you'll need this name in the next step

Step 2: Enable the Android Settings app

1. In the Esper Console, go to Blueprints
2. Select the Blueprint you identified in Step 1
3. Navigate to Esper Settings
4. Find the Android Settings App toggle and turn it on

Step 3: Publish and converge the Blueprint

1. Click Publish
2. In the Publish Blueprint dialog, check the box for Publish and converge devices
3. Confirm the action
4. Wait for the converge process to complete — this pushes the updated configuration to all devices using this Blueprint

Step 4: Verify the Settings app is accessible

On an affected device, check that the Android Settings app icon is now visible and opens correctly.

If the Settings app is still not visible

• Double-check the Blueprint assignment: Go to Devices & Groups, select the device, and confirm it is using the Blueprint you just published. If it's using a different Blueprint, repeat the steps above for the correct Blueprint.
• Check if the device is online: Offline devices will not receive the converge command until they reconnect to the network. Wait for the device to come online and the update will be applied automatically.
• Collect logs if the device is online: If the device is online and the setting still hasn't applied, collect logs using ADB:

  adb shell logcat -d -v threadtime > dpc_log.txt

  Then contact Esper Support with the Blueprint name, device serial number, and Esper Agent version.
• Check for custom launcher restrictions: If your device uses a custom launcher with kiosk lockdown, the Settings app icon may need to be added to the kiosk app list in addition to being enabled in Esper Settings.

Important notes

• Always check Publish and converge devices when publishing. Publishing without this option will update the Blueprint version but will not push changes to already-enrolled devices.
• Enabling the Android Settings app grants device users full access to the native system Settings menu. On shared or kiosk devices, consider whether this is appropriate for your deployment before enabling.
• This feature works across all Android OEMs on the Esper platform, not just Samsung devices.

Still need help?

If you've completed these steps and the Settings app is still not accessible, contact Esper Support. Have the following information ready:

• Blueprint name
• Device serial number(s)
• Esper Agent version
• Esper Agent logs (if collected via ADB)