Universal-Debloater-Alliance/universal-android-debloater-next-generation

What it does

UAD-ng is a cross-platform desktop GUI written in Rust that talks to a connected Android phone over ADB and removes or disables preinstalled system apps. It is a detached fork of the older UAD project, redesigned for better privacy and efficiency by cutting unnecessary and obscure packages. The practical goals are less background activity (energy, speed, memory) and a smaller attack surface. It targets non-rooted devices, so it works on stock OEM ROMs where vendors preinstall social, shopping and duplicate apps.

The repository is the application itself, not a list-only project: the binary is the UI, and the package recommendations come from the bundled uad_lists.json.

Getting started

1. On the phone, enable Developer options and USB debugging, then connect it to the computer with a USB cable and authorize the debugging prompt.
2. Install the adb platform tools on the computer so the GUI can reach the device.
3. Get UAD-ng: download a release build, or compile from source following the building guide.
4. Start the GUI, confirm the device is detected, and browse the package list. Debloat actions are applied per package; review each suggested package and its note before acting.

The maintainers' getting started and usage wiki pages cover device setup and the interface in detail.

Constraints

• Requires a working ADB connection; the phone stays non-rooted, but USB debugging must be enabled and the computer authorized on the device.
• The README opens with a clear warning that use is at the user's own risk. Removing the wrong system package can break device functions, so the recommendation notes in the list are part of the workflow, not optional metadata.
• The app collects and transmits no user data; the only outbound requests are GETs to GitHub for the package list and update checks — a networking detail that matters on restricted networks.
• On newer Android releases, ADB uninstall of system apps may fail, as reported for Android 17 in the 2026 discussion; this is a platform/ADB limitation rather than a UI bug.
• Licensed GPL-3.0.

Related work

The Universal Debloat List has been reused by other tools: Canta debloats from the phone itself via Shizuku, AppManager and android-debloat-list build on the same data, and De-Bloater uses Magisk. These are alternatives for users who cannot or do not want to use a PC.

HotRepo's take

The project's strongest evidence of real use is a long-running Hacker News presence: the 2024 debloating thread drew 303 points and 222 comments, where users described heavy OEM preinstalls on retail Samsung phones and one commenter pointed readers to this maintained fork over the original UAD (comment). A second 2026 thread with 231 points discusses ADB uninstall failing on Android 17, which is exactly the kind of platform change that constrains this tool's core operation. In HotRepo's Rust daily snapshot for 2026-11-09 the repository recorded 9,854 stars and 33 new stars that day, ranking 6th on that language list — a single snapshot, useful as a dated fact rather than a trend. The 2026 thread is also a reminder that debloating depends on Android's ADB behavior, so check current platform reports before mass-removing packages.