# Philips TPM191E: device notes and additional observed unit states Checked on a Philips 50PUS8505, TP Vision TPM191E (`PH9M_EA_5599`), Android TV 12 / API 31, firmware `STT2.230526.001`. It shares the platform and firmware family of this folder's existing [`debloat.txt`](debloat.txt), but this was not a test of that full list. ## What was checked - Disabled an owner-selected subset of 13 packages from the existing list: Philips analytics, usage logging, demo and promotion/store packages; the Sticker and Fitness Buddy preloads; and Google feedback/setup-only packages. Nothing was uninstalled. - After one reboot, all 13 selected packages remained disabled. - Installed the repository launcher, then disabled the stock launcher. Home resolved to `com.gathin.tvhome/.MainActivity` after installation and was focused during the navigation checks. - The physical remote's Sources and Settings buttons continued to open Philips' internal menus. The launcher's Inputs menu reported HDMI and YPbPr, with Live TV configured as `org.droidtv.playtv`; no separate AV input was reported. This is a single-session report, not a several-day debloat test. The full `debloat.txt` was not applied to this model. Streaming-app playback, broadcast/HDMI playback, USB-drive playback, app-shortcut remapping and long-press volume repeat were not validated here. Keep the existing list's package choices commented out unless they match your own use. ## Philips 55OLED854/12: single-session notes Checked on a Philips 55OLED854/12 (OLED, Poland), same TP Vision TPM191E board and firmware as the lead unit above (`STT2.230526.001`). Details and package names are in `debloat.txt`'s "Fourth unit" note; this section covers the launcher side. - Installed the repository launcher, then disabled the stock launcher, same order as the 50PUS8505 unit. Home resolved to `com.gathin.tvhome/.MainActivity` and stayed focused there. - The Sources drawer (Inputs pill) listed USB, Network, a connected recording drive, a Switch on HDMI 1, an Xbox on HDMI 2, HDMI 3, HDMI 4 and YPbPr, each correctly named from HDMI-CEC where a device reported one. `org.droidtv.eum` was disabled briefly, then re-enabled on reading the philips-50pus8517 notes, without testing the drawer while it was off -- so this unit confirms the drawer works with `eum` enabled, not that disabling it actually breaks it here too; that part of the other board's finding was taken on trust, the same caution applied to `nettvbrowser`, `menudataapp` and `nettvregistration` (see `debloat.txt`). - The remote's Settings button stopped responding once the stock launcher was disabled, same category of issue as the TCL G09 in `docs/TROUBLESHOOTING.md`. Found with `adb shell getevent -lt` while pressing the button: this remote sends `KEY_OPTION` with no `MSC_SCAN`, so the framework reports scancode 357 directly. Mapping it with `config.xml`'s `settings_key_scancodes` and `-HomeKeyService` fixed the button, but enabling `HomeKeyService`'s key filtering broke Volume Up/Down's hold-to-repeat, the same trade-off the TCL G09 notes describe. The owner chose to keep volume repeat, so this unit ships with `key_filter` false: the Settings button does nothing, and Settings is reached from the launcher's own on-screen button instead. - `app_library` and `library_button` were used to curate Home down to the owner's chosen apps (4 dock + 4 grid) with everything else (including the Play Store's own tile and `org.droidtv.eum`'s "How-to videos" tile) moved to the Library screen instead of `hidden_apps` removing them outright. Note for anyone trying the same thing: `app_library`/`library_apps` only *add* apps that would not otherwise show (ordinary non-TV apps); they do not hide anything. Hiding an already-visible tile from the main grid still needs `hidden_apps`. - The OLED screensaver (see `debloat.txt`) showed up more than once during the session, each time after a few minutes of screenshots taken a step at a time rather than genuine idling; it is real OLED housekeeping, not something triggered by the debloat or the launcher. - A fresh reboot was done once, before the launcher install, to confirm the debloat list's persistence and run the idle-log check; the launcher, the Settings-button mapping and `com.google.android.tvrecommendations` (disabled after the launcher took Home) have not yet been through a reboot on this unit. ## Philips 65OLED804/12: notes after three days Checked on a Philips 65OLED804/12 (OLED, 2019, Germany), same board and Android 12 firmware as the lead unit (`STT2.230526.001`); it shipped with Android TV 9. Package details are in `debloat.txt`'s "Fifth unit" note; this section covers the launcher side. - The install script ran through: cold start in about 1.3 s, without the first-start timeout the 75PUS8505 list describes. With the stock launcher still enabled, Home stayed with it (its HOME filter has priority 2, as the 75PUS8505 list explains); the new launcher took Home the moment the stock one was disabled. The Home key from Live TV then landed on `com.gathin.tvhome/.MainActivity` (`mFocusedApp`). - config.xml as on the 65PUS9435: `live_tv_package` `org.droidtv.playtv`; `hidden_apps` `org.droidtv.playtv`, `org.droidtv.demome`, `org.droidtv.eum`, `org.droidtv.channels`, `com.vewd.core.browserui`. - The Inputs menu listed HDMI 1 to 4, YPbPr and Live TV, with the HDMI-CEC name of a home cinema system on HDMI 1. Sound runs over HDMI ARC to that system; single Volume Up/Down presses reach it with or without the key helper. - A held Home press did nothing with this household's slow third-party remote, until `home_long_press_home` was set and the launcher reinstalled with `-HomeKeyService`. The cause and the log lines are in `docs/TROUBLESHOOTING.md`. It was first noticed after a Blu-ray player woke the TV over HDMI-CEC and the TV came up on that input; that turned out to be a coincidence, as the same held press failed from Live TV too. - Everything above survived three restarts, one of them a cold start; the TV comes back on Live TV after power-on, as the firmware does by itself, and Home from there opens the launcher. ## Another 65OLED804/12 unit: initial state only On 25 October 2026, a separate Philips TV reported `65OLED804/12` as its Android device name. Its system properties identify the platform as TPM191E / `PH9M_EA_5599`, MediaTek MT5887, Android TV 12 / API 31, fingerprint `Philips/PH9M_EA_5599/PH9M_EA_5599:12/STT2.230526.001/4215:user/release-keys`, matching the firmware above. At observation, Home still resolved to the stock `com.google.android.tvlauncher/.MainActivity`. The Freeview/TP Vision packages noted above were disabled. `com.google.android.youtube.tvmusic` was also disabled, but its disable history was not established. No additional package had been disabled for cleanup, and the shared debloat list was not applied to this unit. This is a starting-state observation, not a debloat or launcher test. ## Philips 50PUS7354: single-session notes Checked on a Philips 50PUS7354 (LED, 2019, France, on Wi-Fi), same TP Vision TPM191E board and firmware as the lead unit (`STT2.230526.001`), with its original Philips remote. Package details are in `debloat.txt`'s "Sixth unit" note; this section covers the launcher side. One session with two restarts, not a several-day test. - `launcher/build-and-install.sh` ran through on its own: cold start in 1.7 s, and Home moved to `com.gathin.tvhome/.MainActivity` once the stock launcher was disabled (`mFocusedApp`). - The Inputs menu listed HDMI 1 / MHL, HDMI 2 to 4 (a computer on HDMI 3 by its HDMI-CEC name, marked connected), YPbPr and Live TV, with `live_tv_package` `org.droidtv.playtv`. Live TV opened from it, and Home came back opaque over the picture. - The remote's SOURCES and Settings buttons kept working with the stock launcher disabled: SOURCES opens `org.droidtv.channels`' sources drawer, the Settings button `org.droidtv.philipstvdrawer`. So this remote did not need the fourth unit's `settings_key_scancodes` 357. - The remote's Netflix and Rakuten TV buttons did nothing once Netflix was disabled (Rakuten TV is not installed on this unit). Netflix is Linux key 632 (`KEY_ONSCREEN_KEYBOARD` in `getevent -lt`); `KeyInputMgrSvc` logs `Netflix key=632` and hands it to `NetflixLaunchService`. Rakuten TV is 779 (`GlobalKeyRcv`: `key=779,scan=779`). `app_keys` `scan:632:` and `scan:779:`, installed with `HOME_KEY_SERVICE=1`, opened the chosen apps instead (checked on the real remote). - With `HomeKeyService` bound, a held Volume Up moved one step per press, as on the fourth and fifth units. `consume_volume_keys` true did not bring the ramp back here; single presses still stepped once. The owner kept the key helper. - A held Home press did nothing with the original Philips remote too, not only with the fifth unit's slow third-party remote: two holds logged `START u0 {act=android.intent.action.ALL_APPS pkg=com.android.tv.settings}` and stayed in the app. `home_long_press_home` fixed it; Home opens on release. - The firmware opens `org.droidtv.playtv` at every boot (`wm_set_resumed_activity`: FallbackHome, then PlayTvActivity). `power_on_home_always` with `HOME_KEY_SERVICE=1` brought Home up about 9 s later, and the owner confirmed a standby and power-on from the remote lands on Home as well. ## Philips 43PUS7304/12: single-session notes Checked on a Philips 43PUS7304/12 (LED, 2019, Germany, on Wi-Fi), same TP Vision TPM191E board and firmware as the lead unit (`STT2.230526.001`), with its original Philips remote. Package details are in `debloat.txt`'s "Seventh unit" note; this section covers the launcher side. One session with two restarts, not a several-day test. - `launcher/build-and-install.sh` with `HOME_KEY_SERVICE=1` ran through on its own: cold start in 1.8 s, Home moved to `com.gathin.tvhome/.MainActivity` once the stock launcher was disabled (`mFocusedApp`), and it stayed there after a restart. - config.xml as on the 50PUS7354: `live_tv_package` `org.droidtv.playtv`, `hidden_apps` `org.droidtv.playtv`, `org.droidtv.demome`, `org.droidtv.eum`; `home_long_press_home` and `power_on_home_always` true. A held Home and a power-on from the remote both land on Home; held Volume Up/Down step once per press, as on the other units. - SOURCES and the Settings button kept working on the real remote with the stock launcher disabled. - A tile for the Philips channel list: leaving `org.droidtv.channels` out of `hidden_apps` and setting `launch_actions` `org.droidtv.channels=org.droidtv.intent.action.CHANLIST`, `app_labels` `org.droidtv.channels=Favoriten` and `app_banners` `org.droidtv.channels=banner_tv` gives a tile that opens the channel list over Live TV, where the favourite lists are picked. Checked on the real remote. - The remote's Rakuten TV and Netflix buttons, read with `getevent -lt`: 779 (`030b`) and 632 (`KEY_ONSCREEN_KEYBOARD`), the same scancodes as the 50PUS7354. `app_keys` `scan:779:` and `scan:632:com.google.android.youtube.tv` opened the chosen apps from the real remote. ## Philips 65PUS8204/12: single-session notes Checked on a Philips 65PUS8204/12 (LED, 2019, UK, on Ethernet), same TP Vision TPM191E board and firmware as the lead unit (`STT2.230526.001`), with its original Philips remote. Package details are in `debloat.txt`'s "Eighth unit" note; this section covers the launcher side. One session with three restarts, not a several-day test. - The launcher was built with `tools/docker-build.sh` and installed with `SKIP_BUILD=1 launcher/build-and-install.sh`, which ran through on its own: cold start in 2.0 s, and Home moved to `com.gathin.tvhome/.MainActivity` once the stock launcher was disabled (`mFocusedApp`). - config.xml: `live_tv_package` `org.droidtv.playtv`; `hidden_apps` `org.droidtv.playtv`, `org.droidtv.eum`; `columns` 6; `home_long_press_home` and `power_on_home_always` true, installed with `HOME_KEY_SERVICE=1`. - The Inputs menu listed HDMI 1 / MHL, HDMI 2 to 4 (HDMI 3 marked connected), YPbPr and Live TV. HDMI 3 opened `org.droidtv.playtv` on the `hdmi_port=3` input (the capture is empty, as on every HDMI input), and Home came back opaque over the picture. An injected `KEYCODE_TV_INPUT` did nothing, as an injected `KEYCODE_TV` on the fifth unit; the real SOURCES button opened `org.droidtv.channels`' sources drawer. - SOURCES, the Settings button (`org.droidtv.philipstvdrawer`) and Netflix (kept installed) kept working on the real remote with the stock launcher disabled. A held Home press did nothing until `home_long_press_home`, as on the fifth to seventh units, and with `HomeKeyService` bound a held Volume Up moved one step per press. - The firmware opens `org.droidtv.playtv` at every boot (`wm_set_resumed_activity`: FallbackHome, then PlayTvActivity). With `power_on_home_always` the owner confirmed a standby and power-on from the remote lands on Home, and after a restart `mFocusedApp` was the launcher. - The remote's Rakuten TV button is 779 (`030b` in `getevent -lt`), as on the sixth and seventh units. The button with a butterfly icon is new here: it sends `02b7`, scancode 695, which `GlobalKeyRcv` logs as `key=326,scan=695` and `App Gallery: 326`, then sends `org.droidtv.ACTION.LAUNCH_APP_GALLERY`. Only `org.droidtv.nettv.market` declares that action (its MarketMainActivity), and batch 2 of `debloat.txt` disables it, so after the list the button does nothing (`cmd package query-activities -a org.droidtv.ACTION.LAUNCH_APP_GALLERY` answers "No activities found"). `app_keys` `scan:779:` and `scan:695:`, installed with `HOME_KEY_SERVICE=1`, opened the chosen apps from the real remote (Apple TV and Disney+ here; `ActivityTaskManager` logged both starts). ## Philips 65PUS7354/12: notes Checked on a Philips 65PUS7354/12 (LED, Portugal, on Ethernet), same TP Vision TPM191E board and firmware as the lead unit (`STT2.230526.001`), with its original Philips remote. Package details are in `debloat.txt`'s "Ninth unit" note; this section covers the launcher side. - `launcher/build-and-install.sh` with `HOME_KEY_SERVICE=1` ran through on its own: cold start in 1.5 s, and Home moved to `com.gathin.tvhome/.MainActivity` once the stock launcher was disabled (`mFocusedApp`). - config.xml: `live_tv_package` `org.droidtv.playtv`; `hidden_apps` `org.droidtv.playtv`, `org.droidtv.demome`, `org.droidtv.eum`; `columns` 5; `home_long_press_home` and `power_on_home_always` true. - The Inputs menu listed HDMI 1 / MHL (a sound system by its HDMI-CEC name, marked connected), HDMI 2, HDMI 3, HDMI 4 (a game console by its HDMI-CEC name), YPbPr and Live TV. - The firmware opens `org.droidtv.playtv` at every boot (`wm_set_resumed_activity`: FallbackHome, then PlayTvActivity); with `power_on_home_always` the launcher came up about 7 s later, and `mFocusedApp` was the launcher after a restart. - Checked on the real remote with the stock launcher disabled: a held Home lands on Home (`home_long_press_home`), SOURCES and the Settings button kept working, and held Volume Up/Down step once per press with `HomeKeyService` bound, as on the other units. - The remote's Netflix (632), Rakuten TV (779) and App Gallery (695) buttons, the same scancodes as the sixth to eighth units, opened the chosen apps with `app_keys` `scan:632:`, `scan:779:` and `scan:695:`.