Skip to content

Debloat any Android or Google TV over Wi-Fi and get an Apple TV-style home.

examples: focus Streamer notes on my debloat test

SWotoab7d697e8f04
diff --git a/examples/google-tv-streamer-4k-kirkwood/README.md b/examples/google-tv-streamer-4k-kirkwood/README.md
index 03cb1fc11..0072f49bb 100644
--- a/examples/google-tv-streamer-4k-kirkwood/README.md
+++ b/examples/google-tv-streamer-4k-kirkwood/README.md
@@ -1,64 +1,44 @@
# Google TV Streamer: keep Cast and stock Home enabled
-A second Google TV Streamer, device `kirkwood`, Google TV 14, SDK 34, build `UTTK.260317.003`,
-was tested from 20 through 28 October 2026. The owner reported no everyday instability during
-that period. The five-package [Cast-preserving list](debloat-keep-cast.txt) is a subset of
-[the original list](debloat.txt). It leaves Google's launcher and setup wizard enabled.
+I tested this on my Google TV Streamer, device `kirkwood`, Google TV 14, SDK 34, build
+`UTTK.260317.003`, from 20 through 28 October 2026. I had no everyday stability issues during
+that period. This five-package [Cast-preserving list](debloat-keep-cast.txt) is a subset of
+[the original list](debloat.txt). I kept Google's launcher and setup wizard enabled.
## Choose the list
-Use `debloat-keep-cast.txt` if keeping casting and firmware-update services available matters more
-than taking over Android's default HOME resolver. It disables only feedback, remote usage logging
-and advertising services. It leaves streaming apps, Assistant, ambient mode, the phone remote,
-Bluetooth, keyboard, Play Store and Play Services enabled.
+Use `debloat-keep-cast.txt` to disable feedback, remote usage logging and advertising services
+while keeping casting and firmware-update services enabled. It also leaves streaming apps,
+Assistant, ambient mode, the phone remote, Bluetooth, keyboard, Play Store and Play Services enabled.
The original `debloat.txt` documents a different Home handover, including disabling setupwraith
-and restoring Cast credentials after receiver restarts. That handover was not used for this
-second unit's observation period. Do not apply both lists if you want to keep setupwraith enabled.
+and restoring Cast credentials after receiver restarts. I did not use that handover during this
+test. Do not apply both lists if you want to keep setupwraith enabled.
Apply and undo commands are in each list's header. Only disable packages that were enabled in
-your backup. The factory-disabled recommendations stub was left unchanged and is not in this list.
+your backup. I left the factory-disabled recommendations stub unchanged; it is not in this list.
-## Home behavior on the second unit
+## Home behavior on my unit
-Disabling `com.google.android.apps.tv.launcherx` made setupwraith's `RecoveryActivity` claim HOME,
-even though `cmd package set-home-activity` reported success. The stock launcher was immediately
-re-enabled; setupwraith was never disabled. Keeping both enabled preserved Cast and the stock
+When I disabled `com.google.android.apps.tv.launcherx`, setupwraith's `RecoveryActivity` claimed
+HOME, even though `cmd package set-home-activity` reported success. I immediately re-enabled the
+stock launcher and never disabled setupwraith. Keeping both enabled preserved Cast and the stock
remote buttons without the credential enable/wait/disable ritual.
-A locally modified launcher and the existing Home accessibility helper were used for custom Home,
-boot and standby-wake behavior. Those local launcher changes are outside this contribution and
-are not needed for the five-package list. This list alone leaves Google TV as default Home; it
-does not promise automatic custom-launcher startup with the unmodified reference launcher.
+I used a locally modified launcher and the existing Home accessibility helper for custom Home,
+boot and standby-wake behavior. Those launcher changes are outside this contribution and are
+not needed for the five-package list. This list alone leaves Google TV as default Home; it does
+not configure automatic custom-launcher startup with the unmodified reference launcher.
-## Verification and limits
+## Verification
-Packages and their activities/services were inspected before disabling. Changes were applied in
-small batches, one package command per shell call, with real-device screenshots and navigation
-checks. The owner tested physical Home, Netflix, YouTube, Settings/dashboard and Input buttons,
+I inspected the packages and their activities/services before disabling them. I applied changes
+in small batches, one package command per shell call, and checked screenshots and navigation on
+the device. I tested the physical Home, Netflix, YouTube, Settings/dashboard and Input buttons,
and phone-to-TV YouTube casting after reboot. All worked.
-On 28 October, device readbacks showed the same boot ID as 21 October, all five packages still
-disabled, the Cast receiver and both stock Home packages enabled, and the Home helper bound with
-no crashed services. A pulled screenshot showed the custom launcher. Its historical process exits
-contained only the earlier package updates and deliberate force-stops, with no later crash or ANR
-exit recorded. This supports the reported several-day result, not a guarantee for other units.
-
-## Bluetooth speaker announcements during standby
-
-Before the observation period, a paired Echo announced the TV connection at night even though the
-display stayed off. At 04:44 on 21 October, the retained logs showed the Cast receiver exiting itself
-with status 0, restarting, creating an audio track and activating the speaker's A2DP stream. No
-interactive power wake was recorded at that time. Similar nightly Cast self-exits predated this test.
-
-The speaker's Bluetooth audio link was disconnected without disabling Bluetooth or Cast. The owner
-reported no further overnight announcements. On 28 October, retained Bluetooth state-machine history
-still ended with that speaker's disconnection on 21 October, and Bluetooth reported zero crashes.
-Cast's exit history continued to show nightly status-0 self-exits on 22-28 October.
-
-That supports a background Cast/audio-link explanation for this unit. It does not identify why
-Cast restarts or prove how the speaker decides to announce a connection. Disconnecting the audio
-link is an observed workaround, not an automatic reconnect solution. No automation is included.
-
-Only these summarized observations are shared here. Raw logs, backups, screenshots with personal
-details and device identifiers remain private.
+On 28 October, I checked that all five packages were still disabled, the Cast receiver and both
+stock Home packages were enabled, and the Home helper was bound with no crashed services.
+The device had the same boot ID as 21 October. A screenshot showed the custom launcher, and its
+process-exit history contained only my earlier package updates and deliberate force-stops, with
+no later crash or ANR exit recorded.
diff --git a/examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt b/examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt
index 442974830..bbe47221d 100644
--- a/examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt
+++ b/examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt
@@ -1,5 +1,5 @@
# Google TV Streamer (device kirkwood), Google TV 14 (SDK 34), build UTTK.260317.003, 4 GB RAM
-# Second unit: tested 20-28 October 2026. Five-package subset with stock Home and Cast kept enabled.
+# Tested on my unit 20-28 October 2026. Five-package subset with stock Home and Cast kept enabled.
# Apply: TV_HOST=<ip> tools/disable.sh examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt
# Undo: TV_HOST=<ip> tools/restore.sh examples/google-tv-streamer-4k-kirkwood/debloat-keep-cast.txt com.google.android.apps.tv.launcherx
# Disable only. Back up first; comment out packages you want to keep.
@@ -15,6 +15,6 @@ com.google.android.feedback
com.android.tv.feedbackconsent
com.google.android.tv.remotecontrol.logging # remote usage logging, not the phone remote service
-# Privacy Sandbox advertising services; activities and services inspected before disabling
+# Privacy Sandbox advertising services; I inspected activities and services before disabling
com.google.android.adservices.api
com.google.android.ext.adservices.api