My TV couldn't be debloated, so I filtered it with AdGuard Home DNS

I wanted to strip the ads and tracking off my Hisense TV, but it runs VIDAA and has no ADB. How I fixed it with AdGuard Home on a Raspberry Pi and one custom rule.

IvánPublished on 6 minLeer en español

A few days ago I came across CleanYourTV, an open source project that debloats Android TV and Google TV sets over ADB: it disables telemetry and preinstalled apps and swaps the ad-stuffed home screen for a clean launcher. I cloned it, keen to get rid of the ads on the living room TV, which is a Hisense… and five minutes later I found out it was no use to me at all. Here’s why, and how I ended up solving it from the network side with the AdGuard Home I already had on my Raspberry Pi.

Spoiler: the DNS filter had been running for a week, and the TV hadn’t gone through it even once.

1. First, check what OS your TV runs

Before cloning anything, confirm this, because it decides everything else. Many Hisense TVs sold in Europe don’t run Android but VIDAA, the brand’s own OS. You can tell from the home screen: if there’s a row of apps with the VIDAA logo and no Google Play anywhere, it’s VIDAA.

  • Android TV / Google TV: has ADB. Tools like CleanYourTV can disable packages (pm disable-user) and replace the launcher, and it all rolls back with one line.
  • VIDAA (and also LG’s webOS or Samsung’s Tizen): no ADB. You can’t disable apps or change the home screen.

Mine was VIDAA, so all I could touch were its menus and what goes out over the network. For the latter I already had the right tool.

2. What you can do with the remote

Before touching the network, turn off whatever the TV itself lets you turn off. On VIDAA the names change between versions (U5, U6, U9…), but it goes roughly like this:

Where What to turn off
Settings → Advanced settings → Enhanced viewing Automatic content recognition (ACR), which analyses what you watch, even over HDMI
Same menu Personalised ads and content recommendations
Settings → System → Advanced settings → Personalised ads Off, and Reset advertising ID
Settings → Support → Legal and privacy Review what you agreed to when setting up the TV

This cuts down tracking, but the home screen banners are still there. For those you have to cut them off at DNS.

3. AdGuard Home on the Pi (what I already had)

AdGuard Home is a DNS server that answers 0.0.0.0 when asked about an ad or tracking domain. I run it as one more service in the Pi’s Docker Compose file:

  adguard:
    image: adguard/adguardhome:latest
    container_name: adguard
    restart: unless-stopped
    network_mode: host          # needs port 53 on the Pi
    volumes:
      - ./adguard/work:/opt/adguardhome/work
      - ./adguard/conf:/opt/adguardhome/conf
    command: ["--no-check-update", "-c", "/opt/adguardhome/conf/AdGuardHome.yaml",
              "-w", "/opt/adguardhome/work", "--web-addr", "0.0.0.0:3003"]

I moved the web UI to port 3003 because 3000 is already taken by Gitea. Upstreams are Quad9 and Cloudflare over DoH, with two lists: AdGuard DNS filter and HaGeZi Multi NORMAL.

To have the whole house use it, I set the Pi as the preferred DNS on the router and 9.9.9.9 as the alternate. That way, if the Pi goes down, nobody loses internet. Devices still ask the router, and the router asks the Pi. In the first hour it handled about 5,800 queries and blocked around 10%.

4. The problem: the TV wasn’t there

With AdGuard running for a week, I searched the query log for anything that smelled of Hisense: vidaa, hisense, hismart… Zero hits. Meanwhile the other TV in the house, an LG, showed up everywhere.

A VIDAA TV that’s switched on talks to its servers constantly, so it had to be somewhere. First I checked it was on the network. VIDAA leaves port 36669 open for phone remote control, which made it easy to find:

nmap -p 36669 --open 192.168.1.0/24

It answered at 192.168.1.70. It was connected, yet not a single query of its went through AdGuard. The explanation: the TV had a hard-coded DNS server in its network settings, skipped the router’s and went straight out to the internet. A DNS filter only sees what it’s asked.

