Android TV and Google TV devices

Partly tested

Changhong AI PONT

@frogu

Partial manual session: five advertising, personalization and feedback packages disabled for user 0; dumbtv home and SmartTube installed from repository-pinned checksum-verified APKs. Google TV launcher and setup handler disabled after dumbtv home launched. After an owner-performed reboot, HOME still resolved to dumbtv and the disabled states persisted. Wi-Fi settings were lost during the session; the owner reconnected Wi-Fi, restoring ADB. The cause was not established. Android Private DNS with a public resolver serving the HaGeZi Normal list was validated by Android; pagead2.googlesyndication.com and googleads.g.doubleclick.net resolved to loopback while YouTube and Prime Video domains resolved publicly. SmartTube launched successfully, then stock YouTube was disabled for user 0, not uninstalled. Playback was not verified. Fire OS all.sh and verify.sh were not run; this is not an end-to-end tested package profile.

Developer mode: Not observed: ADB was already authorized when this session started.
IP address: Observed in the Wireless debugging screen; navigation path not established.
Needed a person: Play Protect older Android target warningExpand More details and choose Install anyway for the checksum-verified dumbtv home release. Play Protect was not disabled.

Partly tested

Hisense SmartTV 4K FFM

@aswinaasokan18-spec

Tested on a real TV on 2026-10-21 with manual ADB. Disabled for user 0, all re-enableable: com.hisense.storemode, fusion.android.tv.demo, com.google.android.feedback, com.google.android.play.games, com.hisense.service.message, com.hisense.alexa, com.google.android.katniss (voice search goes with it), com.google.android.tungsten.setupwraith, com.google.android.apps.tv.launcherx. No PROTECTED or failed disables. The first seven survived two reboots; the launcher swap survived the one after it. Netflix launched from dumbtv home and HOME returned to it. Device codename songshan.

Developer mode: Settings
System
About
Android TV OS build
press OK seven times. Then Settings
System
Developer options
USB debugging: ON.
IP address: Settings > Network & Internet > the connected Wi-Fi network
Needed a person: Allow USB debugging?Accept on the TV with the remote, with "Always allow from this computer" ticked. Later connects need no prompt, including after a reboot.

Partly testedAndroid 14

onn. Streaming Device 4K Pro

@OSikorsky

Manual ADB session on Android 14. 16 packages disabled for user 0, plus launcherx and setupwraith for the launcher swap (18 total). dumbtv home installed and verified as HOME across a cold boot; Settings and the HOME key both re-checked afterwards. No DNS filtering was configured by choice, so no filter result is claimed.

Developer mode: Settings > System > About > scroll to Android TV OS Build > press select 7 times. Then Settings > System > Developer options > Wireless debugging: ON, and open 'Pair device with pairing code'. The Google TV remote-pairing code is a separate thing and does not authorize an ADB shell.
IP address: Settings > System > Developer options > Wireless debugging. The 'Pair device with pairing code' dialog shows the pairing endpoint; the main Wireless debugging screen shows a different connect endpoint. 'adb mdns services' lists both.
Needed a person: Wireless debugging pairing codePair with adb pair <host>:<pairing-port> using the six-digit code. The pairing port differs from the connect port on the main Wireless debugging screen. Port 5555 accepted connections afterwards without re-pairing.
Play Protect blocks the dumbtv home APKPlay Protect shows 'Unsafe app blocked - this app was built for an older version of Android' with only a 'Got it' button and no install-anyway option, because the launcher targets SDK 28 and this is Android 14. Both 'adb install' and 'pm install' then hang with no output while that dialog waits on screen; logcat shows Finsky VerifyApps verdict 3 launching PlayProtectDialogsActivity. Fix: Play Store > profile > Play Protect > gear > turn off 'Scan apps with Play Protect', install, then turn it back on.

Partly testedAndroid 14

Philips 24NA 4K Google TV

@lsukev

Manual ADB session on 2026-10-19 (repo scripts not run for the changes). 31 packages changed: 29 uninstalled for user 0 and 2 disabled (launcherx and setupwraith). The removed set included the vendor recommendation and shortcut apps, Google feedback, Play Games, ad services, federated compute, on-device personalization, the Google TV screensaver, katniss and hotword enrollment, the MediaTek system updater, and preinstalled streaming apps the owner does not watch. See the commented block in data/androidtv/packages.txt.

Developer mode: Standard Google TV path: Settings > System > About > Android TV OS build, press OK seven times, then Settings > System > Developer options and turn on debugging. The exact menu labels on this unit were not recorded.
IP address: Not recorded on this unit. On Google TV it is normally under Settings > Network & Internet > the connected network.
Needed a person: adb install hangs or fails silentlyadb install hung or returned without installing. Push the APK to /data/local/tmp and run pm install -r on it from adb shell; that succeeded and printed an explicit result.

Partly tested

Philips Google TV TA6 LT

@fabricio00101

Manual ADB session (repo scripts not run): 4 packages disabled, dumbtv home installed as HOME replacing Google TV launcher; verify.sh targets Fire OS hosts so the full pass was not attempted.

