Blueprint Convergence Stuck in Drift on Android TV: Free Device Storage to Resolve

Android

Title: Android TV device stuck in Drift — free storage to restore Blueprint sync

When an Android TV device has critically low internal storage, Blueprint convergence fails and the device remains in Drift status instead of returning to Synced.

Why this happens

Android's Package Manager requires contiguous free space equal to or greater than the size of each APK before it can install an application. When internal storage is full or near-full, the Package Manager cannot allocate that space, convergence halts, and the device stays in Drift. This is most common on Android TV boxes with limited built-in storage.

Steps

1. Confirm the error is storage-related. In the Esper Console, go to Devices & Groups → [Device Name] → Blueprint and expand the convergence log. Look for an entry containing Failed to allocate or 0 allocatable. The number in the message (for example, Failed to allocate 243411366 because only 0 allocatable) tells you exactly how many bytes the device tried to reserve — use this as your minimum target for space to free.
2. Uninstall non-essential apps from the Esper Console. Go to Devices & Groups → [Device Name] → Apps and uninstall any applications that are not required by your Blueprint. Removing apps remotely is the fastest method and does not require physical access to the device.
3. Clear additional storage using Remote View if needed. If uninstalling apps alone does not free enough space, go to Devices & Groups → [Device Name] → Remote View to access the live device screen. From there, navigate to the device's storage settings to clear app caches or delete files. Use this method to close any remaining gap between the space freed in the previous step and the target amount.
4. Re-initiate convergence. Go to Devices & Groups → [Device Name] → Blueprint and select Converge. This instructs the Esper Agent to retry applying the Blueprint now that storage is available.

Verify: Go to Devices & Groups → [Device Name] → Overview. The device status should change from Drift to Synced within 10 minutes of convergence completing. Reopen the Blueprint convergence log and confirm no Failed to allocate entries appear in the new run.

If this doesn't resolve it

If the device returns to Drift immediately after a successful convergence, a secondary Blueprint policy — such as a kiosk configuration or device restriction — may also be failing. Review the full convergence log for additional errors beyond the storage entry.

If the device reports available free storage but convergence still fails with 0 allocatable, the device filesystem may be fragmented or corrupted. In this case, factory reset the device and re-provision it through the Esper Console.

If multiple devices are affected and storage is not the cause on any of them, collect the following before contacting Esper Support:

• Device IDs for all affected devices
• The Blueprint ID applied to those devices
• Esper Agent logs collected via ADB:

  adb shell logcat -b all -d > esper_agent_logs.txt

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.