# How to Use Universal Android Debloater Next Generation on Android Emulators > Learn how to use Universal Android Debloater Next Generation on emulators. This guide explains its ADB compatibility for seamless device management and app removal. - Repository: [Universal-Debloater-Alliance/universal-android-debloater-next-generation](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation) - Tags: how-to-guide - Published: 2026-06-18 --- **Yes, Universal Android Debloater Next Generation works on Android emulators because it communicates through standard ADB, which treats emulators and physical devices identically.** Universal Android Debloater Next Generation (UAD-NG) is an open-source debloating tool maintained by the Universal-Debloater-Alliance organization. While primarily designed for physical Android devices, the tool's architecture explicitly supports emulator targets, allowing developers to clean up Android Virtual Devices (AVDs) before testing or deployment. ## How UAD-NG Detects Emulators The tool detects emulators through the same Android Debug Bridge (ADB) interface used for physical hardware. In the source code, the **`adb`** module explicitly categorizes *"Local emulators"* as a supported device type, ensuring seamless integration with emulator workflows. ### The ADB Detection Layer In [`crates/uad-core/src/adb.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-core/src/adb.rs), the `devices()` method enumerates all connected ADB targets. Lines 102-107 specifically handle USB, TCP/IP, and **local emulators**, returning them as valid device entries. This means when you run `adb devices` and see an emulator listed, UAD-NG recognizes it automatically. ### Error Handling for Missing Devices The codebase acknowledges emulator workflows in its error messaging. In [`crates/uad-core/src/sync.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-core/src/sync.rs) (lines 227-228), the application detects the ADB error string *"adb: no devices/emulators found"* and transforms it into a user-friendly message. Similarly, the GUI layer in [`crates/uad-gui/src/widgets/navigation_menu.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-gui/src/widgets/navigation_menu.rs) (line 102) displays *"No devices/emulators found"* when the device list is empty, confirming that emulators are treated as first-class targets alongside physical devices. ## Prerequisites for Debloating Emulators Before using Universal Android Debloater Next Generation on an emulator, ensure you have: - **A running Android emulator** with ADB enabled. The standard Android Studio emulator enables this by default. - **ADB installed and available on your PATH**. UAD-NG invokes the `adb` binary directly. - **UAD-NG installed** (either the GUI or CLI version). - The emulator's serial number (visible via `adb devices`) if running multiple devices. ## Step-by-Step Usage Guide ### Verify ADB Connectivity First, confirm your emulator is visible to ADB: ```bash adb devices ``` You should see output similar to: ```text List of devices attached emulator-5554 device ``` If the emulator appears here, UAD-NG can communicate with it. ### Using the CLI with Emulators The CLI entry point in [`crates/uad-cli/src/main.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-cli/src/main.rs) forwards device selection to the core library. To target a specific emulator, use the `--device` flag with the serial number: **List removable packages:** ```bash uad-cli list --device emulator-5554 ``` **Debloat a specific package:** ```bash uad-cli debloat --device emulator-5554 --package com.example.unwanted ``` ### Using the GUI with Emulators Launch the graphical interface: ```bash cargo run -p uad-gui ``` When the GUI starts, the left-hand navigation pane (implemented in [`crates/uad-gui/src/widgets/navigation_menu.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-gui/src/widgets/navigation_menu.rs)) automatically displays detected emulators by their serial numbers (e.g., *"emulator-5554"*). Selecting the emulator shows the list of installed packages, allowing you to debloat the virtual device exactly as you would a physical phone. ## Summary - Universal Android Debloater Next Generation treats emulators as standard ADB targets, supporting them through the same code path as physical devices. - The `devices()` method in [`crates/uad-core/src/adb.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-core/src/adb.rs) explicitly includes local emulators in its enumeration logic. - Both CLI and GUI interfaces support emulator workflows, with the CLI accepting `--device` flags and the GUI displaying emulators in the navigation menu. - Error handling in [`crates/uad-core/src/sync.rs`](https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/blob/main/crates/uad-core/src/sync.rs) and the UI acknowledges emulator-specific messaging, confirming first-class support. - Any emulator visible via `adb devices` can be debloated safely using UAD-NG. ## Frequently Asked Questions ### Does Universal Android Debloater Next Generation work with Android Studio emulators? Yes. UAD-NG works with any emulator that exposes itself through ADB, including the standard Android Studio emulator. As long as `adb devices` lists the emulator, UAD-NG can connect to it and remove packages. ### Can I debloat multiple emulators at once using the CLI? Yes. You can specify different emulator serial numbers using the `--device` flag for each command. Run `adb devices` to see all available emulators, then target each one individually with `uad-cli` commands using their respective serial numbers (e.g., `emulator-5554`, `emulator-5556`). ### Is there any risk in debloating an emulator compared to a physical device? The risk is identical. Debloating removes system packages permanently from that emulator instance. However, unlike physical devices, you can easily reset an emulator to factory defaults if you remove critical packages, making it a safe environment for testing package removals before applying them to physical hardware. ### Do I need root access to use UAD-NG on an emulator? No. UAD-NG uses ADB to disable or uninstall packages, which works on emulators without root access. The emulator's default security model allows ADB to perform these operations, making it easier to debloat emulators than some locked-down physical devices.