Custom Launcher App and Custom Boot Audio Support in Esper Kiosk Mode

Android

Custom boot audio

Why this happens

Boot sounds are stored in protected system partitions written at the OEM firmware level. Android MDM agents, including the Esper Agent, operate in the application layer and cannot access or modify these partitions on standard commercial devices. As a result, Esper cannot override or replace firmware-resident boot audio directly.

Workaround: play audio on app startup

If your OEM does not provide a mechanism for replacing boot audio at the firmware level, you can approximate the behavior by triggering audio playback when your kiosk or launcher app initializes. This works with .ogg and other standard Android audio formats.

Review your device OEM's firmware documentation to confirm whether your hardware model supports system partition customization or exposes a mechanism for replacing boot audio. If it does, follow the OEM's process rather than this workaround.
In your kiosk or launcher application code, implement audio playback triggered by the onResume() lifecycle event or application startup. Store the audio file in the application's accessible storage — not in a system partition.
Build and sign the updated APK, then deploy it to devices via Apps & Configuration → Apps and apply it through the relevant blueprint.
Reboot the device and confirm the audio plays after the launcher initializes.

Verify: After reboot, the custom audio should play once the kiosk or launcher app finishes initializing. Note that playback will begin after Android completes its boot animation — it cannot replace hardware-level boot sound or the Android boot animation itself. This is an expected limitation of the application-layer approach.

If this doesn't resolve it

If the custom launcher settings are not applying after confirming the agent version and blueprint configuration, or if you need guidance on a specific OEM's boot audio customization mechanism, contact Esper Support with the following information:

Device make, model, and Android version
Esper Agent version from Devices & Groups → [Device Name] → Device Info
A screenshot or export of the blueprint configuration
The Activity Feed output from the affected device showing the blueprint application attempt

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.