Important
Early development — alpha. AZUL NEX is an interface and management layer for the official Android SDK Emulator and Android Debug Bridge (ADB). It is not an Android operating system, OEM firmware package, physical-device simulator, or device-identity spoofing tool. Features listed as planned are not available yet.
AZUL NEX brings common Android Virtual Device (AVD) tasks into one Windows desktop workspace. Instead of jumping between terminal commands, it gives you a focused place to discover emulators, install official Android system images, create virtual device profiles, launch instances, and send basic controls.
Built by Azuliciado, with a dark interface, electric-blue accents, and a performance-conscious direction.
| Area | Current capability | Status |
|---|---|---|
| SDK detection | Finds common Android SDK locations and environment variables | Implemented |
| AVD library | Lists AVDs already configured in Android Emulator | Implemented |
| Device installer | Installs Android API 33–36 Google APIs x86_64 images and creates AVDs from SDK hardware profiles | Basic |
| Emulator launch | Requests launch of a selected AVD | Implemented |
| Running devices | Lists ADB-connected emulator instances | Implemented |
| Device controls | Sends Back, Home, and Recent key events | Implemented |
| APK install | Installs an APK on a selected running emulator | Implemented |
| Display presets | Shows a small set of example screen-size presets | Basic |
| Input mapping | Custom keyboard, mouse, and multi-touch mapping | Planned |
| Multi-instance tools | Clone, import, export, and organize device profiles | Planned |
The Device Installer uses official Android SDK system images and hardware definitions available in the installed SDK. Device profiles define virtual hardware configuration; they do not install Samsung, Google, Xiaomi, or other manufacturers' firmware and do not turn an AVD into a genuine physical device.
Open Device Installer in AZUL NEX, choose an available emulator hardware profile, select an Android release (API 33, 34, 35, or 36), name the virtual device, and click Install Device. AZUL NEX uses the official SDK Manager and AVD Manager to download the matching Google APIs x86_64 system image and create the AVD.
Before using the installer, open Android Studio > SDK Manager and review and accept the applicable Android SDK component licenses. AZUL NEX does not automatically accept license agreements.
Requirements:
- Android SDK installed and detected.
- Android SDK Command-line Tools (latest).
- Internet access for downloading system images.
- Applicable Android SDK component licenses accepted by the user.
- Sufficient free disk space, memory, and CPU virtualization support.
- One workspace: a clear home for Android virtual-device management.
- Useful controls: practical actions without needing to memorize every ADB command.
- Hardware-aware: sensible defaults and honest performance guidance for different PCs.
- Bilingual: English and Spanish project documentation.
- Transparent: clear separation between shipped functionality and roadmap ideas.
- Windows 10 or Windows 11, 64-bit.
- .NET 8 SDK to build from source (or the .NET 8 Desktop Runtime for framework-dependent builds).
- Android SDK Platform-Tools (ADB).
- Android Emulator.
- Android SDK Command-line Tools (latest) for the Device Installer.
- Hardware virtualization configured as required by your Android Emulator installation.
Install Android Studio or the Android SDK command-line tools. In SDK Manager, install Android Emulator, Android SDK Platform-Tools, and Android SDK Command-line Tools (latest). Review and accept the SDK component licenses there. You can create AVDs in Device Manager or use the AZUL NEX Device Installer.
```bash git clone https://github.com/Azuliciado/AZUL-NEX.git cd AZUL-NEX ```
```bash dotnet run --project src/AzulNex/AzulNex.csproj ```
If the SDK is not detected automatically, set `ANDROID_SDK_ROOT` to your Android SDK directory and restart the app.
```bash dotnet publish src/AzulNex/AzulNex.csproj -c Release -r win-x64 --self-contained true -p:PublishSingleFile=true ```
The GitHub Actions workflow also builds the Windows app and packages an installer. Check the Actions page for the latest result. A public installer should only be considered available after a successful workflow and a published release.
Android emulation can be demanding. The number of instances you can run smoothly depends on CPU virtualization support, memory, graphics drivers, emulator image, and resolution. Older or integrated-graphics systems may need a low-resolution AVD and a single running instance.
AZUL NEX does not promise a specific FPS, boot time, or number of simultaneous devices.
See the full AZUL NEX roadmap. The next priorities are:
- Verify and stabilize the Windows build and installer.
- Improve device lifecycle management and AVD configuration.
- Add live device-screen viewing and configurable input mapping.
- Add reliable multi-instance workflows and performance diagnostics.
- Expand the device preset library with clearly sourced configuration data.
- C# and .NET 8
- Windows Presentation Foundation (WPF)
- Android Emulator
- Android Debug Bridge (ADB)
- GitHub Actions for Windows CI
Ideas, bug reports, and thoughtful pull requests are welcome. Please read CONTRIBUTING.md and use the repository's issue templates.
Please review SECURITY.md before reporting a vulnerability. Do not run APKs or tools from sources you do not trust.
AZUL NEX's original repository code is distributed under the MIT License. Android SDK components and other third-party software remain subject to their respective licenses.
AZUL NEX · Crafted by Azuliciado
Built with curiosity. Designed for control.