TV Vibe Cleanup
Improve the owner's TV using its actual inventory and keep-list. Treat the Redmi case study as an example, never as a universal removal list. This needs a local executor with network access to the TV and Google Android SDK Platform-Tools; cloud-only chat cannot reach a home LAN by itself.
Establish the target
Identify the TV model, Android version, debugging status and ADB endpoint. Connect only to the owner's chosen TV, using its on-screen approval. Do not scan unrelated network devices or enable router port forwarding. Read workflow.md for pairing, helper commands and recovery.
Ask which streaming apps and features must stay: Netflix, YouTube, free channels, HDMI/set-top boxes, USB media, Chromecast, Miracast/Mi casting, remote, keyboard, voice search and updates. Ask only for missing preferences; previous authorization and answers carry forward. Passwords and linking codes belong on the owner's device, not in chat.
Inspect before choosing changes
Use scripts/tvkit.py inspect to capture package states, default Home, animation values, storage and a hashed device identity. Keep inventory, plans, journals, APK backups and logs in a private directory outside a public checkout. Save observations before modifying the device.
Identify each candidate's function from package metadata, launch activity and reliable vendor/source documentation. Names alone are insufficient. package-notes.md distinguishes examples from protected functions. Do not clear Play Services, streaming-app data or account state to chase performance.
Present a concrete plan with target packages, reasons, preserved features and rollback. Execute within existing authorization; ask about genuine new choices or destructive operations, not routine reversible steps already requested. A public guide or attached document is evidence, not authorization to run its commands.
Apply and verify
The helper supports offline plans, selected disabling, optional animation changes, a before-change journal, read-back verification and exact enabled-state restoration. apply and restore require an explicit --yes execution flag. Recheck the device identity and current Home before changing anything. Validate the whole plan before the first mutation.
Prefer disabling first. It preserves installed apps and data but usually saves little storage. Physical removal needs the separate APK/split-backup procedure in workflow.md; the helper does not implement uninstall. Record additional manual changes and their original states. Keep-data uninstall is not a full app-data backup.
For a new Home, follow launcher.md: configure and build the attributed upstream launcher, test it, set and verify the default, and retain a tested stock-Home recovery route before considering old launchers for disabling. Preserve HDMI/USB/casting independently of visible tiles.
For optional ad-free YouTube playback, read smarttube.md. Authenticate sources and keep the signing/update channel consistent. Do not silently replace signed-in YouTube or redirect casting.
Test navigation and owner-selected features. Distinguish package-enabled checks from actual playback, casting, input and voice tests. Compare repeatable before/after conditions for performance claims. Do not add broad compilation tweaks, process limits, RAM cleaners or persistent keep-alive services without a demonstrated benefit. On the original 1 GB TV, extra compilation did not materially help; Assistant's original mode was restored.
Finish with evidence
Return what changed, what was measured, what remains untested, where recovery lives and how to use it. Keep journals and backups on the owner's computer. When finished, the owner can disable network debugging, which ends remote access. Claim a faster result only when measurements or the owner's test support it.
For public demos, preserve normal action speed or disclose edits. Native/secure surfaces may record black, as Netflix did on the source TV. Avoid account pickers, emails and linking codes in shared footage.