cleanyourtv packages Wi-Fi Android debugging, package-disable scripts and a replacement Home launcher into one workflow for Android TV and Google TV. For developers, the consequence is a reversible way to modify a television without root or a cable: selected packages are disabled rather than uninstalled, and the project provides restore tooling.
The workflow changes package state
Setup requires a computer on the same Wi-Fi network as the television. Users must enable USB debugging, authorize the computer through the television’s debugging prompt and, when a separate Network or ADB debugging option is present, enable that too. The documented quick start uses a coding assistant with shell access, while a manual route is available through Python 3 tools and shell or PowerShell scripts. Project instructions
Before making changes, the workflow backs up the installed-package list and settings. It then applies model-specific selections with Android’s pm disable-user; the supplied disable.sh and restore.sh scripts apply or reverse the same debloat list. The project’s checklist also asks which apps the user needs and whether voice assistance, Chromecast and system updates should remain enabled. Package-management workflow
A small launcher supplies the new Home screen
The replacement app, com.gathin.tvhome, is described as roughly 280 KB installed. It is written in Java with AndroidX RecyclerView and designed for televisions with 1 GB of RAM; the repository says it uses no network connection, background services, video or blur effects. Building it requires JDK 17 and Android SDK platform 34. Launcher documentation
The project describes the resulting interface as Apple TV-style. It includes a dock, a top shelf for the focused app, an application grid, input controls, network status, settings access, themes and a clock screensaver. Launcher feature list
The installation scripts query which package owns Home and disable only launchers they recognize as tvlauncher or launcherx, unless the operator supplies an override or chooses to leave the stock launcher alone. The build-and-install script also rolls back if the new launcher does not become Home. Installation behavior
Compatibility stops at OS boundaries
The repository reports 54 tested TV lists across 23 brands. Its detailed list is not limited to television sets: it also covers streaming boxes, sticks and projectors, including Chromecast with Google TV, NVIDIA Shield, Xiaomi devices, Fire TV hardware and XGIMI projectors. Tested-device lists
The project targets Android TV and Google TV. Samsung televisions running Tizen and LG televisions running webOS use different systems. Fire TV can use the debloat portion, but Fire OS does not assign Home to a third-party launcher; the repository also notes that some China-market TCL sets refuse launcher installation. Platform limitations
Analysis: The project’s central engineering choice is to treat disabled-package state as the rollback boundary instead of deleting software. That makes restoration possible, but it does not remove the need for device-specific judgment. The checklist concerning voice assistance, Chromecast and updates shows the unresolved trade-off: packages considered bloat may also participate in integrated services a household wants to retain. A restore script can reverse state changes, but it cannot make that selection for the operator. The documented workflow and restore model
Top comments (0)