Overview
Android 16 beta is officially available on Genymotion Desktop. Genymotion announces Android 16 is ready for local testing on Windows, macOS (Intel & Apple Silicon), and Linux. The release follows the successful introduction of Android 16 for Genymotion Cloud. Genymotion Desktop offers the same stability, performance, and feature set for local users. Developers can start in the Cloud or debug on Desktop.
Start in the Cloud
Run massive parallel tests on Genymotion SaaS platform to catch regressions early.
Debug on Desktop
When a tricky bug is found, 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.
- Update Genymotion Desktop to the latest version.
- Check for updates in the status bar.
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.
- If Android 16 does not appear in the drop-down list, click the button to display more options.
5. Follow the install wizard according to your need.
6. Click on Install.
Note on Stability (Beta)
Genymotion wants to get this version into your hands as quickly as possible so developers can start preparing their apps. As such, this initial release of Android 16 for Desktop is currently in Beta. Genymotion has tested the release extensively and considers it reliable for the vast majority of development and testing workflows. However, bleeding-edge releases may include edge cases to keep in mind.
Known Issues
- On-Screen Keyboard Trigger: Currently, the on-screen keyboard toggle button may not automatically appear when a text input field is focused.
- Workaround: If the soft keyboard is required, 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, disable quick boot in your device configuration.
Happy emulating!