Debloat any Android or Google TV over Wi-Fi and get an Apple TV-style home.
Workflow: Add or update a TV list
When to use this: you tested a TV's debloat list for a few days and want to share it, or you have a second unit or a fix for a list that exists.
- Check
examples/README.mdfirst. The same product code and firmware as an existing folder is usually a second unit or a re-badge: add your notes to that folder instead of a new one. - Create
examples/<brand>-<model>/debloat.txt, lower-case with hyphens. Copy the format ofexamples/xiaomi-mi-tv-4a/debloat.txt:- The first line is a comment with the exact model, Android version and firmware build
(
tools/tv.py --probeprints them). - Then the Apply and Undo lines, the stock launcher and Live TV package if they differ, and what was kept and why.
tests/test_list_gives_commands.pyrefuses a header that names none of the five scripts and no README: a folder whose firmware needs a batch of its own gives the commands in itsREADME.mdinstead, which counts. - One package per line, grouped under a comment that names the group, with a trailing comment on anything non-obvious. No duplicates, nothing but package names outside comments.
- The first line is a comment with the exact model, Android version and firmware build
(
- List only packages you actually disabled and lived with for a few days. Note anything you re-enabled. Mark untested entries as comments.
- Add
examples/<folder>/tv.jsonbeside the list, likeexamples/xiaomi-mi-tv-4a/tv.json:{ "tv": "Xiaomi Mi TV 4A (MiTV-MOOQ1)", "os": "Android TV 10", "brand": "Xiaomi", "notes": "PatchWall, Mi analytics, SmartShare, MiLink" }tvandosfill the folder's row in the TV tables,brandthe README's brand grid (spelled as it is there),notesthe Notes cell inexamples/README.md: one line of Markdown, links relative toexamples/,\|for a pipe. One thing in it is read back: a package named in backticks withkept,disabledorrefusedstraight after it is a claim about what the list does, andtests/test_example_readme_package_fates.pyholds it to the list -keptandrefusedhave to be off an active line,disabledon one (the stock launcherlauncher/build-and-install.shtakes Home from is the exception) - so a package left commented out is notdisabledhowever the comment reads, and a package the list still sends is notkept. Any other wording after the name claims nothing, which is hownotesstays free prose.readme_osis the one optional key: it is the OS cell of the two-column table inREADME.nl.md, for a set whose row there should read shorter than the same set's row inexamples/README.md- that table has room forGoogle TV launcher on Android TV 11, the short one forGoogle TV 11.tests/test_examples.pychecks the file. - Change nothing outside the folder. The tables in
examples/README.mdandREADME.nl.md, the brand grid inREADME.md,README.nl.md,README.de.md,README.uk.mdandREADME.tr.md, and the counts (theTV modelsnumber in the card's alt text) are generated from everytv.jsonbytools/gen_tables.py, which a maintainer runs after merging; CI compares them only onmain. One copy of those counts is outside the generated blocks: the story sentence that shows the card on the same five front pages ("The lists now cover 387 TV models from 103 brands") is prose, so a regeneration moves the picture and leaves the sentence where it was - the round that took the tree to 387 models shipped 380 in the story two screens below the card.tests/test_press_counts.pyreads the pair out of the sentence and holds it to the alt text beside it (README.de.md states (TV models, brands) (380, 101) in its story sentence and its card states (387, 103)), so they move in the same commit. - A
README.mdfor TV-specific notes and aconfig.jsonwith the dock are welcome in the folder. Notes are free prose; three things in a README are read back, two of them against the list beside it. A package count ("The 38 packages that were disabled", "the debloat list disables 71 packages") is compared with whattools/disable.shwould send for the list, so a line added or commented out later moves the number in the README with it:tests/test_example_list_count.pyanswersexamples/<folder>/README.md says 12 packages in the debloat.txt row and its debloat.txt carries 8. A sentence the page wraps across two lines is still read as one sentence, so a break cannot hide the number. Its undo is the other: the restore command a README shows passes the same stock launcher as the list's own Undo line, or none where the list passes none, because those two are where an owner looks for the way back and the copy that passes a different package leaves the stock home disabled.tests/test_folder_undo_agrees.pynames each difference (the Skyworth 7S60_A5 README passed the Coocaa home while its list passed nothing). The third is a path from the repository root written in backticks, which is what a reader copies into a terminal: the filelauncher/build-and-install.shwith its suffix, never the bare name, andtests/test_example_readme_paths.pyreads every folder's README and names each path this tree does not have (a Windows twin written with backslashes, a placeholder such asexamples/<your tv>/debloat.txtand the folders.gitignorelists are not read as paths). Thatconfig.jsontakes only the keysthemes/README.md's Keys table says a theme can set: the rows it marksconfig.xmlonly - the vendor settings screens, the icon tiles - are never read out of a pushed file, sotheme.shdrops them without a word and the launcher keeps its own value. A set that needs one wants that line in the folder'sREADME.md, for the owner to set inlauncher/app/src/main/res/values/config.xmlbefore building.tests/test_shipped_config_keys_are_read.pyholds every shippedconfig.jsonto the table. Do not add install or restore scripts, Private DNS or AdGuard setup, orpm uninstallsteps: the folder only disables, andtools/disable.shandtools/restore.shdo the rest.tests/test_list_folders_ship_lists_only.pyholds every folder underexamples/to that, so a script in the folder is a red suite rather than a second answer to the undo every list already has.
A model with notes but no several-day list goes in docs/devices/<brand-model>.md, with one line under the notes
list at the end of examples/README.md. A folder in examples/ must have packages in it.
Update an existing list
Keep the header accurate: add the second unit's model, firmware and region rather than replacing the first.
Explain each added or re-enabled package in a comment. If the folder's README says how many packages the list
holds, that number moves with the list in the same edit (step 6). A list that disables the firmware updater says
why in the header; keeping it enabled is preferred. pm hide or pm block needs the matching undo in the header.
Edits to someone else's list are judgement calls, so say in the PR which TV you tested on and for how long. If the
row should say something new, change the folder's tv.json, not the tables.
Then run the tests: python3 -m unittest discover -s tests -v.