SmartTube: An Android TV Media Client You Install Outside Any App Store

What SmartTube replaces on a television

SmartTube is a media client for Android TVs and TV boxes, written mostly in Java and released under the MIT licence. It browses and plays content from public sources through a remote-friendly interface, and the README lists SponsorBlock integration, adjustable playback speed, 8K resolution support, 60fps playback, HDR compatibility and live chat as features. It does not require Google Services, which matters on TV boxes sold without Play Services.

The audience is narrow by design. The README states plainly that phones and tablets are not supported, and that Samsung Tizen, LG webOS, Apple TV and other non-Android platforms are out. If your television runs Android underneath, including older sets on Android 4.3 (Kitkat), it is in scope. That constraint is the whole product: this is a TV interface, not a general viewer.

How the app is put together

The repository layout shows a multi-module Gradle build. The application lives in smarttubetv/, with shared code in common/ and SharedModules/, and a media layer in MediaServiceCore/. Third-party components are vendored as directories rather than pulled from a package registry: exoplayer-amzn-2.10.6/, leanback-1.0.0/, fragment-1.1.0/, doubletapplayerview/, filepicker-lib/, slidableactivity/, leanbackassistant/ and chatkit/ all sit at the top level. The topics list names Retrofit2 and RxJava for Android, so network calls and asynchronous work follow that stack.

That structure tells you what upgrading costs. Because ExoPlayer and the Leanback support libraries are checked in as source directories, a version bump is a repository change, not a line in a dependency file. The build also depends on Git submodules, which the .gitmodules entry confirms: a plain clone without submodule initialization will not be the whole source tree. For anyone packaging the app themselves, that is the first thing to get right.

Installing SmartTube on Android TV or Google TV

The README is explicit that you should not download SmartTube from any app store, APK website or blog, because those copies were uploaded by other people and may carry malware or ads. The project is not published on any app store. It offers a beta release and a stable release, and describes the beta as recommended because it receives new features and bugfixes faster.

The easiest documented route uses Downloader by AFTVnews. Install it on the television, open it, and enter one of the short codes:

kutt.to/stn_beta
kutt.to/stn_stable

After the download, the README says to read, understand and confirm the security prompts. As an alternative to the short link, the same document gives numeric codes 79015 for beta and 28544 for stable, which require the AFTVnews Downloader browser addon if it is not already installed. Two further methods are listed: transferring the APK from a phone or computer with a file transfer app such as Send Files to TV, or putting the APK on a USB stick and opening it with a file manager such as FX File Explorer or X-plore. The README warns that Android's preinstalled file manager does not work for this.

On Chromecast with Google TV, installation is blocked by default. The README describes enabling Developer Options by clicking the Android TV OS build entry under Settings > System > About until the developer message appears, then turning on the unknown sources toggle under Apps > Security & Restrictions > Unknown sources for the file browser you chose. Advanced users can sideload over ADB, and the README links external guides for that rather than documenting the commands itself.

The security notice you have to read first

The most important paragraph in the README is not about features. The maintainer states that the development environment was infected by unknown malicious software, that a few builds may have been affected, and that after detection everything was wiped, a clean setup was restored, and all builds are now scanned with VirusTotal. The F-Droid version is also to be verified before release. The notice adds that public keys may have been compromised, and that new versions and a new public key are being distributed along with instructions for restoring backups.

This is a real limitation on adoption, and it deserves a direct reading. The project says no extra action is required because the app uses one-time connection codes with limited permissions, which for example cannot change your password. It still offers revocation steps: open myaccount.google.com/security, find "Your connections to third-party apps & services", tap "See all connection", locate YouTube TV or Google Drive, select the app and remove access. If you install SmartTube, that page is worth checking, and the built-in security features the README asks you to keep enabled are worth keeping enabled.

Where SmartTube stops working

The README's own limitation list is short but consequential. Comments are described as unstable. Voice search and casting may perform worse than the official apps depending on the device, which is a device-dependent statement rather than a fixed defect. The bigger boundary is hardware: starting in October 2025, new Amazon FireTV devices no longer run Android, and the README states that SmartTube will not be compatible with the Fire Stick 4K Select and newer devices running Amazon's VegaOS. FireTV devices released before that date remain supported.

Installation itself has failure modes the README names. If installation fails, either disk space is full or the APK did not download correctly, and the fix is to clear space and download again. If the app installs but crashes on open, it was probably installed to an SD card or external storage; it needs to go to internal memory. These are not edge cases on cheap TV boxes with small internal storage, which is exactly the hardware this project targets.

SmartTube next to NewPipe and the official client

The closest comparison in kind is NewPipe, another open source media front end for Android. The difference in approach is the target surface. NewPipe is built for touch on phones and tablets, while SmartTube is built for a D-pad remote on a television, and its README excludes phones and tablets outright. That means the two are not substitutes: if you want one client for a phone and a TV, neither project covers both, and you would be running two applications with two update paths.

The other comparison is the vendor application that ships with the television. The README's feature list is essentially a set of differences from that baseline: SponsorBlock integration, adjustable playback speed, and no dependency on Google Services. The trade-off is that you give up the vendor's distribution channel. There is no store listing to fall back on, updates arrive through the app's built-in updater with changelog, and every install begins with a sideload and a security prompt. Whether that is worth it depends on whether the features matter more to you than the store does.

Maintenance, updates and licensing

The repository is not archived, and the last push was on 2026-09-10, days before a beta release 32.45 on 2026-09-07 and a stable release 32.38s on 2026-09-01. That cadence shows two channels running in parallel, with beta ahead of stable, which matches the README's recommendation of the beta build. The app carries a built-in updater with a changelog, and release notes also appear on the Telegram channel @SmartTubeNewsEN and on the GitHub releases page.

Upgrade cost is mostly borne by the user, not the developer. You re-download an APK rather than receiving a store update, and the Chromecast with Google TV path adds a developer-options step that has to be repeated if the setting is reset. For anyone building from source, the vendored ExoPlayer and support libraries make version upgrades heavier than a dependency bump, and the submodules have to be initialized. The MIT licence is permissive, so redistributing a modified build is allowed, but the README's warning about unofficial copies means a modified build circulating without context is exactly the situation the project is trying to avoid. That is a description of the licence terms, not legal advice.

Editorial conclusion

Adopt SmartTube if you have an Android TV, a TV box or a FireTV device released before October 2025 and you are willing to sideload an APK and confirm the download source yourself. Do not adopt it on a phone, a tablet, or a TV running Samsung Tizen, LG webOS or Apple TV, because the README lists those as unsupported. Before installing, verify the build against the VirusTotal scanning the README says is now applied, and check whether your device falls on the VegaOS side of the October 2025 FireTV split.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. yuliskov/SmartTube on GitHub