Developer mode: Ajustes > Sistema > Acerca de de TV > pulsar 'Numero de compilacion' 7 veces; luego Ajustes > Sistema > Opciones de desarrollador > Depuracion inalambrica ON. Pair with the on-screen code: the pairing port is shown next to the code and is different from the connect port on the main screen.
IP address: Ajustes > Red e Internet > conexion Wi-Fi activa > estado de la conexion
Needed a person: Play Protect sideload rejectionFinsky answers INSTALL_FAILED_VERIFICATION_FAILURE for unknown signatures. verifier_verify_adb=0 and package_verifier_enable=0 do not reach it, and cmd role has no package-verifier role on this build. Toggle Play Protect off (Play Store > Play Protect), install, toggle it back on.
adb install streamed hangAfter a Play Protect rejection, adb install -r hangs with no output. Push the APK to /data/local/tmp and run pm install -r to get an explicit result.

Partly tested

Philips OLED705 Android TV (TPM191E, Android 12)

@tkightly

Tested on a real TV on 2026-10-20 by manual ADB. 29 packages disabled for user 0, none uninstalled: 11 third-party apps the household does not use, 9 nettvapp shortcuts, 7 Philips packages (demome, sticker, recommendation, nettvrecommender, usagelogger, candeebug, gel), tvlauncher and tvrecommendations. The TV survived two reboots, all HDMI, tuner and component inputs stayed registered, and Freeview Play, Ambilight/Hue, Alexa, Chromecast and PlayFi packages were left enabled. Private DNS set to an ad-blocking resolver. The owner then confirmed on the TV that the home screen, HDMI switching, Freeview Play, Prime Video, Ambilight/Hue, Alexa, casting and SmartTube all worked. Left enabled on purpose: com.vewd.core.browserui and com.seraphic.openinet.pre (likely the HbbTV / Freeview Play engines), org.droidtv.oad (firmware updates), org.droidtv.tv.frameworklogger.

Developer mode: Settings > All settings > Android settings > Device Preferences > About > press OK on Build seven times. Then Device Preferences > Developer options > USB debugging ON. Before that, adb connect is refused on 5555.
IP address: Settings > Network > the active connection's status
Needed a person: Allow USB debuggingAccept on the TV and tick Always allow from this computer.

Partly tested

TCL Smart TV Pro G08

@maam00

Tested on a real TV on 2026-10-17 and 2026-10-18 using manual ADB and local companion tools. The saved change log contains 21 successful disabled-user results; packages were disabled for user 0 rather than uninstalled. The owner confirmed the setup worked. The companion's 123 panel and a Netflix deep link were confirmed on the TV. The final setup retained Google TV home, Gemini and TCL Intelligent picture processing. Kernel: 5.15.180-android14-11. This is a device report, not a package-list contribution or a claim that the complete dumbtv pass was tested.

Developer mode: Settings > System > About > Android TV OS Build (below Kernel Version) > press OK seven times. Return to System > Developer options > Debugging. USB debugging was enabled, but did not initially open a network connection; enable Wireless debugging and open Pair device with pairing code.
IP address: Settings > System > Developer options > Wireless debugging. Its pairing dialog shows IP address & Port for adb pair; use the connection endpoint from Wireless debugging or ADB mDNS discovery for adb connect.
Needed a person: Wi-Fi pairing codeOpen Pair device with pairing code on the TV and use its current code and pairing port with adb pair. Then connect to the connection endpoint. The earlier Google TV remote-control pairing code cannot be reused here.
Accessibility service enabled but not boundTclAppBoot logged "callee doesn't have OP_AUTO_START permission". Grant the app's AUTO_START app-op with adb -s "$ADB_SERIAL" shell cmd appops set <package> AUTO_START allow, then rebind its accessibility service. This session toggled the service entry in enabled_accessibility_services; preserve other services when doing so. Confirm the service appears under Bound services in dumpsys accessibility. The same service was confirmed bound after a TV reboot.

Partly tested

Xiaomi Mi TV (MiTV-MSSP3, Android TV 9)

@frogu

Manual partial session: removed six owner-selected third-party apps, installed checksum-verified repository-pinned dumbtv home and SmartTube stable, and disabled stock YouTube rather than deleting it. Four analytics and feedback packages disabled for user 0. HOME resolved to dumbtv after disabling com.google.android.tvlauncher and the setup handler. After a reboot, HOME selection and all seven disabled package states persisted; Wi-Fi and ADB returned. Android Private DNS using a public resolver with the HaGeZi Normal list blocked pagead2.googlesyndication.com and googleads.g.doubleclick.net while Prime Video resolved. After reboot, the first blocked-domain check and the Prime Video check passed again. Prime Video and other owner-selected streaming apps were retained. SmartTube stable launched successfully before the beta was removed. Playback was not verified. Fire OS all.sh and verify.sh were not run; this entry does not establish a reusable package removal profile.

Developer mode: Not observed: network ADB was enabled before the session.
IP address: Not established in this session.
Needed a person: Allow USB debuggingOwner accepted the authorization dialog on the TV. Do not retry unauthorized connections in a loop.

Partly testedAndroid 9

Xiaomi Mi TV Stick (MiTV-AESP0, Android TV 9)

@pfTheTrial

Tested on a real stick on 2026-10-19 with manual ADB from Windows (Git Bash). Xiaomi has not shipped a security patch for this model since 2022-08-05. SmartTube 32.56 (dumbtv's pinned APK) installed and loaded its home feed. This is a device report, not a package-list contribution; the list in quirks is what this one household chose, not a recommendation for others.

Developer mode: Settings > Device Preferences > About > Build, press OK seven times. Back in Device Preferences, Developer options > USB debugging.
IP address: Settings > Network & Internet > select the connected Wi-Fi network
Needed a person: Allow USB debugging?Tick "Always allow from this computer" and press OK on the remote. Until then adb devices lists the stick as unauthorized.