Serious Discussion Debloated a Xiaomi phone with UADNG

@Bot, I debloated a Mi TV using UADNG's recommended, advanced, and unlisted sections. The TV now has only the following apps: Projectivity Launcher, Stremio, SmartTube, VLC, Aves Gallery, LocalSend, Fluffy File Manager, Button Mapper, and TV Bro. The Projectivity Launcher properly overrides the default (Google TV) launcher; the home button on the remote also opens Projectivity Launcher. Remapped remote buttons also work well; I remapped PatchWall with Stremio and YouTube with SmartTube.

I plan to test the Flicky F-Droid client and the Bluetooth Remote smartphone app.
 
  • Like
Reactions: oldschool
@Bot, I debloated a Mi TV using UADNG's recommended, advanced, and unlisted sections. The TV now has only the following apps: Projectivity Launcher, Stremio, SmartTube, VLC, Aves Gallery, LocalSend, Fluffy File Manager, Button Mapper, and TV Bro. The Projectivity Launcher properly overrides the default (Google TV) launcher; the home button on the remote also opens Projectivity Launcher. Remapped remote buttons also work well; I remapped PatchWall with Stremio and YouTube with SmartTube.

I plan to test the Flicky F-Droid client and the Bluetooth Remote smartphone app.
Your Mi TV setup sounds functional and very lean, but I would be careful with calling it fully “safe” until it has been tested for a while in normal daily use.

What looks good

Your current app set is small and purpose-driven:

  • Projectivity Launcher for a cleaner home screen
  • Stremio and SmartTube for media use
  • VLC for local playback
  • Aves Gallery and LocalSend for local media/files
  • Fluffy File Manager and TV Bro for utility access
  • Button Mapper for remote customization

If the launcher override works correctly and the home button reliably returns to Projectivity, that is a very good sign. The same applies to your remapped PatchWall and YouTube buttons.

What I would test before treating it as “done”

On Android/Google TV devices, aggressive debloating can leave delayed issues rather than immediate ones. The main things worth checking are:

  • cold boot and reboot behavior
  • waking from sleep/standby
  • Wi-Fi reconnect after reboot and after long idle periods
  • Bluetooth pairing retention, if you use accessories
  • HDMI-CEC behavior with the TV remote and external devices
  • audio output switching
  • playback of local files and network streams
  • whether Projectivity still survives updates or restarts as default launcher
  • whether Button Mapper remaps still persist after reboot

About removing too much on a TV

TV debloating is often less forgiving than phone debloating because some packages affect:

  • remote input handling
  • voice search integration
  • Chromecast / Google Cast
  • Play Store updates
  • DRM-dependent streaming apps
  • system overlays and setup components

I cannot verify from your post which exact packages were disabled, so I would avoid assuming all advanced and unlisted removals are harmless on every Mi TV firmware build.

About the apps you plan to test

Flicky
An F-Droid client can be useful on a TV, but as with any third-party app store client, the main considerations are update reliability and source trust. It is worth checking the project page and release notes directly rather than relying on summaries.

Bluetooth Remote
A phone-as-remote app can be very handy, especially if physical remote mapping becomes inconvenient. The main things to verify are connection stability, permission requests, and whether it keeps working after the TV sleeps or reboots.

Practical advice

Since the TV is already working well, the safest approach is:

  • leave the current setup as-is for a few days of normal use
  • test one new utility at a time
  • avoid removing more packages unless a specific problem or unnecessary service is identified
  • keep notes of any package changes so you can reverse them if something breaks later

Bottom line

Your Mi TV debloat result sounds successful so far, especially since the launcher override and button remaps are working properly. The main remaining risk is not immediate breakage, but delayed issues with standby, updates, casting, or system integrations, so a short period of real-world testing is the best next step.
 
  • Like
Reactions: rashmi

You may also like...