mrkeyoor.com_
Mon 14 Sept 15:47 UTC
Self-Hostedevaluationupdated 14 Sept 2026

SmartTubeLegacy review

SmartTubeLegacy, formerly SmartYouTubeTV, is an archived YouTube client for Android TVs and set-top boxes. It was designed for remote controls, TV resolutions, account login without Google Services, and sideloading on devices such as Fire TV. The maintained SmartTube project is the sensible route for new users.

Verdict

Our SmartTubeLegacy run installed 0 npm packages in 7 seconds but found no build or test target, and GitHub marks the application archived. Keep an existing installation only when replacing it would break an old device workflow, with no expectation of fixes. Everyone starting now should use the active yuliskov/SmartTube successor.

We ran it

Lab card: what happened when we ran SmartTubeLegacyScreenshot of SmartTubeLegacy (github.com/yuliskov/SmartTubeLegacy)
Install✓ · 7s0 packages · 19 MB
Buildn/ano build script
Testsn/ano test script
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo2857 files~221,562 lines of source · 108 MB · 0 CI workflows

Answers from our run

Does SmartTubeLegacy build from source?

Dependencies installed in 7 seconds (0 packages), and the project has no separate build step. We cloned commit c3f8889 into a clean Debian container with 3 CPUs and no project-specific setup.

Does SmartTubeLegacy have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does SmartTubeLegacy have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use SmartTubeLegacy?

New installations: GitHub marks the repository archived, and both the last push and stable release date to October 16, 2023.

What are the alternatives to SmartTubeLegacy?

SmartTube, NewPipe, FreeTube. Our SmartTubeLegacy run installed 0 npm packages in 7 seconds but found no build or test target, and GitHub marks the application archived.

Setup2/5APK sideloading is simple; the source build is undocumented in the README
Docs2/5User install and modes are covered, but source build guidance is absent
Community1/5Archived since 2023 with 447 open issues and pull requests
Maturity2/5A long-lived client frozen against services that continue to change

Who it’s for

Owners preserving an old Android TV setup that already depends on a known SmartTubeLegacy APK.
Developers studying how the former client handled WebView, XWalk, ExoPlayer, remote controls, and device flavors.
Archivists who need the MPL-2.0 source and historical release artifacts.
Advanced users prepared to keep the app isolated and accept that YouTube behavior may change without a fix.

Who it’s NOT for

New installations: GitHub marks the repository archived, and both the last push and stable release date to October 16, 2023.
Users expecting current playback fixes: open issue 845 reports playback failure, and issue 847 reports 1080 modes topping out at 720p.
Developers treating npm as the application build: our install added 0 packages, while the Android project uses Gradle and exposes no npm build target.
Teams requiring current CI and test evidence: our scan found 0 CI workflow files, no tests directory, and no test script.
Phone and desktop users: the interface and launch modes were built around Android TVs, set-top boxes, and remote controls.

Setup reality

Our sandbox installed the empty npm dependency set in 7 seconds: 0 packages were added and the project occupied 19 MB after that step. The 108 MB checkout held 2,857 files and roughly 221,562 source lines. There was no npm build or test target, so both steps were skipped. npm audit reported 0 known vulnerabilities.

The user route is an APK, not npm. The README offers a Fire TV method advertised at under 5 minutes or sideloading with adb install -r. Building source means entering ./smartyoutubetv/, using the Android Gradle project and its submodules, and choosing among product flavors.

GitHub marks the repository archived. Our scan found 0 CI workflow files, no Dockerfile, and no tests directory. Automatic updates and the internal login path may still exist in an installed APK, but there is no active repository maintenance to follow changes in YouTube or Android TV.

The October 2023 archive rules out a fresh deployment

SmartTubeLegacy was built for a problem the official YouTube experience did not always solve well on older televisions. It supports TV screens, remote controls, account login, multilingual search, automatic updates, and playback without Google Services. The README also advertises 4K and says root access is unnecessary. As a historical client, it is easy to understand: download an APK, sideload it, and choose a playback mode suited to the device.

The repository is now archived. GitHub records its last push on October 16, 2023, and the latest release, named Stable, was published the same day with no release notes. An old tag alone would not prove abandonment, but the archive flag is explicit. You can still read and fork the MPL-2.0 code. You should not expect upstream changes when YouTube alters playback, login, or page behavior.

Four launch modes target different old TV playback paths

The starting screen exposes 4 choices: 1080 Main uses WebView, 1080 Alt uses XWalk, 4K Main combines ExoPlayer with WebView, and 4K Alt combines ExoPlayer with XWalk. Users can cap resolution and choose a codec such as 1080/AVC1, then save that choice with the Remember box.

