Genymotion SaaS is transitioning to exclusively support arm64 architecture for all Android virtual devices. On March 30, 2026, the ability to create and start x86-based virtual devices will be restricted.
Why did you remove x86/x86_64 devices?
The vast majority of physical Android devices use arm64 processors. Genymotion aligns the platform with the hardware your end-users actually have by using arm64.
This move also ensures meeting Google Play's mandatory 64-bit requirement for all apps. The arm64 architecture ensures your app behaves in the virtual environment exactly as it will on users’ physical devices. This behavior helps catch bugs and supports ensuring quality.
I'm already using arm64 virtual devices but I'm encountering errors. What should I do?
If you are encountering unexpected errors with your ARM devices, you may be using one of Genymotion’s early arm64 Android OS images. The early arm64 Android OS images were tagged as “beta”.
To ensure full compatibility and benefit from the latest improvements, recreate your virtual device using a more recent arm64 OS image. The “beta” tag has been removed from all stable and recommended versions.
What happens if I don't migrate my testing to arm64 devices by the deadline?
After March 30, 2026, you will no longer be able to create or start x86 virtual devices. Your existing x86-based recipes will also fail.
Existing x86 virtual devices will transition to a read-only state for a short grace period. Existing x86 virtual devices will be fully removed after the grace period.
Genymotion strongly encourages beginning the transition of testing workflows now to avoid disruption.
Will this migration affect my pricing or subscription cost?
No. This is a technical upgrade to the platform. This upgrade will not change your current pricing or subscription plan. There will be no cost change associated with this migration.
What do I need to do to prepare?
The actions you need to take depend on how you use Genymotion.
- If you already use only arm64 virtual devices, no action is required on your side.
- If you have custom device setups, any user who has customized a virtual device by installing specific apps, adjusting device settings, or using automated recipes will need to recreate these setups on the platform’s new arm64 OS images, which are already available.
- For basic testing of apps written in Java/Kotlin, no action is required for the app itself, but you will need to start using our arm64 devices virtual devices.
- If your app uses native C/C++ code, you will need to recompile it to include the arm64-v8a architecture and use our arm64 virtual devices.