返回资讯中心
外部精选
软件工程
#开发者实时流

Debloat Any Android or Google TV over Wi-Fi

Strip the bloatware from any Android TV or Google TV over Wi-Fi, and replace the ad-filled home

Hacker News 最新andreicap2026/10/20 · 26 天前28 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

cleanyour.tv · The prompt · 92 TV lists · 18 built on it · The tweet

Strip the bloatware from any Android TV or Google TV over Wi-Fi, and replace the ad-filled home screen with a clean launcher that looks like an Apple TV. No root, no cable, nothing uninstalled, and a one-line restore if you change your mind.

Vibe coded my parents' TV this afternoon! It was showing a sponsored ad before you could even get to Netflix. Gave Claude Code the model number, it found the TV on wifi, removed 25 Xiaomi packages and wrote a new launcher. Looks like an Apple TV now lol.

@gathint, 17 October 2026. The replies are where most of the TV lists here came from. The repo was called tv-vibehack until the 19th; old links work.

Android TVs have the same debug bridge as Android phones. Switch on USB debugging in the TV's developer options, allow your computer once, and the rest is standard Android tooling:

The bloat differs by brand, so the prompt has your coding assistant discover it on your TV and ask before touching anything you might use.

You need a computer on the same Wi-Fi as the TV and a coding assistant with shell access. Suggested: Claude Code on 0G Private Computer, one API key for 100+ models. Claude Code with an Anthropic plan, Codex or Gemini CLI work too.

The assistant backs up, debloats, builds and installs the launcher, and checks each step with screenshots pulled from the TV. With this repo as context it takes about fifteen minutes.

A pitch-black home with a dock of your four favourite apps in a rounded band, where Apple TV puts it.

A top shelf naming the focused app in large type, with an ambient glow in a colour taken from its artwork.

The rest of your apps in a grid that slides up when you press Down.

One floating glass highlight that springs from tile to tile. The focused tile lifts and shows its name.

