Using Cast MLT Screencast Features While Sideloading Android TV Apps

Updated 2026-10-29

Using Cast MLT screencast features while sideloading Android TV apps

Why Cast MLT Screencast Support Matters on Android TV

When you install an app from outside the Play Store, Android TV sometimes forgets to register the Cast MLT (Media Transfer Protocol) screencast targets. That means voice commands, picture-in-picture, and background screencast output stop working once the app is installed via sideload. In practice, this shows up most often with smart‑home integrations (e.g., Hue, Nest) and media players that rely on casting their display output through the system’s MLT pipeline. Fixing it takes only a few configuration steps, but many guides skip them entirely.

Preparing Your Sideload Package

Before touching the TV’s settings, verify your APK includes the correct MLT permissions. Start from a known-good app that you’ve successfully cast before, such as a YouTube or Chromecast skill, and note which versions had working Cast support. That baseline will tell you whether the issue is the app itself or the launcher environment. Sideloading from a trusted source—preferably a direct download of app-release.apk or an ALM (Android Loader Manager) package—avoids the Play Store restrictions on broadcast intents. Keep a copy of the original AndroidManifest.xml in case you need to patch the android.permission.CAST and related MLT flags yourself.

Enabling MLT Screencast Targets via Settings

After sideloading, open Settings → System → Input & Accessories → ScreenCast. Make sure the toggle is on, then select your display source (HDMI‑CEC works best). Next, tap the “Manage Targets” option in Developer options. This screen appears only after enabling Developer options, which you can reach by holding the Home button for three seconds or entering settings y=3 during boot. Confirm that the app you sideloaded now appears in the target list. If it does not, force a restart of the launcher; the sideloaded apps often lose MLT state on reboot.

Common Pitfalls and Workarounds

MLT version mismatch – Some older sideloaded apps bundle an outdated MLT library. If the Cast icon is missing from the target picker, reinstall the app from a build that includes MLT 1.3 or later.
CEC vs. manual HDMI‑CAST – CEC commands can override your display selection and break casting. Use the manual HDMI‑CAST option when you want explicit control over which TV receives the MLT stream.
Power‑on configuration limits – On some firmware builds, the first Cast session after power‑on resets to the default profile. After sideloading, run the “Cast Test” widget once before launching other apps to re‑seed the MLT target map.

Testing and Verifying the Connection

Launch the sideloaded app, press the TV’s Cast button (or pull up the smart‑phone Quick Settings menu), and verify that the on‑screen message displays “MLT screencaster connected.” You can confirm the connection more rigorously by opening the Cast Control overlay on the app and checking that the “Source” field matches your intended TV. If the source is blank, repeat the device pairing flow using the Chromecast app as a bridge: cast to Chromecast first, note the reported screencast format, then switch back to your sideloaded app.

When and Why to Revert to a Sideloaded App

Not every app needs MLT screencast support. If the app you’re testing is a simple utility (weather, calculator, or a custom media player that doesn’t handle casting), sideloading it mainly saves you from the Play Store’s install restrictions without delivering any functional gain. The real trade‑off is between convenience (Play Store auto‑handles Cast registration) and flexibility (sideloading lets you install newer builds with fixes that the store hasn’t pushed yet). For mission-critical casting workflows—like using a Chromecast‑enabled projector with a custom HDMI‑MTP scene controller—a proper sideload with MLT enabled is worth the extra setup time.

Summary Checklist

Verify MLT permissions in the sideloaded APK before installation.
Enable Developer options and the ScreenCast target list.
Select the correct display source and confirm the target appears.
If the target is missing, retry casting through a known‑good app first.
Use CIP (HDMI‑CAST) or manual selection when the automatic fallback misfires.

By following these steps, you can safely install Android TV apps outside the Play Store and keep Cast MLT screencast functionality intact. The process is straightforward, but the occasional gap in embedded MLT support is what makes this tutorial necessary for anyone who builds or tinkers with their TV beyond stock apps.