[thatRailsGuy]

tools/theme-catalog.sh (and theme-catalog.ps1) puts theme folders on the TV under themes/<name>/ without making any of them active. Launcher settings then shows a Theme row that copies the picked one over the active theme, as theme.sh would, and writes theme_revision as pick:<name> so the existing sync clears the on-TV choices and the row can show the current name. A device.json is laid over every theme (pushed or picked), so a TV's app_keys and live_tv_package survive a switch. Without a catalog the row stays hidden and nothing new runs. Docs: themes/README.md#switching-themes-on-the-tv, docs/launcher.md, and a Tools row in the README.

Prior art: the on-device picker in abhishek00235's fork (SHOWCASE.md), redone on current main, with folders found on the TV instead of a fixed list and the device layer added.

APK: 587,073 → 588,965 B (+1,892, 859 B under the gate).

Tested on: TCL 65QM6K (Google TV), Android 14, build UTT2.250416.001. All 28 themes pushed with the catalog script, switched between several on the TV, and the remote's app_keys buttons checked with the real remote after switching.

If this touches the launcher

• Verified on a real TV, screenshot attached (screenshots to follow in a comment)
• D-pad checked from every edge (Up, Down, Left, Right): the new row sits in the settings column and was navigated with the remote; not checked edge by edge
• No network, no background service, no new permission
• New strings in values/strings.xml and the other values-* folders: English and Hebrew only (test_hebrew_resources requires it). Adding the 20 fuller locales cost ~940 B and left the APK 3 B under the gate, so I left them for the translation workflow
• Anything TV-specific is in config.xml or a theme, not in code

Checks: ./gradlew testReleaseUnitTest lintRelease assembleRelease clean (new ThemeCatalogTest), python -m unittest discover -s tests: 3097 tests OK.

[github-actions]

maintainer-bot review · this one needs a maintainer decision · Leans: close (60%)

Thank you for the careful device.json layer that keeps a TV's app_keys across theme switches, and for testing it with all 28 themes on a real QM6K. An on-TV theme picker is a bigger launcher feature than the small core takes, so we suggest it lives in your fork with a row in SHOWCASE.md, as the earlier on-TV theme reader did.

Why it goes to a maintainer: confidence 0.60 is below 0.65.
The bot's own suggestion would be: your own fork, with a row in SHOWCASE.md.

Checks

• Note: possibly collides with Launcher: keep the config copy when config.json is not readable yet after boot #2327 (both PRs modify Config.java readOverlay and related methods around line 785; Launcher: keep the config copy when config.json is not readable yet after boot #2327 first)
• Note: possibly collides with Launcher: add Slovenian translation #2545 (both modify docs/launcher.md)
• Note: possibly collides with Launcher: reach a TV's settings when they are a service, not an activity #3198 (both PRs modify launcher/app/src/main/java/com/gathin/tvhome/LauncherSettingsActivity.java)
• Launcher: 205 lines changed in launcher/ (tests not counted)
• Note: new strings missing in 29 of 30 locales (ar, ast, b+es+419, b+sr+Latn, bn, ca…)
• OK: no new permission, no network use
• Size: size/L (+628 -11, 14 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}

[thatRailsGuy]

[Gathin23]

@thatRailsGuy thank you for the device.json layer that keeps a TV's app_keys across switches, and for checking all 28 themes with the real remote on your QM6K. At +1.9 KB the picker is bigger than the room the core launcher has left, so it fits best in your fork. A one-line SHOWCASE.md row with your screenshot is very welcome, next to the earlier on-TV picker.