How to maintain sideloaded app caches and data on Android TV

Updated 2026-10-31

Maintaining sideloaded sideloaded app caches and data on a minimal Google TV platform

What sideloading means for Android TV

Sideloading on Google TV means installing APKs outside the Play Store, usually via ADB adb install or an APK file copied to the device. On a minimal TV platform this carries extra weight: there is limited storage, no easy way to uninstall a package, and a set of system services that expect certain cache layouts. When you rebuild the OS, update the firmware, or reset the box, unmanaged sideload content can either vanish or break the display. Understanding what you have before you touch anything is the first step to keeping your custom app stack healthy over years of use.

Why cache integrity matters on minimal devices

Low-resource Google TV hardware typically has less than 8 GB of storage and often a shared partition for system and user files. Sideloaded apps create caches for updates, configuration, and offline content. If those caches get truncated during a factory reset or overwritten by an OTA, the app may stop launching or lose features you depend on. In some cases corrupted caches cause the system UI to hang while it tries to read stale data. Maintaining clean, readable cache directories before and after major changes reduces the risk of a hard reset turning into a paperweight.

How to back up sideloaded caches safely

Before any reset, network wipe, or firmware upgrade, perform these steps:

Pull a complete image of the storage partition if the device allows it. Many Android TV boxes expose “backup” via ADB when connected to a PC.
Locate the app’s private cache folders: /data/data//cache and /data/misc/cache on most models. On minimal builds the path may be shorter, but the structure stays.
Copy each cache folder to a separate USB drive or SD card if the box has a USB port. Google TV units with built-in USB typically accept HDDs or sticks for direct backup.
Record the app version and installation date. Some sideloaded packages include license certificates or stored credentials that will not be re-registered after a factory image restore.

Avoid using third-party file managers that require root access on minimal builds; a mistake during a partial write can degrade system partitions.

Safe sideloading workflow for long-term use

The goal is to minimize the number of times you touch the installation layer, because each change pushes the cache tree further outside what the recovery tools understand. Follow this pattern each time you add or replace an app:

Uninstall the old version with adb uninstall . This clears its cache directory along with the binaries.
Delete the old cache folders manually: rm -rf /data/data/com.example.app/cache and the matching /misc/cache entries.
Install the new build, then immediately verify that the app starts and writes new cache files without error messages.
Only after confirming functionality copy the new cache layout to backup storage.

This method keeps the rollback window small. If a problem appears, you can revert with a single factory reset and still have the prior sideloaded version on a separate storage medium.

Where to store caches without risking a system brick

Google TV hardware varies widely: some NVIDIA Shield TV models run the full TV edition of Android TV with a robust filesystem, others are more constrained and lack easy recovery interfaces. Treat every non-OTAP partition as “do not delete.” If your box supports a recovery partition or a built-in “backup and restore” screen in Settings > System > Backup, use it. Otherwise:

Keep backups on a separate media stick rather than on the TV’s internal eMMC. Removing and reinserting the internal storage during a system update is harder to reverse.
Avoid sharing a single USB drive between the TV and other PCs if the device’s filesystem isn’t formatted with clear separation; cross-contamination of cache folders has caused boot loops on a few budget models.

Updating firmware without losing app caches

Factory images for minimal Android TV often overwrite usr/data and leave system caches intact. Before flashing:

Check the image hash against the official release note. Google’s firmware packages list exact cache preservation policies.
If the firmware update includes a “system reset” option, choose “keep my data” rather than “factory reset” when possible. That choice tends to preserve the /data/apk cache area.
After the update, reboot twice and run the app through a smoke test. If the app launches but missing assets, re-copy the original cache from your backup before reinstalling the updated package.

When the official update doesn’t support data retention, sideload a temporary copy of the app onto a second device, wipe the first device, and transfer the working software. It costs an extra purchase but saves hours of debugging on a device with no recovery menu.

Final checklist for a stable sideload habit

Only install from verified sources: official APK archives, trusted sideload sites with MD5 checksums, or previous versions you saved.
Keep a dated log: each entry lists the package name, install date, and whether you cleaned caches afterward.
Limit the number of sideloaded apps on a given build. More packages mean more cache layers that can desync during an OS upgrade.
Test the app after every firmware change and keep the last known-good build alongside the current one on external storage.

Following this approach lets you maintain a functional set of sideloaded applications on a minimal Google TV platform without sacrificing the device to a hard brick or a lost configuration. The extra effort of a proper cache backup pays off the moment you need to recover or upgrade.