Debloat any Android or Google TV over Wi-Fi and get an Apple TV-style home.
Python adbadblockandroid-tvandroid-tv-launcherapple-tvbloatware-removalclaude-codedebloatfire-tvgoogle-tvlauncherprivacysmart-tvsony-braviatclvibe-codingxiaomi
Workflow: Add an off-by-default launcher switch
When to use this: a launcher behaviour or look that existing config keys can't carry.
The core takes a switch only if it changes nothing until a theme or config.xml turns it on:
- Add the key to
launcher/app/src/main/res/values/config.xmlwith a comment that says what it does and that a theme can set it, defaulting to off (false,0or the current behaviour). - Read it in
launcher/app/src/main/java/com/gathin/tvhome/Config.java, from the resource and from the theme JSON, the way existing keys such asshow_statsare read. - Add a row to the Keys table in
themes/README.md, and the key's screenshot row indocs/switches.md(docs/switches/<key>.jpg, from a real TV with the key on: 16:9, under 300 KB, personal things blurred);tests/test_switches.pyrefuses a Keys row without one, so the two go in the same pull request and the site's Switches tab picks it up from there. - If it adds a row to Launcher settings, put its strings in
launcher/app/src/main/res/values/strings.xmland everyvalues-*folder. - With the key off, nothing new runs: no receiver, no service, no write, no permission grant in the install script. The bot checks this in the diff, not in the description.
- Add a JVM unit test under
launcher/app/src/test/java/com/gathin/tvhome/for any logic that can be tested without a TV. - Keep it small: a switch should cost a few hundred bytes to about 1 KB of APK. Build and check the size
gate; the gate is hard. The size is also printed on the front pages, so a switch that moves it updates
STATSintools/readme_stats.py- the numberdocs/card.jpgis drawn from, and what each page's alt text describes - and theabout N KBin everyREADME*.mdthat shows that card: its alt text, thelauncher/build-and-install.shTools row and the Launcher section's first sentence, in each page's own words. - Verify on a real TV with the switch on and off, D-pad from every edge, and attach screenshots.
- If you can, run the regression check in
perf-ab.mdwith the switch on: a baseline before you start, your build after, and the numbers in the PR. It's optional, but welcome.
Anything TV-specific goes in config.xml or a theme, not in code. A bug fix that corrects wrong behaviour needs
no switch. No new dependencies in launcher/app/build.gradle without an issue first.
Then run the tests: python3 -m unittest discover -s tests -v.