Experience Android 16 directly on your local machine
We are thrilled to announce that Android 16 beta is officially available on Genymotion Desktop! Following our successful release of Android 16 for Genymotion Cloud , we have been working hard to bring the same stability, performance, and feature set to our local users. Whether you are on Windows , macOS (Intel & Apple Silicon), or Linux , you can now build, test, and explore the latest Android OS directly from your workstation.
Many of you have already been testing Android 16 using our Genymotion SaaS Cloud . We know that flexibility is key to your workflow. Now you can both: Start in the Cloud: Run massive parallel tests on our SaaS platform to catch regressions early. Debug on Desktop: When you find a tricky bug, pull the same Android 16 environment up on Genymotion Desktop to use local debugging tools to fix it fast.
How to Get Started
Getting your hands on Android 16 is simple: 1. Update Genymotion Desktop if necessary: Ensure you are running the latest version of the Genymotion Desktop application (check for updates in the status bar download it here ). 2. Create a New Device: Click the (+ Create) button to add a new virtual device. 3. Select your desired Hardware Profile 4. Select Android 16 (click on button if it does not appear in the drop-down list) 5. Follow the install wizard according to your need 6. Click on Install Android 16 powered by Genymotion Desktop
Note on Stability (Beta)
We want to get this version into your hands as quickly as possible so you can start preparing your apps. As such, this initial release of Android 16 for Desktop is currently in Beta.
Rest assured we have tested it extensively, and it is reliable enough for the vast majority of development and testing workflows . However, as with any bleeding-edge release, there are a few edge cases to keep in mind.
Known Issues
- On-Screen Keyboard Trigger: Currently, the on-screen keyboard toggle button may not automatically appear when you click into a text input field. Workaround: If you require the soft keyboard, simply go to
your device configuration
and manually enable the
“Use virtual keyboard for text input”
option. This ensures the keyboard appears whenever you need it.
- Quick Boot Consistency: In specific circumstances, the Quick Boot feature may fail to initialize properly, resulting in a crash of the emulator or the last Android app. Workaround: if you encounter this issue with your workflow, just disable quick boot in
your device configuration
.
Happy emulating!
Prev Previous Genymotion SaaS is moving to arm64