Remove Ads from Android TV and Google TV with an Apple TV-Style Launcher

tv-vibehack debloats any Android TV or Google TV over Wi-Fi and swaps the sponsored home screen for a clean launcher that looks like Apple TV. Nothing is rooted, flashed, or uninstalled, and a single restore command puts the set back the way it was.

Before: the stock Google TV home screen with a sponsored ad. After: the tv-vibehack launcher

The project began as an afternoon spent fixing a Mi TV in the author’s parents’ living room. That set played an advert before you could reach Netflix. Claude Code did the whole job by talking to the real television, and the prompt that drove it lives in the repo so you can run the same workflow on your own set. Most of the per-TV debloat lists in the repo came out of the replies to the tweet below.

The tweet: vibe coded my parents' TV this afternoon, with before and after screenshots

How do you replace an Android TV home screen without root?

You use the same debug bridge Android phones have. Switch on USB debugging in the TV’s developer options and the set starts listening on your Wi-Fi, asking once to allow your computer. Everything after that is standard Android tooling.

The workflow has three stages. First, back up the installed package list and settings. Second, disable the manufacturer’s telemetry, ad services, content rows and preloaded junk with pm disable-user. Those packages stay on the machine and remain recoverable, which is what makes the restore script able to undo every step. Third, install a small native launcher and make it the default home screen.

Bloatware differs by brand, so the prompt tells your coding assistant to discover it on your TV first and ask you before it touches anything you might use.

What do you need, and how long does it take?

You need a computer on the same Wi-Fi as the TV and a coding assistant with shell access. The author used Claude Code; anything similar works.

On the TV, open Settings, then Device Preferences, then About. Press OK on Build seven times, go back, open Developer options and turn on USB debugging. Some sets also show a Network or ADB debugging toggle. Turn that on too and keep the TV powered up.

On the computer, open your assistant, paste the prompt from PROMPT.md and fill in your TV model. Accept the “Allow USB debugging?” dialog when it appears on the set, then answer the checklist questions. Which streaming apps do you use, which four go in the dock, and do you keep the voice assistant, Chromecast and firmware updates. The assistant then backs up, debloats, builds and installs the launcher, verifying each step against screenshots pulled from the TV.

On a 1 GB Mi TV the first run took one afternoon. People running the workflow with this repo as context report about fifteen minutes.

What does the new home screen look like?

The background is pitch black. A lighter rounded band at the bottom holds your four favourite apps in exactly the position Apple TV puts its dock.

A top shelf shows the focused app’s name in large type, with an ambient glow in a colour pulled from the app’s own artwork. The rest of your apps sit in a grid that slides up when you press Down. Focus is handled by one floating glass highlight that springs from tile to tile, lifting the focused tile slightly and showing its name. Each tile drawing its own border is gone.

Three frosted buttons sit on that shelf. Inputs gives a dropdown of HDMI ports, AV and Live TV. Wi-Fi shows the network you are on. Settings opens system settings. A greeting, a large thin clock and the date are set in the Outfit typeface. An optional Clock screensaver drifts the clock and the glow to a new spot every minute so nothing burns in. The system runs it only while the TV is idle.

The remote’s Input button can keep working. On Google TV the stock launcher handled it, and an optional accessibility service maps KEYCODE_TV to the system input switcher inside any app. Turn it on with INPUT_KEY_SERVICE=1 at install time.

What disappears along with the old home screen is equally concrete. No sponsored rows, no “Discover” nags, no analytics phoning home, no apps you never asked for.

Which TVs are supported?

Anything running Android TV or Google TV, which covers Xiaomi and Redmi, TCL, Hisense, Sony, OnePlus, Realme, Nvidia Shield and most others.

Samsung (Tizen) and LG (webOS) run different systems and are not supported. Amazon Fire TV takes the debloat half only. Fire OS will not let a third-party launcher take over Home, so the Fire TV lists remove Amazon’s ads and telemetry while leaving the home screen alone.

Lists that people have tested and contributed live in examples/.

TV OS
BenQ E55-735 (Changhong AI PONT, DVB96BQ) Google TV 14
CHiQ AI PONT (DVB93CQ) Android TV 11
Hisense SmartTV 4K FFM (huangshan, MediaTek) Android TV 10
Insignia 55″ F30 4K Fire TV (NS-55F301NA25, AFTDCT31, duckie) Fire OS 7 / Android 9
NVIDIA SHIELD TV Pro 2019 (P2897, mdarcy) Android TV 11
OnePlus TV (D00, Dubai) Google TV 14
RCA AI PONT SA (Changhong, redwood, ISDB92RC) Android 14
SANYO ATV R2 (SCBC, Realtek RTD285O) Android TV 9
Sony BRAVIA 4K UR2 (BRAVIA_UR2_4K, MediaTek) Android TV 10
Sony BRAVIA XBR-65X900E (2017, BRAVIA_ATV2) Android TV 9
TCL 55″ 4K Google TV, 2023 (G10, G10_4K_US_NF) Google TV 12
TCL 65C725 (Smart TV Pro, BeyondTV4) Android TV 11
TCL BeyondTV (India) Android TV 9
TCL QM6K Pro, 2025 (G08, MediaTek tcl9618) Google TV 14
Xiaomi Mi Box S (MIBOX4, oneday), streaming box Android TV 9
Xiaomi Mi TV (MiTV-MOOQ0, croods) Android TV 10
Xiaomi Mi TV 4A (MiTV-MOOQ1) Android TV 10
Xiaomi MiTV-AESP0 stick (aquaman, 1 GB) Android TV 9
Xiaomi MiTV-AXSO0 (dangal; Mi TV 4C Pro 2019 / 4A Pro) Android TV 9
Xiaomi MiTV-MOOR2 (venom, MediaTek) Google TV 11
Xiaomi TV A Pro 75″ 2026 (MiTV-MZTU0, river, MediaTek) Google TV 14

A missing model is no blocker. The prompt discovers the bloat itself. Contributing your list afterwards means the next person with the same set skips that step.

Can you run the whole thing by hand?

Every step the assistant performs can be typed yourself. The tooling needs 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'      # run one shell command on the TV
printf 'cmd1\ncmd2\n' | tools/venv/bin/python -I tools/tv.py --batch   # several, one connection

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 and restore the stock launcher
Tool What it does
tools/tv.py A pure-Python ADB client handling shell, batch, push and pull. Works where the stock adb binary is blocked.
tools/b64push.py Uploads larger files such as APKs as base64 chunks and verifies the checksum.
tools/disable.sh / tools/restore.sh Apply or undo a debloat list. PowerShell versions sit next to them.

On Windows the PowerShell scripts need neither WSL nor Git Bash. With Android Studio installed nothing else is required, since the install script uses its bundled JDK and the default SDK location.

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
powershell -ExecutionPolicy Bypass -File tools\restore.ps1 -TvHost 192.168.1.50 examples\xiaomi-mi-tv-4a\debloat.txt

Both install scripts ask the TV which launcher owns Home and only disable one they recognise. Those are Google’s tvlauncher and launcherx. Override the check with STOCK_LAUNCHER=<package> (or -StockLauncher in PowerShell), or pass none to leave the stock launcher alone. After the switch they verify where Home actually resolves and put the stock launcher back if it is not the new one. Git Bash also works. The .sh scripts detect a Windows venv and turn off MSYS path rewriting themselves.

How do you configure and build the launcher?

The launcher is a small native Android TV app (com.gathin.tvhome, about 250 KB installed) written in plain Java with AndroidX RecyclerView and nothing heavier. It is built for sets with 1 GB of RAM, so there is no blur, no video, no network and no background service.

Everything tunable lives in launcher/app/src/main/res/values/config.xml. The dock order, apps to hide, your TV’s Live TV package, the number of columns (tiles shrink to fit from 5 columns up), and rows_below_dock for how many grid rows stay visible under the dock. On sticks and boxes with no HDMI or tuner the Inputs button hides itself.

Language follows the TV, with English, German, Spanish, Catalan and Simplified Chinese so far. If your TV does not offer your language system-wide, Android 13 and later can set it for the launcher alone. Catalan looks like this.

tools/tv.py 'cmd locale set-app-locales com.gathin.tvhome --locales ca'

Build and install with one command.

TV_HOST=192.168.1.50 launcher/build-and-install.sh

It needs JDK 17 and the Android SDK (platform 34, build-tools 34.0.0). On macOS.

brew install openjdk@17 android-commandlinetools
sdkmanager "platforms;android-34" "build-tools;34.0.0"
# newer command-line tools (sdkmanager forwards to the "android" CLI) take this form instead:
# android sdk install platforms/android-34 build-tools/34.0.0

Without Homebrew, the script finds a JDK 17 known to /usr/libexec/java_home and an SDK in ~/Library/Android/sdk, which is Android Studio’s default. The script installs a shrunk release build, about 250 KB instead of 1.6 MB, signed with the debug key so it installs over an older build. It also asks the TV to precompile the app, so the first launch does not wait for the JIT.

Remote navigation was tuned on purpose. Up and Down move exactly one row. Up from the dock goes to the top buttons, the ends of the button row do not fall through to tiles, and the last focused app is remembered when you come back even after the app list changes.

Optional: the Clock screensaver

A large thin clock and the date over an ambient glow, in the launcher’s style. Every minute the clock drifts to a new spot and the glow shifts colour. The system runs it only while the TV is idle. Turn it on over ADB, or pick “Clock” in the TV’s screensaver settings.

tools/venv/bin/python -I tools/tv.py 'settings put secure screensaver_components com.gathin.tvhome/.ClockDream; settings put secure screensaver_enabled 1'

It starts after the TV’s screen off idle time, which you can read with settings get system screen_off_timeout.

One more optional switch. Set show_home_settings_shortcut to true in config.xml and a Default home tile appears at the end of the grid. It opens Android’s own home-screen picker so you can switch launchers from the sofa. Most Android TV firmware ships no such page, and then the tile stays hidden. The stock launcher has to be enabled before it can be picked, which is covered in the restore instructions.

How do you get the stock launcher back?

Keep the list you applied. The restore script re-enables exactly those packages, re-enables and re-selects the stock launcher, and resets the three animation scales.

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 second argument is the stock launcher package. It defaults to Google’s tvlauncher, so pass launcherx on Google TV (and -Stock on Windows).

Three things the restore script does not do are worth knowing before you rely on it. It leaves the new launcher installed, and you uninstall that from the TV’s settings. It knows nothing about packages you disabled outside the list. It does not undo the optional accessibility services or a changed screensaver, and each of those is one settings command, shown in the troubleshooting section below. When the TV is unreachable, the TV’s own Settings and Apps page can re-enable packages too.

What breaks and how do you fix it?

These are the problems the author and contributors actually hit, written down so they do not bite you.

Connection problems

macOS says “No route to host” on adb connect even though the port is open. Recent macOS treats the Google-signed adb as its own app under Local Network privacy and silently blocks it. tools/tv.py avoids the binary entirely.

Some TVs have no “wireless debugging” toggle, Xiaomi among them. USB debugging alone opens network ADB on port 5555.

USB devices go dead while USB debugging is on, seen on the Xiaomi Mi Box S. Its firmware switches the USB port to ADB device mode, which cuts power to a USB speaker or drive. Switch USB debugging off when you are done, since the launcher does not need it.

Windows PowerShell 5.1 adds a byte-order mark to text piped into a program, which turned the first batch command into gibberish. tv.py now strips it, and the .ps1 scripts pipe clean UTF-8.

Git Bash rewrites paths such as /data/local/tmp into Windows paths. The scripts set MSYS_NO_PATHCONV=1 for you. Set JAVA_HOME and ANDROID_HOME before building there.

Problems on the TV itself

Chained pm commands (pm disable a; pm disable b) may silently stop after the first. Run one per shell call, which is what --batch does.

Large pushes hang through the Python client. Use tools/b64push.py for APKs.

Screenshots come out empty while Live TV or an HDMI input is on screen, seen on TCL. Press Home before screencap.

Disable the stock launcher only after the new one is installed. Otherwise the Home button lands on a factory test app.

The new launcher still does not own Home after the stock one is disabled, seen on Google TV (Xiaomi MiTV-MOOR2). Another system app answers HOME. That is com.google.android.tungsten.setupwraith, with .MainActivity at intent-filter priority 4 and .RecoveryActivity at priority 1. You cannot outrank it. Android ignores android:priority on HOME filters for apps that are not on the system image. cmd package set-home-activity prints Success without changing anything, even after a reboot. pm disable-user on one of setupwraith’s components is refused with a SecurityException. Disabling the whole com.google.android.tungsten.setupwraith package is what frees the slot. It is the first-run setup wizard, so everyday use is unaffected. Re-enable it before a factory reset, and listing it in your debloat.txt makes tools/restore.sh handle that for you.

The TV drops off Wi-Fi every minute right after the install, seen on Google TV 14 (Xiaomi MiTV-MZTU0). The same setupwraith .RecoveryActivity took Home and system_server crash-looped on it. The install script now starts the new launcher before disabling the stock one, sets the home preference last, since Android drops it whenever the set of HOME apps changes, then checks where Home resolves and re-enables the stock launcher if it is not the new one. Disable setupwraith as described above. If you are already in the loop, run tools/tv.py 'pm enable --user 0 com.google.android.apps.tv.launcherx'.

No on-screen keyboard after switching launchers, seen on Xiaomi. The default input method pointed at a Baidu keyboard that is not installed. Fix it with one command.

tools/tv.py 'ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME'

