Yes. Quiblo is free software under the GPLv3, with no paid tier, no advertising and nothing paywalled. Every feature is in the build everybody gets.

Does Quiblo come with channels?

No. Quiblo ships with no channels, no films and no way to find any, and this project will not help you find a provider. It is a player, in the same category as VLC: you supply an M3U playlist or an Xtream Codes account that you already have.

What playlists does Quiblo support?

M3U and M3U8 playlists, either from a URL or a file on the device, and Xtream Codes accounts. It plays HLS, DASH, raw MPEG-TS and progressive MP4 or MKV.

Does Quiblo work on Android TV?

Yes. There is a separate television build with its own interface driven entirely by a remote, alongside the phone and tablet build. Both are in every release.

Does Quiblo track me?

No. There is no account, no telemetry and no server of ours anywhere in the path. Quiblo makes no network request to any host you did not configure yourself.

Where do I download Quiblo?

From the releases page on GitHub. Each release carries two APKs — one for phones and tablets, one for Android TV and Google TV — and they are signed with the same key.

Using Quiblo

Downloads

Which APK to take, how to check it is the one we published, and what a pre-release means.

# Where releases live

Every release is published on GitHub Releases. There is no store listing. New versions are something you come and get — with one exception, added in the current alpha: the television app's Settings has a Check now button that reads this page and can fetch the newer APK for you. It runs when you press it and at no other time, and it verifies the published checksum before offering to install anything. The phone app still never checks. See Release notes.

Each release carries four files: two APKs, and a .sha256 beside each.

# Which APK is yours

File	Install it on
`quiblo-<version>.apk`	A phone or a tablet
`quiblo-tv-<version>.apk`	Android TV or Google TV

They are separate applications with different ids, so both can sit on one device without interfering. They share every layer beneath the screens; what differs is the interface, and a television interface driven by a remote is a different piece of work rather than the same one stretched.

The phone APK will install on a television and then never appear in its launcher. That is the most common confusion we hear about, and it is by design rather than a packaging fault: the phone build declares no leanback launcher entry, because a touch-first interface reached with a D-pad is worse than no entry at all. Install the -tv one there.

The minimum Android version is 11 (API 30) for both.

# Checking what you downloaded

Each APK is published with its SHA-256 checksum beside it, so you can confirm the file you have is the file we built. Download both, put them in the same directory, and run:

sha256sum -c quiblo-<version>.apk.sha256

On Windows, certutil -hashfile quiblo-<version>.apk SHA256 prints the hash to compare by eye.

This is worth doing because an IPTV player is exactly the kind of app that gets repackaged with something added. A checksum that matches means the file came from our build, whatever site you found it on — and a checksum that does not match means throw it away, no matter how plausible the source looks.

Every published APK is signed with the project's release key. Android will refuse to install a build signed with a different key over one of ours, which is a second, automatic version of the same check.

# Stable releases and pre-releases

Some releases are marked Pre-release on that page. The difference is a claim about testing, not about the build process — both are built and signed identically by the same automation.

A beta is feature-complete for its version and has been swept on real devices. It is the one to take if you want to help us find things.
An alpha exists to prove the release machinery works. It is not for watching television with.
A stable release is one with no pre-release marker, and it is what GitHub offers as "Latest".

Version numbers follow semantic versioning: the middle number moves when something is added, the last when something is fixed.

# Upgrading, and the one case that needs an uninstall

Installing a newer APK over an older one keeps everything — sources, favourites, history and profiles all survive, and the database migrates itself.

The exception is a build somebody handed you before the project published signed releases. Those were signed with the Android debug key, and Android will not upgrade over one with a properly-signed build: the install simply fails, usually with a message about conflicting signatures that does not explain itself. Uninstall the old build first.

On a television, "uninstall" can also mean uninstalling for another user account on the device — a build installed under a second profile blocks the install without appearing in the launcher you are looking at. If a television refuses a release for no visible reason, that is the first thing to check.