Skip to the content.

Illustration: a smart TV with a tidy home screen and a broom-and-sparkles motif

VIDAA Clean TV

English Español

test

Documented privacy settings and DNS filtering guidance for smart TVs running VIDAA, plus offline tools to inspect DNS logs. The aim is to reduce ads and telemetry without rooting or changing firmware. One owner-reported DNS-filtering session is logged (Hisense 65A67H); no model has a completed settings session yet. Menu availability and results depend on the model, region and firmware; see TESTING.md.

Why a separate project

Clean Your TV and similar tools disable Android packages over ADB. That route is not documented for the non-Android VIDAA sets covered here: Clean Your TV’s Hisense compatibility page lists sets running VIDAA OS as not covered because the tool needs Android, and the justatv.eu VIDAA guide reaches the same conclusion - with no ADB on VIDAA, cleanup means settings and network filtering, not package tools. This project takes the settings-and-DNS route instead. This scope is not a claim that every TV sold with VIDAA branding has the same internals; see the compatibility guide.

How it works

This project works through the TV’s own settings and the network it talks to. It does not use a debug bridge or modify the TV’s software.

Step What happens
Settings Use the remote to find documented content-recognition, usage-data and advertising-personalization settings. Availability and effects need verification on your TV; note original values so you can revert.
Filter A DNS filter on your network stops ad and telemetry domains from resolving. The TV itself is never modified.
Observe The filter’s query log shows what your TV actually talks to, so new block rules come from evidence, not guesses.

No root, no firmware changes, nothing installed on the TV, and everything can be undone.

Quick start

You have Do this
Just the remote docs/01-on-device-settings.md - about five minutes; local settings you can change back.
An always-on computer or Raspberry Pi Add docs/02-dns-filtering.md and docs/03-observing-dns.md.
A VIDAA TV you are cleaning for the first time Follow docs/05-first-hardware-session.md and log what you see.

New here? docs/00-start-here.md walks from identifying your exact TV to one concrete reversible action.

Try the offline synthetic example without a TV, router, credentials or network access.

What you get

Part What it looks like
Content recognition off Turns off the documented content-recognition setting. Its exact scope and effect depend on firmware and remain unverified on the target TV.
Advertising personalization setting Ads can still appear. The documented personalization toggle can be disabled; its effect has not been verified on the target TV.
A cleaner home screen (DNS route) The upstream blocklist author reports recommendation rows, promo tiles and VIDAA Free promos gone, with YouTube and Netflix intact.
A test log, not promises TESTING.md records exactly what was verified, on which model and when. Nothing else is claimed.

Supported TVs

Intended for TVs running VIDAA, including sets marketed with HomeOS branding. Check your actual operating system, region and firmware rather than relying on the brand alone. The table describes documentation coverage, not a compatibility certification.

Platform Documentation and verification status
Hisense VIDAA All three routes are documented. The upstream author reports DNS results on Hisense sets in Europe; one owner-reported DNS session on a 65A67H is logged in TESTING.md. Settings paths are not yet verified on a Hisense model.
Toshiba VIDAA Settings and DNS routes are documented; menu paths and results still await the first logged Toshiba 50UV1553DB session.
Android TV / Google TV sets, including Hisense models that actually run Android You want Clean Your TV instead - this project does not apply to Android.
Samsung (Tizen), LG (webOS) Different systems entirely; nothing here applies.

Per-model pages live under docs/tv/: Toshiba 50UV1553DB and Hisense VIDAA.

Documentation

Start with FAQ.md if you are deciding whether any of this is for you.

Doc What it covers
docs/00-start-here.md From “I have a VIDAA TV” to a first real, reversible action
docs/01-on-device-settings.md Route 1: the reversible settings pass
docs/02-dns-filtering.md Route 2: DNS filtering setup, options and honest warnings
docs/03-observing-dns.md Route 3: observing DNS and building your own rules
docs/04-local-control-mqtt.md Note on the local MQTT control interface
docs/07-compatibility.md Choose a route by OS and feature, without borrowing another model’s test result
docs/05-first-hardware-session.md Protocol for the first real cleanup session
docs/08-app-compatibility.md Per-app compatibility matrix: reported status, setup and limits, never a guarantee
TROUBLESHOOTING.md When something breaks or does not match the docs
SECURITY.md What to check before trusting a report or sharing logs
NOTICE.md / RELEASE.md Credits, versioning and release notes

What this project does NOT do

Existing work this builds on

Development

python3 scripts/test_classify_dns_log.py -v runs the offline test suite (stdlib only). CI runs it, plus a syntax and duplicate validation of the supplement blocklist and a check that internal documentation links resolve, on every push and pull request across Python 3.10-3.14.

Contributing

Reports from other VIDAA models are the most useful contribution right now - see CONTRIBUTING.md for the verification rule and what a first-session report needs. Changes are recorded in CHANGELOG.md.

Hardware verification status

Nothing here is claimed as tested on a specific model until it appears in TESTING.md with a date and a firmware version. The current target device is a Toshiba 50UV1553DB (VIDAA, Europe). Per-model pages live in docs/tv/. Until that first session is logged, treat every menu name as “wording varies - read the privacy section”.

License

MIT for original content (see LICENSE). Third-party projects keep their own licenses (see NOTICE.md).