wtf is android-dex?

Android DEX turns an Android phone into something resembling a desktop computer, letting a person mirror apps, control the phone, stream audio, manage media, and run multiple Android apps at once from a Windows, macOS, or Linux computer, connected either over USB or Wi-Fi. It works without rooting the phone and is powered by the screen mirroring tool scrcpy, paired with wireless ADB, Android's device debugging protocol. The project ships as a desktop app built with Flutter, alongside a companion project called ADB Device Manager that handles picking and connecting to devices. Downloads are provided as ready made packages for Windows, macOS, and Linux on the project's releases page. Under the hood, Android DEX is built from three parts that must each confirm readiness before the desktop interface unlocks. The desktop side app, written in Flutter, starts an ADB connection and two small local servers, then pushes a Java program to the phone and starts it as a logic engine. Once that engine responds that it is ready, the desktop app checks whether a companion Android app is installed, installs it if missing, and starts a background service on the phone that confirms readiness over a WebSocket connection. Only once both parts confirm readiness does the full desktop interface unlock, including extended notification and media handling. Setting it up needs a computer running Windows 10 or later, macOS 11 or later, or a modern Linux distribution, plus an Android phone running Android 8.0 or later. ADB is bundled with the app, so no separate driver install is needed. The steps are to enable developer options by tapping the build number several times in phone settings, turn on USB debugging, then either plug the phone in over USB or enable wireless debugging for Wi-Fi, and launch the app, which shows a boot progress bar before unlocking the desktop view. If the connection does not succeed automatically, a button appears during startup to open the device manager and pick a device manually without restarting. The project also includes separate documentation files covering its architecture, boot flow, reconnection handling, data model, error handling, and internal modules for anyone wanting more detail.