Development build (7fdb85b)

Development build 26 of AAE, made from the latest change on master. It's for testing, before a stable release, and is replaced by each new change.

Built from 7fdb85b: QMP and SPICE connect through a platform local socket, so the core builds for Windows

Help, About AAE, says which build you have; please include that, or a diagnostic report, when reporting a problem.

Windows

Download AAE-dev-windows-x64-setup.exe below and run it. It installs AAE for you alone, with no administrator prompt, replacing the AAE you have, and adds it to the Start menu. README.txt, in the folder AAE is installed in, explains what's needed and how it works. Check for Updates doesn't offer development builds; it offers the next stable release when there is one. In PowerShell, this fetches and runs the latest one:

irm https://github.com/aaron-gh/accessible-android-emulator/releases/download/dev/AAE-dev-windows-x64-setup.exe -OutFile ~/Downloads/AAE-dev-setup.exe; & ~/Downloads/AAE-dev-setup.exe

AAE isn't signed for Windows yet, so SmartScreen may say it protected your PC. Choose More info, then Run anyway.

Mac

Download AAE-dev.dmg below, open it, and drag AAE to Applications, replacing the AAE you have. It's version 0.6.0-dev.26. It's signed like stable releases, so AAE keeps its permissions. Check for Updates doesn't offer development builds; it offers the next stable release when there is one. The first time, macOS may say it can't check AAE: go to System Settings, Privacy & Security, and choose Open Anyway.

Android: AAE Remote

AAE Remote uses the devices on a Mac or PC running AAE from an Android phone, with their sound and vibrations on the phone. Download AAE-Remote-dev.apk below on the phone and install it; Android may ask to allow installing apps from your browser. On the computer, turn on File, Serve Devices to Phones, or run aae serve, then pair the phone with the code it shows. It needs Android 8 or later; gesture mode needs Android 11.