[xbsheng]

The app_keys row said an input:<input id> target switches to that TV input, and nothing else. Since the
merge of #3173 (RemoteKeys.launch, launcher/app/src/main/java/com/gathin/tvhome/RemoteKeys.java) that
switch is aimed at live_tv_package first and only falls back to the bare channel URI, so the row now says
so: set live_tv_package, or an app that also claims the channel URI (the Fluffy file manager on a TCL G03)
can take the press or turn it into a chooser. It also says that input_uri_scheme and input_action shape the
Inputs rows and a tile's launch_actions entry rather than a remote key: openInput() in MainActivity reads
both, RemoteKeys.launch() reads neither.

One table row in themes/README.md, no code, no new test (wording only).

Tested on: no TV; CLEANYOURTV_STRICT=1 tools/venv/bin/python -m unittest discover -s tests → 2894 tests
OK (skipped=26), python3 tools/gen_tables.py --check exit 0. The claims were read from RemoteKeys.launch()
and MainActivity.openInput() on this branch.

If this adds or changes a TV list

• not a TV list

If this touches the launcher

• no launcher code changed; the row only describes what the merged Launcher: an input: app key opens in the Live TV app first #3173 does

If this adds or changes a theme

• no theme added

[github-actions]

maintainer-bot review · suggests merge (p3)

Thanks for checking the app_keys row against RemoteKeys.launch() and openInput(). The live_tv_package note and the Fluffy chooser example will save TCL owners some confusion, and this wording-only fix looks ready to merge as it is.

Checks

• Size: size/S (+1 -1, 1 files)

This is a suggestion; a maintainer makes the final call. A maintainer can comment /bot review to run it again.

_{Reviewed by maintainer-bot · runs on 0G Private Computer}

[Gathin23]

Thanks @xbsheng, the themes README's app_keys row now says an input: key asks live_tv_package first and that input_uri_scheme is the tile, so the docs match how remote keys behave.