Home · Community report
Debloat a smart TV over ADB
A Muse user reports it compared two firmware versions, reached their TV over Tailscale and disabled 10 packages with ADB, calling every change fully reversible. The post names no model or packages, so this page shows how to debloat a smart TV one approved, undoable step at a time.
What you can get
What it is
Debloat plan and change log
A written debloat plan for one TV listing each package, why it is a candidate and how to re-enable it, plus a log of what was disabled; not a firmware modification or a guarantee the TV runs faster.
It came back right when
- Every package in the plan has a matching re-enable command
- The TV boots to the home screen, plays video and responds to the remote after each change
- A saved baseline package list exists from before the first change
The checks are editorial, not from the source.
- Prepare
The TV's brand, model and firmware version
- Ask and review
Write down the TV's model and firmware version from its settings, and list the apps and inputs you rely on so they stay off the disable list.
- Check the result
Every package in the plan has a matching re-enable command
Editorial, not from the source
Works when
- Android TV, Google TV or Fire TV sets where ADB debugging can be turned on
- Owners who can test the TV after each change and keep a restore log
Does not work when
- TVs on a platform without ADB access
- Sets under a warranty or rental agreement that forbids software changes
The source case
@Chatsalll reports that Muse downloaded the last two firmware versions of their TV and, in their words, reverse engineered them to compare what had changed, then wrote a debloat plan. By their account it connected to the TV through Tailscale, used ADB to disable 10 packages, killed other background processes, and kept everything fully reversible. The post says the prompt is in an attached image, which is not in the captured text, and it names neither the TV model nor the packages that were disabled. Nothing in the post shows whether the TV ran better afterwards or that any change was actually reversed.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
Downloaded last two firmware versions and reverse engineered it to compared what’s changed
Source excerpt
Used ADB and disabled 10 packages 😯
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring The TV's brand, model and firmware version, ADB debugging enabled on the TV and a computer or remote session that can reach it on the network, A list of the apps and features you actually use, so they stay enabled. Source community report, checked 2026-10-19.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- The TV's brand, model and firmware version
- ADB debugging enabled on the TV and a computer or remote session that can reach it on the network
- A list of the apps and features you actually use, so they stay enabled
How to try it
Editorial, not from the source
- Write down the TV's model and firmware version from its settings, and list the apps and inputs you rely on so they stay off the disable list.
- Turn on developer options and USB or network debugging on the TV, then confirm a computer on the same network (or over a private VPN such as Tailscale) can connect with adb connect and accept the prompt on the TV screen.
- Export the current package list with adb shell pm list packages before changing anything, and keep that file as your baseline.
- Review the proposed plan line by line; drop anything tied to the launcher, system UI, network, updates or remote input, and make sure each line has a matching re-enable command.
- Approve and disable one package at a time, rebooting and testing video playback, inputs and the remote after each.
- Keep a log of every package disabled and the command that restores it, and re-check the list after the next firmware update, which can re-enable apps.
What this author reports
@Chatsalll replied that Muse "just did the same thing for me", then listed the steps: two firmware versions downloaded and compared, a debloat plan, a Tailscale connection to the TV, 10 packages disabled over ADB, background processes killed, and "Everything fully reversible".
The post points to a prompt in an image that the captured text does not include. It names no TV brand, model or package, and it gives no before-and-after measure, so how much the change helped is unknown.
Disable, don't uninstall
On Android-based TVs, the general practice is to disable a package for the main user with adb shell pm disable-user --user 0 <package> rather than removing it. That keeps the app on the system partition, and pm enable <package> brings it back. An uninstall for user 0 can usually be undone with cmd package install-existing, but disabling is the easier path to reverse.
A factory reset normally restores disabled system apps, so it is the last-resort undo. Before that, keep your baseline package list and the log of what you changed.
Reaching the TV remotely
ADB over the network listens on the TV's local address, usually port 5555. If the agent or computer is not on your home network, a private VPN like Tailscale is one way to reach it without opening a port to the internet. Turn network debugging off again when you finish, since anyone who can reach that port and is approved on the TV can run commands.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- The post does not name the TV model, the firmware versions or the 10 packages that were disabled, and the prompt it mentions is only in an image that is not in the captured text.
- The claim that the firmware was reverse engineered and that everything is fully reversible is the author's account; no diff, command log or restore test is shown.
- Disabling the wrong system package can break the launcher, updates or input; some TV makers treat ADB changes as outside normal support, so check your warranty terms.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
If it goes wrong
Editorial, not from the source
- The TV boots to a black screen or loops after a package is disabled
- Reconnect over ADB if you can and run pm enable on the last package you changed; if ADB no longer connects, a factory reset from the TV's recovery menu restores system apps.
- adb connect fails or shows the device as unauthorized
- Check that network debugging is still on, that the IP has not changed, and accept the authorization prompt on the TV screen with the remote.
- Disabled apps are back after a firmware update
- Updates can re-enable packages. Compare against your saved list and approve any re-disabling again, since the new firmware may have renamed or added components.
Common questions
Can Muse debloat a smart TV?
One user reports that Muse connected to their TV over Tailscale, used ADB to disable 10 packages and kept the changes reversible. The post does not name the TV or the packages, and this guide has not reproduced it.
Is disabling packages over ADB reversible?
Generally yes for disable-user, which pm enable undoes, and a factory reset usually restores system apps. Keep a log of every package and its restore command so you do not depend on a reset.
Which packages are safe to disable on a TV?
It depends on the brand and firmware. Leave the launcher, system UI, input, network, update and tuner or HDMI components alone, and test one package at a time.
Do I need Tailscale for this?
No. The author used it to reach the TV; a computer on the same local network can connect with adb connect directly.
Next
Related to this task
More in Home
Get recurring task recommendations — ask your own agent to check for relevant updates.