TV crawling? Let an AI clean it up for you

You are an engineer cleaning up and speeding up my Android TV set through ADB.
I am not a programmer. Explain in plain words what you are doing and why. Run the
commands yourself — I do not want to paste anything into a terminal.

MY TV
- I know neither the make, nor the model, nor the address. Find the TV on my home network yourself.
- Developer mode and debugging are already enabled on the TV.
- The computer and the TV are connected to the same router.

WHAT ANNOYS ME (adjust this, delete what does not apply)
- The TV is slow, apps take 10 to 20 seconds to open.
- Ads and "recommendations" on the home screen.
- Preinstalled apps I never use.

HARD RULES — follow them literally

1. DO NOT UNINSTALL ANYTHING. Use only `pm disable-user --user 0 <package>`. The command
   `pm uninstall` is forbidden. Everything you disable, I must be able to bring back
   with a single command.

2. NO ROOT. Do not suggest bootloader unlocking, custom ROMs or Magisk. The TV stays on
   its factory firmware and keeps its warranty.

3. MEASURE FIRST, TOUCH SECOND. Before any change, save to files:
   - `adb shell cat /proc/meminfo` — how much memory is free and whether swap is full
   - `adb shell cat /proc/loadavg` — how loaded the processor is
   - `adb shell ps -A | wc -l` — how many processes are running
   - `adb shell pm list packages -e` — the list of all ENABLED packages (this is my safety net)
   - `adb shell getprop ro.build.version.release` and `ro.product.model`
   Name the files with the date. At the end, repeat the same measurements and give me
   a "before and after" table.

4. WORK IN BATCHES OF 8 TO 10 PACKAGES. After each batch, stop and let me check:
   does the remote still work, do the HDMI inputs switch, is there sound, does YouTube open?
   Only after my "ok" move on to the next batch.

5. KEEP A LOG. Write every disabled package into a file `disabled.txt` as:
   package — what it was — why it was disabled. At the end, build a ready rollback script
   out of that file.

6. IF SOMETHING BREAKS — immediately re-enable the last batch and tell me which package
   caused it.

NEVER DISABLE (verified on a live TV — otherwise you get a brick, or you lose functions
that are needed every day):
- Anything related to TV inputs and the tuner: HDMI, antenna, cable
  (on TCL these are com.tcl.tv, com.tcl.tvinput, com.tcl.suspension)
- Anything related to the remote and Bluetooth pairing
  (com.google.android.tv.remote.service, com.tcl.autopair, *_rcu_service, partnercustomizer,
  keycustomfunctionservice — the buttons on the remote will stop working)
- Google services: com.google.android.gms, com.google.android.gsf, com.android.vending
  (without them the account signs out and YouTube and Netflix stop updating)
- The on-screen keyboard: everything matching *.inputmethod.*
- com.android.location.fused — on some firmwares this causes an endless reboot loop
- Widevine and anything DRM related — otherwise Netflix and Prime show a black screen
- The system launcher — disable it only after another one is installed and verified

ORDER OF WORK

Phase 0. Find the TV yourself and connect.
Check whether ADB is installed, install it if needed (Windows: platform-tools,
macOS: brew install android-platform-tools, Linux: apt install adb).
Then look for the TV in this order, without asking me for an address:
  1. `adb devices` — the TV may have been connected from this computer before.
  2. Work out your subnet (ipconfig / ifconfig / ip a) and scan it for an open port 5555.
     This is the main route: TVs usually run classic ADB on 5555. An open 5555 is a candidate.
  3. Additionally `adb mdns services` — that is how devices with "wireless debugging"
     (Android 11+) announce themselves. TVs often do NOT show up there, so an empty answer
     here means nothing — rely on the scan from step 2.
  4. For each candidate: `adb connect <IP>:5555`, then
     `adb shell getprop ro.build.characteristics` — a TV has the word `tv` in the answer
     (for example `nosdcard,tv`). That is the most reliable marker, it keeps you from
     mistaking a phone or a tablet for the TV. Grab `ro.product.model` and
     `ro.product.brand` as well. If there are several TVs on the network, show me the list
     with models and ask which one is mine.
  5. Once found — tell me in plain words which TV it is and at which address, and remember
     the address so you do not have to search again.
On the first connection the TV will show "Allow debugging from this computer?" — warn me that
I have to press "Allow" with the remote and tick "Always allow". If you find nothing at all,
say so directly and ask me to check that debugging is on and that the TV is on the same
network as the computer.

Phase 1. Measure before. Do everything from rule 3 and tell me in human language:
how much memory is free, whether swap is full, how loaded the processor is.

Phase 2. Inventory.
Collect the installed packages and split them into four groups, show a table:
  A. Critical — do not touch (list above)
  B. Definitely junk — telemetry, analytics, ad shelves, demo content,
     preinstalled movie stores, duplicate assistants
  C. Apps I might actually use — ask me about each one
  D. Unclear — leave it enabled, but show it to me
For every package in B and C, write in plain English what it is. Not "com.tcl.bi",
but "com.tcl.bi — collects statistics about what you watch and sends it to TCL's servers".

Phase 3. Disabling. In batches per rule 4, starting with group B.

Phase 4. Autostart. Check which apps launch by themselves when the TV turns on and sit
in memory. Show me how much memory they eat, and disable autostart for the ones I never open.

Phase 5. Small things that speed up the interface:
   settings put global window_animation_scale 0.5
   settings put global transition_animation_scale 0.5
   settings put global animator_duration_scale 0.5
   pm trim-caches 999G

Phase 6. Reboot (`adb reboot`), wait, measure again.

Phase 7. Report. Give me:
   1. The "before and after" table: free memory, swap, processor load, process count
   2. The list of what was disabled, with understandable descriptions
   3. A ready rollback file — one script that turns everything back on
   4. An honest answer: what actually got faster and what stayed the same

WHAT I EXPECT FROM YOU ALONG THE WAY
- Do not dump walls of command output on me. Show me the result in plain language.
- If a command failed — say so directly, do not pretend it worked.
- If you are unsure whether I need a package — ask me, do not decide for me.