TizenTube Cobalt: What It Is and How to Install It Outside Tizen
Experience TizenTube on other devices that are not Tizen.
At a glance
- What is it?
- TizenTube Cobalt is a Cobalt-based build of TizenTube for devices that are not Tizen TVs. It removes ads, adds SponsorBlock and DeArrow support, and ships as a sideloadable release rather than a store app.
- Who is it for?
- Adopt TizenTube Cobalt if you have a Google TV certified device, or a Fire TV, Android TV, or desktop platform that can sideload an APK, and you want ad removal plus SponsorBlock and DeArrow in one container. Skip it if you are on a stock Samsung Tizen TV, where TizenTube itself is the intended target, or if you need a documented rollback path, because the README does not provide one.
- Can I use it commercially?
- Yes. BSD-3-Clause is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 125 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on September 30, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The problem TizenTube Cobalt solves, and who it is for
TizenTube targets Samsung Tizen TVs. TizenTube Cobalt exists for everyone else. The repository description states the purpose directly: experience TizenTube on other devices that are not Tizen. That is a narrow but real audience. If you own a Samsung TV, the upstream TizenTube project is the thing you want. If you own a Google TV stick, an Android TV box, a Fire TV device, or a desktop machine, the Tizen-specific build does not apply to you, and Cobalt is the port that does.
The app is built on Cobalt, which the README describes as a lightweight, cross-platform application container and runtime for HTML5-based apps, originally developed by Google for embedded and resource-constrained devices such as smart TVs, set-top boxes, and game consoles. That matters for the target hardware. Cobalt implements a subset of the W3C HTML5 standard rather than a full browser engine, so it is meant to run web apps at high performance on low-power chips. A streaming front end is exactly that kind of workload.
The feature set is short and specific: an ad blocker, SponsorBlock support, video speed control, and DeArrow support. The README also says more features are planned and points feature requests at the TizenTube issue tracker rather than this repository. If you want a general-purpose media player with a plugin ecosystem, this is not it. It is a viewing-experience patch bolted onto a container.
How Cobalt, SponsorBlock, DeArrow and the ad blocker fit together
The architecture is a container plus a modified web app. Cobalt is the runtime that renders the streaming site; TizenTube Cobalt is the build that changes what that site does when it loads. The README does not publish an internal module map, so the layering has to be read from the feature list rather than from source. What can be said is that the ad blocker operates on the streaming site itself, while SponsorBlock and DeArrow are third-party services the app integrates with.
SponsorBlock is a crowd-sourced segment database hosted at sponsor.ajay.app. The README says TizenTube Cobalt automatically skips sponsored segments in videos. That means segment data has to come from somewhere, and the README names SponsorBlock as the source. DeArrow, at dearrow.ajay.app, is the companion service for titles and thumbnails; the README describes its role here as removing clickbait and misleading video titles. Both are external dependencies that the app reaches over the network, which is worth knowing if your device sits behind a restrictive DNS setup.
Video speed control is purely local. It changes playback rate, nothing else. The ad blocker is the feature with the most visible effect on the browsing experience, and the README frames it as removing interruptions from ads rather than as a network-level filter. That distinction matters: this is not a Pi-hole style blocker, it is an in-app intervention on the streaming site.
Installing TizenTube Cobalt and a first real use
There is no package manager step and no build-from-source instruction in the README. Distribution is through GitHub releases, and the README links to the latest release page. The install procedure it gives has three steps: download the latest release, sideload or install the app on your device using a file manager, ADB, or a platform-specific method, then open the app.
Start by downloading the release asset for your platform from the latest release page. The README does not enumerate asset names, so check the release listing itself rather than guessing a filename. The README does not give an ADB command line, so follow your platform's own sideloading method; the documented route is a file manager, ADB, or a platform-specific method.
For Fire TV, the README lists an AFTVNews code, 6366500, which is the identifier used by that site's Downloader-based install flow. The related search term TizenTube Cobalt Downloader lines up with that path: you enter the code in the Downloader app rather than pushing the file over ADB. The README does not walk through the Downloader steps, so treat the code as the entry point and follow the Downloader app's own prompts.
Once the app opens, the first real use is simply playing a video on the streaming site. If the ad blocker is active you should not see pre-roll or mid-roll ads; if SponsorBlock is active, sponsored segments are skipped automatically. The README does not document a settings screen, per-feature toggles, or where SponsorBlock categories are configured, so do not expect a documented configuration surface. The project keeps its community channels on Discord, Telegram, and Matrix, and routes bug reports and feature requests to the TizenTube issue tracker.
The repository root also carries a docker-compose.yaml that builds Linux, Raspberry Pi, RDK, unittest, and webtest images from cobalt/docker/ subdirectories. That is the Cobalt build and test infrastructure, not an end-user install method, and the README does not present it as one.
Where TizenTube Cobalt is the wrong tool
The clearest limitation is the one in the name. If your television is a Samsung Tizen set, this port is not aimed at you; the repository description scopes it to devices that are not Tizen. Installing it on Tizen hardware is not a documented path, and the README offers no such instructions.
The second limitation is the install model. Sideloading means no automatic updates from an app store. The README does not describe a self-update mechanism, so keeping current is a manual job: check the releases page, download, reinstall. For a device you set up once and forget, that is friction. The release history shows three releases in nine days in May 2026 (v2.0.0 on 2026-05-09, v2.0.1 on 2026-05-10, v2.0.2 on 2026-05-17), which is a burst of activity rather than a steady cadence, and the last push to the repository was on 2026-05-28. Anyone expecting a rolling stream of fixes should look at that date.
The third is dependency on services outside the project's control. SponsorBlock and DeArrow are third-party endpoints. If either is unreachable, the corresponding feature degrades, and the README does not describe offline behaviour or a fallback. There is also no documented rollback procedure: the README does not explain how to revert to a previous release or uninstall cleanly, and it does not list known incompatible devices beyond recommending Google TV certification. If you need a supported, warranty-safe install on a living-room TV, this is a sideload, and you should treat it as such.
TizenTube Cobalt vs SmartTube: two different containers
The comparison people search for is TizenTube Cobalt vs SmartTube, and the difference is architectural rather than cosmetic. SmartTube is a native Android TV application. TizenTube Cobalt is a Cobalt-based HTML5 container running a modified streaming web app. Those are two ways of reaching a similar goal: a television viewing experience without ads and with sponsor skipping.
A native app talks to the platform's own media and UI APIs. It is built for Android TV as a first-class target, which is why it fits that platform's launcher, remote handling, and update expectations. A Cobalt container instead renders a web app inside a runtime that implements a subset of HTML5. The advantage of the container approach is reach: the same web app can run on hardware where a full browser would be too heavy, and the porting work is in the container and the web app rather than in a platform-specific rewrite. The cost is that you inherit the container's constraints. Cobalt implements a subset of the standard, not all of it, so any behaviour that depends on browser features outside that subset is not available.
The practical consequence for a buyer is update mechanics and platform fit. A native Android TV app follows that platform's distribution norms. TizenTube Cobalt follows GitHub releases and sideloading, and the README points you at Google TV certified hardware for the best experience. Neither approach is strictly better; they are different bets about where the code should live. If you want the app to feel native to Android TV, that is the native route. If you want the TizenTube feature set on a device that is not a Tizen TV, the Cobalt port is the one that carries it.
Licence, upgrade cost, and what the repository does not tell you
The project is licensed under BSD-3-Clause. That is a permissive licence, and it permits redistribution and modification with the usual conditions attached, including retention of the copyright notice and disclaimer. This is not legal advice; read the LICENSE file in the repository, along with LICENSE.chromium_os, before you redistribute anything. The presence of a Chromium OS licence file is a reminder that this is a Cobalt-derived tree with upstream obligations, not a from-scratch codebase. A quick look at the top-level entries confirms that: base/, build/, cc/, chrome/, components/, content/, crypto/, and dbus/ are Chromium tree directories, and cobalt/ is where the Cobalt-specific code lives.
Upgrade cost is the practical question, and the honest answer is that the README does not describe an upgrade path at all. There is no documented migration between major versions, no changelog guidance in the README, and no stated compatibility matrix for devices. With v2.0.0, v2.0.1, and v2.0.2 all landing in May 2026, and the last push on 2026-05-28, the release history is short and recent. Plan on treating each release as a fresh sideload until the project documents otherwise.
The docker-compose.yaml at the repository root builds Linux, Raspberry Pi, RDK, unittest, and webtest images from cobalt/docker/ subdirectories. If you were hoping for a containerised deployment of TizenTube Cobalt itself, that is not what this file offers. The documented end-user route remains the release page.
Editorial conclusion
Adopt TizenTube Cobalt if you have a Google TV certified device, or a Fire TV, Android TV, or desktop platform that can sideload an APK, and you want ad removal plus SponsorBlock and DeArrow in one container. Skip it if you are on a stock Samsung Tizen TV, where TizenTube itself is the intended target, or if you need a documented rollback path, because the README does not provide one. Before installing, check the assets on the latest release page for your platform, and confirm your device is listed as Google TV certified, since the README recommends that for a better experience.
Frequently asked questions
What is TizenTube Cobalt?
It is an app based on Cobalt that brings the TizenTube viewing experience to devices that are not Tizen, removing ads and adding SponsorBlock, DeArrow, and video speed control. The README describes it as a Cobalt-based app that enhances streaming site playback.
How do I install TizenTube Cobalt?
Download the latest release from the GitHub releases page, then sideload or install the app using a file manager, ADB, or a platform-specific method, and open it. The README recommends a Google TV certified device for a better experience.
Can I install TizenTube Cobalt on my FireStick?
The README lists an AFTVNews code, 6366500, which is the identifier used with that site's Downloader-based install flow for Fire TV devices. It does not walk through the Downloader steps themselves.
How does TizenTube Cobalt compare with SmartTube?
SmartTube is a native Android TV app, while TizenTube Cobalt is a Cobalt-based container running an HTML5 streaming web app. The README does not compare the two, so the difference comes down to the container approach versus a platform-native application.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/reisxd-tizentubecobalt)