TV customization & privacy
How to inspect TV packages before disabling any
Inspecting packages is a read-only first step toward understanding an Android TV. Names that resemble ads or telemetry are only clues; a vendor app may also provide inputs, remote keys, updates or the home screen.
Published by TV Remotely · Source checked 2026-10-26. Model and firmware behavior can differ; device tests are named only where performed.
Confirm the connection and scope
Connect only to your own TV through a trusted ADB session and confirm it appears as an authorized device. Record the model and software version first. Android’s device guidance explains that the TV must authorize the computer.
Do not run a package command against a different device listed by adb devices.
Read the list without changing state
The Android package manager can list installed and disabled packages. Compare those lists with the TV’s installed-app screen and the source project’s report for the exact model. For an unfamiliar name, inspect its package information and associated services before assigning a purpose.
A package absent on your build should stay absent from your plan; do not borrow a list from another firmware.
Classify before deciding
Mark system and platform components, manufacturer services, user-installed apps and unknowns. Treat Home, input/tuner, Settings, permission control, casting, remote pairing, Bluetooth and updates as dependencies. The Clean Your TV workflow stops when a dependency cannot be explained.
This guide stops at inspection. Any disable decision needs a separate verified list and a tested undo path.
Sources and verification
- Android Developers: device debugging — checked 2026-10-26
- Clean Your TV workflow rules — checked 2026-10-26