Three frosted buttons: Inputs (HDMI ports under the names you gave them in the TV's settings, AV, Live TV), Wi-Fi or Ethernet with the network name, Settings.

A greeting, a thin clock and the date in Outfit, and a matching Clock screensaver. Set show_stats in config or a theme for one line under the clock: CPU, free memory and free storage. It stays off unless you turn it on, and it refreshes only while Home is on screen.

Themes that change colours, wallpaper, dock and columns without a rebuild, and module cards that let other apps plug a tile in, only with your say-so.

And a TV that stops working against you: no sponsored rows, no "Discover" nags, no analytics phoning home, no apps you never asked for.

Anything running Android TV or Google TV. Samsung (Tizen) and LG (webOS) run different systems; see SHOWCASE.md for a webOS port. Fire TV takes the debloat half only, since Fire OS will not hand Home to a third-party launcher. A few China-market TCL sets refuse to install any launcher at all; their lists say so in the header.

Tested lists from contributors, one folder per model in examples/:

TCL 18 · Sony 16 · Xiaomi 15 · Philips 6 · Hisense 5 · BenQ 2 · CHiQ 2 · Haier 2 · Hitachi 2 · Panasonic 2 · Skyworth 2 · AiPro2K · Amazon Fire TV Stick · Chromecast with Google TV · Insignia Fire TV · Kalley · NVIDIA Shield · OnePlus · onn · PRISM+ · RCA · Redmi · SANYO · Thomson · Toshiba Fire TV · Vu · JMGO, Portronics, Stellamore, Wanbo and XGIMI projectors

Your TV not here? The prompt discovers the bloat itself. Add your list afterwards and the next person with your model skips that step: CONTRIBUTING.md.

Everything the assistant does, you can run yourself. The tools need Python 3 and nothing else.

python3 -m venv tools/venv && tools/venv/bin/pip install -r tools/requirements.txt export TV_HOST=192.168.1.50 # your TV's IP address

tools/venv/bin/python -I tools/tv.py --probe # model, Android version, firmware tools/venv/bin/python -I tools/tv.py 'pm list packages' # one shell command on the TV tools/disable.sh examples/xiaomi-mi-tv-4a/debloat.txt # apply a debloat list tools/restore.sh examples/xiaomi-mi-tv-4a/debloat.txt # undo it, stock launcher back TV_HOST=192.168.1.50 launcher/build-and-install.sh # build the launcher and make it Home tools/theme.sh themes/aurora # push a theme; --reset removes it

Tool What it does

tools/tv.py Pure-Python ADB client: shell, batch, push, pull. Works where the stock adb binary is blocked.

tools/b64push.py Uploads large files such as APKs in base64 chunks and verifies the checksum.

tools/disable.sh, restore.sh Apply or undo a debloat list, the undo from the state recorded before the change.

tools/recovery.py Writes the record disable.sh needs to undo itself, and prints the restore batch.

tools/theme.sh Push a folder from themes/ to the launcher and restart Home.

launcher/build-and-install.sh Builds a shrunk release (about 370 KB), installs it, switches Home, and rolls back if Home does not land on it.

Debloat list paths passed to disable.sh and restore.sh are relative to the directory you run from, so your own lists can live outside the repository. Absolute paths also work.

Every script has a PowerShell twin next to it. On Windows with Android Studio installed nothing else is needed:

python -m venv tools\venv; tools\venv\Scripts\python.exe -m pip install -r tools\requirements.txt powershell -ExecutionPolicy Bypass -File launcher\build-and-install.ps1 -TvHost 192.168.1.50 powershell -ExecutionPolicy Bypass -File tools\disable.ps1 -TvHost 192.168.1.50 examples\xiaomi-mi-tv-4a\debloat.txt

The install scripts ask the TV which launcher owns Home and only disable one they recognise (tvlauncher or launcherx); pass STOCK_LAUNCHER=<package> (-StockLauncher) to override, or none to leave it alone.

A small native Android TV app (com.gathin.tvhome, about 370 KB installed) in plain Java with AndroidX RecyclerView and nothing heavier. Built for sets with 1 GB of RAM: no blur, no video, no network, no background services. It needs JDK 17 and Android SDK platform 34 to build; on macOS, brew install openjdk@17 android-commandlinetools and sdkmanager "platforms;android-34" "build-tools;34.0.0". On Linux the install script finds ~/Android/Sdk and the java on your PATH.

Before tools/disable.sh changes anything it writes down what the TV looked like: for every package in the list whether it was enabled, already disabled or not installed, which component owned Home, and the three animation scales. That record lives in ~/.cleanyourtv/, one file per TV and list, and a second run of the same list keeps the first record instead of saving the cleaned-up state over it. If you added packages to the list since, that run adds them to the record before disabling them.

Keep the list you applied. The restore script replays the record, so a package you had disabled yourself stays disabled and Home goes back to the component that owned it:

TV_HOST=192.168.1.50 tools/restore.sh examples/<your tv>/debloat.txt # Android TV TV_HOST=192.168.1.50 tools/restore.sh examples/<your tv>/debloat.txt com.google.android.apps.tv.launcherx # Google TV

The stock launcher argument is only a fallback: with a record, the launcher that actually owned Home is the one that gets it back, and the argument is used only when nothing answered HOME at the time or this project's launcher owned it. The stock launcher is enabled again either way, unless it was already disabled when the record was taken. Without a record (an older run, or a record you deleted) the script says so and falls back to enabling the whole list and resetting the scales to 1.0, which is what it used to do.

It leaves the new launcher installed (remove it from the TV's Settings → Apps if you want it gone) and does not know about packages you disabled outside the list. To switch back later, run the install script again; it works out which launcher to disable even when Home has fallen back to Android's chooser. If the TV is unreachable, its own Settings → Apps page can re-enable packages too.

The full list of things that bit us is in docs/TROUBLESHOOTING.md. The three that matter most:

Is this safe? Can it brick the TV? Nothing is flashed, rooted or deleted; packages are disabled in the user profile. The risk is disabling something the TV leans on, which is why lists are applied in small batches with a restore script ready. The TV's own Settings → Apps page can re-enable packages even without the tools.

What about firmware updates? Most lists disable the update service, so updates arrive only when you re-enable it. If one lands, the worst case is a package coming back and you re-run the script.

Won't the apps break? Streaming apps still update through the Play Store, which is left alone. The launcher just lists what is installed and launches it with intents that have been stable for a decade.

Can I do this for someone in another home? Yes, over a private Tailscale link instead of the same Wi-Fi: either Tailscale on their TV, shared with you, or a computer or Apple TV at their home routing to it. Never by opening the ADB port on their router. Step by step in docs/REMOTE.md.

Isn't ADB access a security hole? It is one explicit "allow this computer" tap on the TV, the same as developing an Android app. Network ADB is plaintext on port 5555, and on firmware with ro.adb.secure=0 any device on the LAN gets a shell, so close it when you are done:

The launcher keeps working without debugging.

Can it block ads inside apps too? Partly, with Android's Private DNS (Android 9 and newer). Point it at an ad-blocking resolver such as AdGuard DNS and every app's ad and tracker domains stop resolving, system-wide, surviving reboots. The trade-off: that resolver then sees every DNS query the TV makes.

tools/tv.py 'settings put global private_dns_specifier dns.adguard-dns.com' tools/tv.py 'settings put global private_dns_mode hostname'

It does not remove YouTube ads, which come from the same servers as the videos. If an app stops playing or the TV reports "No internet" (the resolver is down or unreachable), switch back with tools/tv.py 'settings put global private_dns_mode opportunistic'.

AirPlay? Not from this repo. Chromecast built-in stays for Android phones. For iPhones, jqssun/android-airplay-server works; an install script for it is in PR #84.

Can I just download the APK? Build it with the one-line script; it takes a minute and you control what goes on your TV. No prebuilt binaries.

The most useful contribution is your TV's debloat list, so the next person with that model does not have to rediscover it. Launcher improvements and sharper prompt wording are welcome too. CONTRIBUTING.md has the format and the testing we ask for. Built something on top, a launcher, a port, a theme? Add it to SHOWCASE.md, where eleven projects already live: a webOS port for LG, a Stremio shelf, a Hisense restyle, Fire TV launchers, an AirPlay installer.

Questions about your TV: GitHub Discussions. Press and partnerships: hello@itsgathin.com. Security issues: report them privately through the Security tab, see SECURITY.md.

MIT, see LICENSE. The Outfit typeface is under the SIL Open Font License, see launcher/FONT-LICENSE-OFL.txt.

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →