Speed Up Android TV With Claude: The ADB Debloat Guide

Yes, you can speed up a slow Android TV with Claude — and the best way takes about 30 minutes, needs no root access, and is fully reversible. The winning combination is Claude Code, Anthropic's terminal assistant, driving Android Debug Bridge (ADB) over your home Wi-Fi: it reads your TV's installed apps, sorts the bloat from the essentials, and runs the cleanup commands with your approval at each step.

Here is exactly how it works, what is safe to remove, and how to undo anything.

One honest note up front: Claude does not run on your TV, and there is no Claude app for Android TV. Everything happens on your computer. Claude Code runs ADB commands from your laptop or desktop to the TV over your local network, and you approve each command before it runs.

If you would rather not install anything, the chat version of Claude can still guide you — you paste in your TV's app list, it tells you what to disable, and you type the commands yourself.

What Claude Can and Cannot Do for Your TV

Claude's strength here is judgment, not magic. A typical Android TV ships with 100 or more installed packages, and their names tell you almost nothing. Names like com.google.android.tvrecommendations or tv.samba.ssm mean little to most people, yet one is a recommendation engine you can live without and the other tracks what appears on your screen for advertising. Claude reads the full list, explains each package in plain language, and groups them into safe-to-disable, keep, and ask-first categories.

What Claude cannot do is just as important. It cannot reach your TV on its own, install anything without ADB, or fix hardware limits. A TV with 1 GB of RAM will never feel like a flagship phone, and no AI tool changes that. What this process fixes is the software drag: telemetry services, ad carousels, preloaded apps, and recommendation feeds that consume memory and CPU on every boot.

It also cannot work on every television. This method applies only to Android TV and Google TV devices — Sony, TCL, Xiaomi, Hisense, Philips, Chromecast with Google TV, Nvidia Shield, and Android TV boxes. Samsung's Tizen, LG's webOS, and Roku have no ADB access, so none of the commands below apply to them.

Before You Start: Check Your TV Qualifies

Confirm three things before you begin. First, your TV or streaming device runs Android TV or Google TV — check Settings, then About, for the Android TV OS build entry. Second, your computer and TV are on the same Wi-Fi network, since ADB connects over your local network. Third, you have about 30 minutes and your TV's remote nearby, because you will approve a debugging prompt on the TV screen itself.

Take one precaution that costs nothing: note down your TV's exact model number from the About screen. Claude uses it to tailor its recommendations, because bloatware differs sharply by brand. Xiaomi's PatchWall, TCL's recommendation services, and Sony's Samba TV tracking are completely different packages, and a generic disable list is how people break things they actually use.

Step 1: Enable Developer Options and Network Debugging

On Google TV, open Settings, then System, then About. Highlight Android TV OS build and press the centre button on your remote seven times until you see "You are now a developer." On older Android TV sets the path is Settings, then Device Preferences, then About, and the entry is called Build. Either way, the seven-press unlock is the same.

Go back to System or Device Preferences and open the new Developer options menu. Turn on USB debugging. If you also see a Network debugging or ADB debugging toggle, turn that on too — that is the switch that allows your computer to reach the TV over Wi-Fi. On TVs running Android TV 13 or newer you may see Wireless debugging instead, which uses a pairing code rather than a plain connection.

Find your TV's IP address while you are in Settings: open Network and Internet, select your connected Wi-Fi network, and note the IP address. You will need it in the next step. Keep the TV switched on throughout the process.

Step 2: Install ADB and Connect Over Wi-Fi

ADB is part of Google's official platform-tools package. On a Mac with Homebrew, run brew install android-platform-tools. On Windows, download platform-tools from Google's developer site, unzip it, and open a terminal in that folder. On Linux, install it with your package manager. Run adb version to confirm your terminal can find it. The full connection reference is in Android's official ADB documentation.

For TVs with the older Network debugging toggle, connect with the TV's IP address on port 5555:

adb connect 192.168.1.50:5555
adb devices

Replace the address with your TV's IP. A prompt appears on the TV asking you to allow debugging — accept it, and tick "Always allow" only if this is your own trusted computer. The adb devices command should then list your TV as "device". If it says "unauthorized", check the TV screen for the prompt you missed.

For TVs with Wireless debugging (Android TV 13 and newer), pair first. On the TV, open Wireless debugging, choose "Pair device with pairing code", and note the IP address, port, and six-digit code. On your computer, run adb pair IP:PORT and enter the code when asked. Android's documentation confirms pairing is a one-time step; the TV stays paired until you explicitly forget the computer or revoke debugging authorizations.

Step 3: The Best Solution — Claude Code and CleanYourTV

This is the method that went viral in October 2026, and for good reason. CleanYourTV is an open-source project that gives a coding assistant a structured prompt and safety checklist for debloating Android TV sets over Wi-Fi. At the time of writing it carries over 57,000 GitHub stars and contributor-tested lists covering 472 TV models across 129 brands. It never uninstalls anything: it disables packages with pm disable-user, keeps a backup, and ships a one-line restore.

To use it, install Claude Code on your computer — see Claude Code's official documentation for the current install steps — then clone the CleanYourTV project on GitHub, open that folder in Claude Code, and paste the project's PROMPT.md file with your TV model filled in. Claude Code connects over ADB, backs up your installed package list and settings, and walks through a checklist: which apps you use, whether to keep the voice assistant, Chromecast, and automatic updates.

The assistant then works through the bloat in small batches, asking before it touches anything you might use. It disables manufacturer telemetry, ad services, content rows, and preloaded apps, then builds and installs a lightweight launcher to replace the ad-filled home screen.

The whole run takes about fifteen minutes with the repo as context. If you already use Claude Code, you may know its Projects feature for running parallel AI workers — the same approval-based approach applies here, with every command shown before it runs.

Keep the approval prompts on. Claude Code asks before running each shell command by default, and that is exactly what you want when the target is your television. Never switch it to auto-approve mode for this job: the point of having an AI assistant is that it explains each change and lets you veto anything that sounds wrong.

The No-Install Alternative: Claude Chat as Your Guide

If installing Claude Code feels like too much, the chat version of Claude works as an expert guide while you type the commands. Connect ADB as above, then dump your TV's full package list to a file:

adb shell pm list packages > tv-packages-backup.txt

Paste that list into a Claude chat with a prompt like: "This is the package list from my Sony Bravia running Google TV. Sort these into: safe to disable, must keep, and ask me first. Explain each one in plain language, and give me the exact adb commands for the safe ones only." Claude will return a categorized list with explanations and ready-to-paste commands. You stay in control of every keystroke.

This route is slower than Claude Code, but it teaches you what is actually on your TV, and it works from any browser with no installs beyond ADB itself. Claude Code is powered by Anthropic's Claude models, and recent generations such as Claude Fable 5.2 are strong at exactly this kind of analysis: long lists, careful categorization, and precise command output.

The Commands That Actually Speed Things Up

Whether Claude Code runs them or you type them yourself, these are the commands that do the real work. Run them in small batches, and check the TV still behaves normally after each batch before continuing.

List everything installed, and list what you have already disabled:

adb shell pm list packages
adb shell pm list packages -d

Disable a package for the main user without uninstalling it. This is the safe command — the package stays on the device and can be switched back on:

adb shell pm disable-user --user 0 com.example.bloatware

Re-enable anything you disabled by mistake, using the same package name:

adb shell pm enable com.example.bloatware

Speed up the interface by shortening animations. The default scale is 1; 0.5 makes every transition twice as fast, and 0 turns animations off entirely. These settings survive reboots:

adb shell settings put global window_animation_scale 0.5
adb shell settings put global transition_animation_scale 0.5
adb shell settings put global animator_duration_scale 0.5

Limit background processes through Developer options on the TV itself: open Developer options, find Background process limit under the Apps section, and choose "At most 4 processes". Avoid "No background processes" — it forces every app to cold-start and makes the TV feel slower, not faster. Note that this toggle may reset after a reboot on some sets, so check it again if the TV starts feeling heavy after an update.

Optionally, block ad and tracking requests at the DNS layer. This does not speed up the processor, but it stops the home screen from fetching ad content on every visit:

adb shell settings put global private_dns_mode hostname
adb shell settings put global private_dns_specifier dns.adguard-dns.com

What Is Safe to Disable — and What to Never Touch

Disabling the wrong package can break Wi-Fi, the remote, or the home screen itself, so this table matters more than any other section. The rule is simple: telemetry, ads, and preloads go; anything that manages connectivity, input, or the launcher stays until you have a replacement ready.

The setupwraith warning deserves emphasis: on Chromecast with Google TV, that package manages active Wi-Fi profile credentials. Disabling it can sever the wireless connection mid-session and leave you locked out of ADB with no easy way back. Similarly, never disable your only launcher before a replacement is installed — without a home screen, the TV boots to a blank display and only ADB or a factory reset will recover it.

Work in batches of five to ten packages, then use the TV normally for a few minutes. If something you use stops working, re-enable the last batch before going further. This slow-and-steady approach is what separates a faster TV from an afternoon of troubleshooting.

Best Android TV Speed Tweaks That Need No Computer

Not every improvement needs ADB or Claude. If you own the best Android TV you could afford and it still feels slow, start with these remote-only fixes before you touch a terminal. They help any streaming device, including an older Android TV box that is struggling with modern apps.

First, uninstall apps you never open: Settings, then Apps, then each app, then Uninstall. Second, clear the cache of heavy apps like YouTube and the Play Store from the same Apps menu — clearing cache is safe and keeps your sign-ins, unlike clearing data, which signs you out.

Third, restart the TV properly from Settings rather than just switching it off; many sets only sleep when you press power. Fourth, check free storage: a TV with almost no free space slows to a crawl, and removing one or two large apps can transform it.

Finally, turn off the features you do not use. If you never use the "Discover" tab's recommendations, switching the home screen to "Apps only mode" (where your set offers it) removes the heaviest part of the interface at a stroke. These tweaks alone can make a noticeable difference, and they stack with the ADB cleanup above.

How to Undo Everything

Every change in this guide is reversible, which is the whole point of using pm disable-user instead of uninstalling. To undo a single package, run adb shell pm enable with its package name. To see everything you disabled, run adb shell pm list packages -d. If you used CleanYourTV, its restore script re-enables everything it touched in one step.

To undo the settings tweaks, set the three animation scales back to 1, and set the background process limit back to "Standard limit" in Developer options. To undo the DNS change, set private DNS mode back to automatic in the TV's network settings. Then turn off USB debugging and network debugging in Developer options — leaving ADB open on port 5555 is an unnecessary exposure on your home network.

Factory reset is the last resort, and it works: disabling is stored per user, so wiping the TV restores every package to its original state. You will need to sign into your apps again afterwards, so treat it as the final option, not the first. If the TV boots to a blank screen because the launcher was disabled, connect over ADB and re-enable the launcher package — or use the remote to reach Settings and reset from there.

Frequently Asked Questions

Can Claude connect directly to my Android TV?

No. Claude has no Android TV app and no direct connection to televisions. Claude Code runs on your computer and sends ADB commands to the TV over your home Wi-Fi, with your approval for each command. The chat version of Claude cannot send commands at all — it analyses your package list and tells you what to type.

Is disabling bloatware with ADB safe?

Disabling with pm disable-user is safe when done carefully, because nothing is deleted and every change can be reversed with pm enable. The risk comes from disabling system-critical packages such as Wi-Fi credential services, the only launcher, or remote-control services. Work in small batches, keep the backup list, and never disable a package you do not understand.

Will this void my warranty or break Netflix?

This method uses only official Android tooling, with no root access and no bootloader unlock, so it does not trip the protections that affect DRM-protected playback. Streaming apps keep working normally. Because nothing is uninstalled, a factory reset returns the TV to its exact original state if you ever need warranty service.

Should I buy a new Android TV box or fix the one I have?

Try the cleanup first — it costs nothing and takes half an hour. If your streaming device has 2 GB of RAM or more, debloating plus faster animations usually restores a responsive feel. If it has 1 GB of RAM and a very old processor, the cleanup still helps, but a newer Android TV box will feel faster in ways software cannot match. Judge by the result, not by the age on the box.

Do I need to keep developer options on afterwards?

No. Once you finish, turn off USB debugging and network debugging in Developer options. The disabled packages stay disabled and the animation settings persist, so you lose nothing by closing the debug port. Turn debugging back on only if you want to make further changes later.

The Bottom Line

The best way to speed up an Android TV with Claude is Claude Code plus ADB: connect over Wi-Fi, let the assistant categorize your TV's bloat with the CleanYourTV safety checklist, approve each batch of disables, and finish with faster animations and a lighter home screen. It takes about 30 minutes, needs no root, and every change can be undone.

If you prefer not to install Claude Code, the same result is reachable with Claude chat guiding your own typing — slower, but just as safe. Either way, your TV ends up doing what you bought it for: showing your apps quickly, without the advertising and telemetry slowing it down.