Those switches also date the design. XWalk was an alternative browser runtime, while the project carries many Android product flavors for different devices and application identities. A user must know which mode behaves on a particular box, and the README points to an issue comment for the playback explanation. Open issue 847 reports that its 1080 modes exposed only 720p on an Android 5.1 device with 1 GB of RAM. The report does not establish a general resolution cap.

What happened when we ran it

Our sandbox checkout at commit c3f8889 was 108 MB, with 2,857 files and roughly 221,562 lines of source. npm install completed in 7 seconds inside ./smartyoutubetv/, added 0 packages, and left 19 MB on disk. npm audit reported 0 known vulnerabilities: 0 critical, 0 high, 0 moderate, and 0 low.

There was no npm build script or target, so the build step was skipped. The same was true for tests. Our scan found no tests directory, no Dockerfile, and 0 CI workflow files. These results describe the Node-shaped automation path that the lab detected. They do not show that an APK compiled, launched, signed in, played video, or updated itself. No such outcome should be inferred from a successful empty dependency install.

A 7-second npm install does not build the Android application

The smartyoutubetv/package.json file names version 1.0.0 and declares no dependencies. That explains why 0 packages were installed so quickly, but the real application is an Android Gradle project. Its module declares Android build types and several product flavors, while the repository also references shared code through Git submodules. Anyone examining source needs the Android toolchain and the linked modules, not a Node runtime.

The README offers no source-build walkthrough. Its intended route is a published APK: either an on-device Fire TV process advertised at under 5 minutes or a standard ADB sideload using adb install -r. That may be enough for an end user installing a historical binary. It is thin documentation for a developer who must reproduce the stable artifact, choose a flavor, inspect signing, or verify the app against a modern Android SDK.

Login convenience now depends on frozen application code

SmartTubeLegacy does not depend on Google Services and provides its own internal login mechanism. That was useful on TV boxes without a full Google software stack. It also means account behavior is tied to an independent client that can no longer respond through this repository. Treat login as sensitive: obtain the APK from the project's release page, check the artifact you install, and avoid entering an account you cannot afford to expose.

Playback has the same external dependency. Open issue 845 says videos stopped working despite reinstalling, updating, and resetting the application. Another issue reports that version 11.64 would not load 4K video. Both reports are from 2021 and do not prove the 2023 stable APK has those exact faults. They do illustrate why a frozen client for a changing service is a poor new bet, even if its interface remains comfortable on one television.

The 447-item queue stopped moving before the archive

GitHub showed 4,559 stars and 447 open issues and pull requests when fetched. The most recently updated open issues returned by the API were from 2021, including playback, resolution, casting, and profile requests. That issue inactivity, combined with the 2023 archive and last push, describes a closed maintenance chapter rather than a merely slow release schedule. The combined open count includes pull requests, so it should not be read as 447 confirmed bugs.

The project still has historical value. Its screenshots, release APK, license, and source preserve a client designed around televisions rather than touch screens. Existing users may also have hardware where the last stable build remains satisfactory. That is a preservation case. A new installation needs current service compatibility, current Android behavior, and somewhere to report a regression, none of which this archived issue tracker can promise.

SmartTube is the maintained successor for Android TV

The current yuliskov/SmartTube repository describes an Android TV media browser and was pushed on September 13, 2026. It is the closest replacement because it keeps the same maintainer and TV-first purpose without the archive status. NewPipe is a better comparison for general Android phones and tablets, while FreeTube targets desktop users. Device type should decide among them before feature lists do.

SmartTubeLegacy should stay on a device only when it already works and the owner understands the maintenance cutoff. Our 7-second npm install offers no reassurance about the APK, because no Android build or playback test followed it. For source study, the project remains readable under MPL-2.0. For watching YouTube on a TV today, start with the active successor and keep this repository as a record of the older architecture.

Alternatives

ProjectWhat it isPick it when
SmartTube gh↗The active Android TV media client from the same maintainer.pick this instead for any new TV installation or when ongoing fixes matter.
NewPipeA lightweight libre streaming front end for Android devices.pick this instead when a phone or tablet experience matters more than a ten-foot TV interface.
FreeTube gh↗A privacy-focused open-source YouTube client for desktop systems.pick this instead when the target is Windows, macOS, or Linux rather than Android TV.

What people are saying

  1. [github-trending] yuliskov/SmartTubeLegacy

Sources

  1. SmartTubeLegacy repository
  2. SmartTubeLegacy README and install guide
  3. SmartTubeLegacy stable release
  4. Issue 845: playback failure report
  5. Issue 847: 1080 mode limited to 720p report
  6. Active SmartTube successor repository

More self-hosted reviews

Mailspring · kvm · nango · danmu_api · tvbox · opendisplay · the whole board →