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
Merge PR #3538: tools: manage.py set refuses a keycode list the launcher would throw away
Gathin23a32b628411da
diff --cc themes/README.mdindex c88a47b85,83927c226..b7ee57a81--- a/themes/README.md+++ b/themes/README.md@@@ -165,8 -165,7 +165,9 @@@ A new key needs one there in the same p| `greeting` | string | Replaces the time-of-day greeting while the festive skin is on || `accent_color` | `#RRGGBB` | Colour of the focus glow while the festive skin is on; diya gold if not set, pumpkin orange for `halloween` || `settings_key_scancodes` | list, `config.xml` only | The same buttons by Linux scancode, for `HomeKeyService` (`HOME_KEY_SERVICE=1`); the Xiaomi/Fengmi projector remote's gear is scan 384. `Config.java` reads `settings_key_keycodes` out of a theme but never this one, so a `config.json` that sets it is dropped - it belongs in `config.xml` before the build. Find a code with `tools/tv.py 'getevent -lt'` |+| `settings_key_keycodes` | list of keycodes | Remote buttons that open Settings, for `HomeKeyService` (TCL Google TV gear: `[83]`) |+| `settings_key_clear_task` | bool | With `settings_key_panel` off, those buttons clear the TV Settings task before opening Settings, so Back goes Home. For boards whose firmware also opens its own page in that task from the same press: a Skyworth 2K NSTV (Google TV 14) gear sends `KEYCODE_SETTINGS` too, which `com.mediatek.tv.service` turns into Display & Sound under Settings (`false` by default) |+ | `settings_key_keycodes` | list of keycodes | Remote buttons that open Settings, for `HomeKeyService` (TCL Google TV gear: `[83]`). Every entry is a whole number of at least 1: one entry that is a word or a number under 1 and the launcher keeps `config.xml`'s list instead of yours, so no button is added, and tools/manage.py's `set` refuses such a list before writing it || `settings_key_panel` | bool | Those buttons open a small quick settings panel (TV settings, Display, Network, Apps, Launcher settings) instead of the TV's Settings || `settings_fallback_components` | list, `config.xml` only | Vendor screens tried in order when nothing usable answers the standard Settings action (Xiaomi China, TCL/FFALCON, and Fire OS, where the real menu lives in its launcher), each as `package/activity`; the first one whose package is installed wins, and when none is, the standard intent is sent anyway and may open nothing. Fire OS answers that intent with a `CTSDummy` stub, which counts as missing so the fallback runs. A package named here also has to be listed in the launcher's `<queries>` (Android 11 package visibility), so a set whose settings app is neither of these needs a build, not a theme push. Not read from a theme || `restore_key_services` | bool | After a force stop of the launcher, Home puts the remote's accessibility helpers (`HomeKeyService`, `InputKeyService`) back on the enabled list; needs `RESTORE_KEY_SERVICES=1` (`-RestoreKeyServices` on Windows) on every install, since an install without it takes the grant back. Off by default |