How to Migrate Sideloaded Android TV Apps to a New Device and Keep

Updated 2026-10-30

Migrating previously sideloaded Android TV apps to a new device

What you need before you move your apps

If you’ve sideloaded apps onto Android TV using APK files or a helper tool, the first thing to do is confirm which apps actually depend on local storage, custom skins, or network services. Some apps that looked portable in theory break the moment they’re on a different IP address or hardware revision, and that’s why a clean install without them is often the healthier choice. Gather the APKs you originally installed, the version numbers you used, and any notes about root or special launchers you set up—those details save time when you rebuild the environment on the new box.

Check that the new Android TV platform supports the APK target SDK your apps were built against; Google updates the minimum supported API level periodically, and apps targeting older levels may crash when launched from a different device. You also want to verify that your new device has the required storage space and that the TV’s region settings match the original, since some packaging ties install to a locale.

Step 1: Back up everything you can

The safest migration path starts with a complete backup of the app list and configuration. On most Android devices you can’t pull an app off the system without root, but for sideloaded apps the situation is easier: you already have the .apk (or a bundled .jarni) and its permissions.

Run adb shell pm list packages -s on the old box and save the output. Filter for the sideloaded entries, then copy each APK to a fast USB OTG drive or network share. While you’re at it, record the exact versions in the package’s meta-info section (package.vendor, package.version). Many home-media boxes use custom launchers and media-scanners; those live as separate .apks, so don’t overlook them.

Step 2: Install the same APKs on the new Android TV

Connect the new TV to your development PC over ADB. Verify connectivity with adb devices, then push the backups:

adb push MyApp.apk /sdcard/MyApp.apk

Install each file with adb install --install-target /sdcard/MyApp.apk. Because sideloaded installs land outside the system partition, keep them in /sdcard/ or in a private directory and launch them manually from the Home screen. For apps that need root access (screen capture, overlay injection, or custom input), you’ll need a rooted image of the new device and su to copy binaries into /system/xbin; skip rooted installs if your device isn’t rooted.

After installing, run each app once to let it register with the backend services. If the app was using a local database for settings, clear that data so the defaults reset to what you configured on the old box.

A short list of apps that commonly cause friction during migration:

Custom media players that scan network folders
Screen-capture tools requiring overlay permission
Background services that store state in SharedPreferences
Apps tied to a specific account profile that doesn’t carry over

Question: Why does the launcher still stutter after I sideload?

One frequent complaint after moving sideloaded apps is visual glitching, slow UI rendering, or stutter. This usually stems from three causes: mismatched resources (the app was compiled for API 28 and now runs on API 34 without the right manifest flags), leftover cached data from the previous installation path, or the fact that the new TV’s HDMI-ARC timing differs from the old box, causing the TV’s own skinning layer to conflict with the launcher’s theme. Remove all caches (adb shell pm clear <package>), delete the app’s data folder, and reinstall fresh. If it persists, roll back the launcher to its factory state and reinstall just the brand-new apps first—only re-add the heavy media tools after confirming the baseline chain works.

Step 3: Test and validate on the new box

Once the migrated apps are running, walk through the typical user paths. Launch your media server client, browse the library, and check that transcoding or remote playback behaves as expected. Run the same app-specific tests you did on the old device: open the camera or microphone, toggle picture-in-picture, and confirm network-dependent streaming starts without errors. If the app worked on the original device, it should work here—anything missing suggests either a hardcoded path to the old device’s network interface or a service that was using an API the new OS changed.

If you rely on Voice Assistant integration, reconnect the TV’s mic and trigger a command; sometimes the voice app’s background service fails to start after a fresh install because it expects a specific android.hardware.audio flag present in the previous build.

Step 4: Final cleanup and housekeeping

Delete the duplicate copies of the sideloaded packages on the new TV. If you kept the old box running the original apps, uninstall them cleanly; leaving them behind creates confusion for future updates and can waste storage. Re-enable any custom themes, and ensure the Home screen layout matches what you’re used to—you may need to recreate the widget positions that the original launcher set up.

Common pitfalls and how to avoid them

Many users assume that any APK will work anywhere, but Android TV’s sandboxing is stricter than a phone’s. Apps compiled for older OS releases sometimes fail to start on newer TV builds because the manifest declarations change. Before pushing your full catalog, test a representative subset: pick one streaming app, one media player, and one utility. If those three succeed, the rest of the list is likely fine too.

Another trap: forgetting to update the Google Play Services and SmartThings services that some media apps rely on. A freshly sideloaded Netflix client on a 2019 Android TV box might launch, but without updated Play Services it could refuse to sign in. Update system services first, then install your sideloaded apps on top.

Conclusion

Migrating sideloaded apps to a new Android TV is straightforward when you treat the process as a deliberate rebuild rather than a copy-paste. Back up your APK list, push it over ADB to the new device, clear old caches, and validate functionality before fully committing. The small effort you invest in testing the migrated subset first pays off by catching resource-specific bugs before they reach your living room.