Wrong time zone, clock off by 30 or 60 minutes, seen on Xiaomi in Iran. The TV picked a neighbouring zone, and older firmware ships time zone data from before Iran dropped daylight saving in 2022. On Android 10 and newer you can check with tools/tv.py 'cat /apex/com.android.tzdata/etc/tz/tz_version'. Set the zone yourself.

tools/tv.py 'settings put global auto_time_zone 0; cmd alarm set-timezone Asia/Tehran'

If the clock then jumps an hour ahead in spring, a fixed offset keeps it right.

tools/tv.py 'cmd alarm set-timezone GMT+03:30'

The same applies to any country whose rules changed after the firmware was built.

Is this safe? Will it brick the TV?

Nothing is flashed, rooted or deleted, so the firmware itself is never at risk. Packages are disabled for the user profile, which lives in the data partition. What can go wrong is disabling something the TV leans on. One Hisense booted to Android Recovery until “Try again” was pressed. On Google TV, disabling the stock launcher without the setup wizard sent Home into a crash loop. Both cases and their fixes are in the troubleshooting section above.

The practical recipe is small batches. Apply a list in small batches, keep the backup folder the assistant makes, and have tools/restore.sh ready. Even with no tools at all, the TV’s own Settings and Apps page can re-enable packages, and a factory reset is the last resort rather than the first move.

Firmware updates need no special worry. Most lists disable the manufacturer’s update service, so updates arrive only when you re-enable it on purpose. If one lands anyway, the worst case is a package coming back enabled, and you re-run the script.

Streaming apps keep working as their APIs change because they still update through the Play Store, which is left alone. The launcher never talks to them. It lists what is installed and launches it, using Android launcher intents that have been stable for over a decade.

Access came through the Android Debug Bridge with one explicit “allow this computer” tap on the TV, the same as developing an Android app. The TV only trusts the key you approved, and you can switch USB debugging off afterwards while the launcher keeps working. No prebuilt APK is published. Build it yourself with the one-line script, which takes about a minute and keeps you in control of what goes on your TV.

Contributing and licence

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. The format and the testing asked for are in CONTRIBUTING.md.

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

Setup checklist

  1. On the TV, press OK on Build seven times to unlock developer options, enable USB debugging, and enable the network or ADB debugging toggle if one exists.
  2. On the computer, join the same Wi-Fi, create the venv, install tools/requirements.txt, and export TV_HOST with the TV’s IP.
  3. Run tv.py --probe to confirm the model and Android version, then pm list packages to see what is installed.
  4. Paste PROMPT.md, fill in the model, and answer the questions on streaming apps, the four dock apps, the voice assistant, Chromecast and firmware updates.
  5. Accept the USB debugging prompt on the TV, then let the assistant back up and disable packages in small batches, writing them into debloat.txt.
  6. Disable the stock launcher only after the new one is installed, using STOCK_LAUNCHER or -StockLauncher when the guess is wrong.
  7. Build and install with launcher/build-and-install.sh (JDK 17, SDK platform 34, build-tools 34.0.0).
  8. If Home gets hijacked on Google TV, disable the whole com.google.android.tungsten.setupwraith package and record it in the list.
  9. To reverse everything, run tools/restore.sh <list> [stock launcher package] and keep that list file somewhere safe.

FAQ

Does this need root?
No. It runs entirely over the Android Debug Bridge. Packages are only disabled for the user profile, the firmware is untouched, and nothing is uninstalled.

My TV is not on the supported list. Can I still use it?
Yes. The prompt discovers the debloat targets on your specific set and confirms each one with you before acting. Contributing your list afterwards helps the next owner of the same model.

What about Samsung and LG TVs?
They are not supported. They run Tizen and webOS respectively. Fire TV gets the debloat half only, since Fire OS refuses to let a third-party launcher own Home.

Will the remote’s input switcher button still work?
Yes. Install the optional accessibility service and set INPUT_KEY_SERVICE=1, which maps KEYCODE_TV to the system input switcher.

Is there a ready-made APK to download?
No prebuilt binaries are published. The one-line build script takes about a minute and keeps you in control of what gets installed.

Is the launcher gone after a restore?
No. The restore script does not uninstall it, so remove it from the TV’s settings if you want it gone. Packages you disabled outside the list, the optional accessibility services and a changed screensaver are also outside the restore script’s reach.

The clock is off by half an hour or an hour. What now?
The firmware’s time zone data is usually the culprit. Turn off automatic time zones with settings put global auto_time_zone 0, then set your zone or a fixed offset with cmd alarm set-timezone.

What licence is this under?
MIT for the code. The Outfit typeface is under the SIL Open Font License.