Android TVでブラウザベースのAPK配布を一時停止してSideloadを試す手順

更新日 2026-10-31

Installed browsers on Android TV carry pre-installed packages, and many third-party APKs stop working once the store block is active. For those of us who distribute custom builds to testbeds or private networks, the clean break is often to set aside the official channel and run the browser-based APK distribution channel temporarily, then switch back to a controlled sideload flow. This note covers the exact steps, the UI changes to expect, and the pitfalls around the sideload handover.

Why do we temporarily pause browser-based APK distribution?

Most of our project groups use direct APK files shared over HTTPS or a corporate transfer tool. The browser distribution method makes sense when you need to push updates to a large number of devices without maintaining a separate installer pipeline on each machine.

On Android TV, the default Chrome-like browser (and some Samsung browsers) runs the same WebView + JavaScript runtime used by the OS. When Google Play services are disabled, or when a policy update blocks the store, the browser becomes the only delivery path. However, once the store blockade is permanent, the browser APK stops being useful—users cannot verify the signature or integrity of the site’s payload through the Play Store.

The reason to pause distribution is simple: keep the two flows separate. We stop pushing through the browser while we prepare the sideload package. This avoids confusion, reduces the risk of installing the wrong version, and gives a clear separation between “the app is available” and “we have signed and verified the APK.”

Step-by-step: pausing the browser-based APK and preparing the sideload

The first thing to remember is that Android TV shows the browser as the native “Chrome” app on Samsung and Tizen-derived branded models, but the actual binary is a proprietary build. The exact menu labels differ, so treat the procedure as a sequence of UI checks rather than a fixed button.

1. Open Settings > Apps > All apps. On Samsung the UI is called “Apps,” on other brands “アプリ” (apps) or “システムアプリ” (system apps).
2. Find the browser entry (usually “Chrome” or “Samsung Internet”). Tap it, then choose “Uninstall.” Do not actually remove it yet—just inspect the permissions screen. Verify that the “Package update” toggle is off and that “Google Play Protect” is disabled.
3. In the browser’s tab, go to the download history panel. Select all downloaded APK files and delete them. This is the moment where the browser distribution channel is effectively paused: the browser can no longer auto-download external APKs.
4. Confirm that the download sync point is cleared. On a 2020+ Sony TV, clearing the download history for the browser clears the cached APK list entirely.
5. On your computer, run Android’s ADB sideload command against the target TV: adb shell pm install --gapper=false -t <package>.apk. The -t flag allows installation over the network and bypasses the locked store check. If the TV rejects the install, verify that the APK’s target SDK version matches the TV’s build version.
6. Once the sideloaded APK installs and launches, boot into recovery mode and use the “restore from backup” option if it appears, which can roll the installed browser back to a previous version before we switched channels.

The pause window should last no more than two weeks in practice. The browser becomes the sole browser for new installs, and any leftover APKs in the cache are the ones we uninstalled in step 3.

Sideload procedure and verification checklist

After pausing the browser, the sideload path is straightforward but requires discipline. Most devices on Android TV accept an APK placed on the TV via the network share (SMB/NFS), or a USB flash drive plugged into the TV’s media port.

1. Push the APK to the TV using an FTP server running on your laptop, or copy it to a USB drive and plug it in.
2. On the TV, navigate to Settings > Apps > Advanced > System apps > “Android Package Installer.” Launch it.
3. Browse to the APK location and select it. Wait for the package name to appear in the install dialog.
4. Confirm installation. The TV may show a “Package verified” message, or it may show “No checksum match detected.” On a TV with Play Store intact, the verification badge is important—if the badge is missing, do not open the app.

Verification checklist before testing the app on your primary input:

• The APK is signed with the same key as the released build (same SHA-256 fingerprint in build.prod.properties or your internal manifest).
• The app icon matches the expected screenshot from the release notes.
• The “Package update” toggle remains off in Settings > Apps > Chrome (or the main browser). If it turns on, disable it again.
• Installing through the browser in a subsequent visit produces an error or unexpected behavior—this signals that the sideload is the intended path.

Common pitfalls and how to avoid data loss

A frequent mistake during the switch is keeping both the browser and the sideloaded APK installed for days. Once the sideload succeeds, uninstall the browser APK from Settings > Apps. Removing Chrome (or the equivalent) means the installed APK has no automatic launch path from the browser’s downlinks. The fallback is the sideloaded APK itself.

If the sideloaded APK fails to launch, check the logcat output (adb logcat) for Play Store related errors—even with the store blocked, the system logs the Play Store security daemon’s rejection reason. On some Sony and Philips models the log mentions “market_checker” or “crypto_verify_failed” even when no Play Store account is signed in. These messages usually indicate a corrupted cache in the browser’s WebView cache directory.

For teams that need fast iteration, consider a small wrapper script that automates the pause → sideload → verify sequence via ADB. Script the checkout of the browser’s download list into a CSV before the pause, so you can return to the browser distribution later without losing track of what was distributed.

Summary

Pausing browser-based APK distribution on Android TV is not a complicated step, but it requires careful ordering: disable the store, delete in-browser downloads, then sideload with ADB. The two methods coexist safely as long as you explicitly uninstall the browser after the switch. Follow the verification checklist, and you will avoid the most common pitfalls—unverified installs, duplicate app icons, and Play Store re-enabling due to leftover cached trust tokens.

関連記事：Android TV の他の記事