5. Pointing the TV straight at AdGuard

On the TV: Settings → Network → Network configuration, manual setup:

  • IP: 192.168.1.70, netmask 255.255.255.0, gateway the router’s.
  • DNS: 192.168.1.50 (the Pi, i.e. AdGuard directly).
  • Secondary DNS: 9.9.9.9.

I pointed it at the Pi rather than the router on purpose. Since everything at home goes through the router, almost every query in AdGuard shows up with the router’s IP and you can’t tell devices apart. If the TV asks the Pi directly, it shows up with its own IP, and I can see what it requests and what gets blocked.

Since I set the IP by hand, I also reserved it on the router so it never hands it to another device. I covered that in how to pin an IP with a DHCP reservation.

6. Watching the TV’s requests live

AdGuard writes its query log to disk in batches, so it lags behind. To see it in real time, I sniffed the DNS traffic reaching the Pi from the TV while I browsed the home screen and opened a couple of apps:

sudo tcpdump -i any -n -l 'src host 192.168.1.70 and port 53'

Within a minute I had the picture. With the standard lists, AdGuard was already cutting off the main stuff:

Domain What it looks like Status
ter-jrnl-eu.vidaahub.com Usage logging (telemetry) Blocked by the lists
exc-jrnl-eu.vidaahub.com Error and event logging Blocked by the lists
rpt-mntz-azure.vidaahub.com “Monetisation” reports Blocked by the lists
customerevents.netflix.com Netflix stats Blocked (Netflix still works)
crtv-mntz.vidaahub.com Ad downloads (“creatives”) Getting through
partner.vidaahub.com Partner app configuration Allowed, and should be

The one that mattered was slipping through: crtv-mntz looks very much like what serves the home screen banners.

7. One custom rule

I added the rule under Filters → Custom filtering rules. I did it in the config file, under user_rules, after taking a backup and with AdGuard stopped:

# 2026-11-04 VIDAA ads (Hisense)
||crtv-mntz.vidaahub.com^

Then I checked by asking the Pi directly:

dig +short crtv-mntz.vidaahub.com @192.168.1.50   # 0.0.0.0
dig +short partner.vidaahub.com @192.168.1.50     # normal IP

The TV can take a few hours to stop showing banners it already has cached.

What not to do

  • Block all of *.vidaahub.com. It’s the quickest option and the surest way to break the apps. Block subdomain by subdomain.
  • Assume a device goes through your filter. TVs, Chromecasts and some phones bring their own DNS. Look for their IP in the log before you believe they’re covered.
  • Set only the Pi as DNS with no fallback. The day you reboot it, the TV (or the whole house) loses internet.
  • Block things without noting what and when. Put a dated comment above every rule: the day an app breaks, you’ll know what to remove.

One honest caveat: with 9.9.9.9 as secondary DNS, the TV can use it whenever it likes and bypass the filter. That’s the price of not losing the TV if the Pi goes down, and for now I’m fine with it.

Summary

  1. Before reaching for debloat tools, check whether your TV runs Android. If it’s VIDAA, webOS or Tizen, there’s no ADB.
  2. Use the remote to turn off ACR and personalised ads.
  3. Make sure the TV actually shows up in your DNS filter’s log. If it doesn’t, it has a hard-coded DNS server.
  4. Point it straight at AdGuard so it shows up with its own IP, and watch what it requests with tcpdump.
  5. Block only the ad and telemetry subdomains, and let the app ones through.

I went after a project with 51,000 GitHub stars and ended up solving it with one line in a filter I already had running. Often the right tool is the one already running at home.

Mini quiz

Did it stick?

Three quick questions. Each right answer is worth 10 XP.

  1. Why is an ADB-based debloat tool useless on a Hisense TV running VIDAA?
  2. AdGuard had been running for a week and the TV never showed up in its log. What was going on?
  3. Why do I let partner.vidaahub.com through instead of blocking everything under vidaahub?
  • #adguard
  • #dns
  • #raspberry-pi
  • #privacy
  • #smart-tv
Esc