What is happening to x86 devices in Genymotion SaaS
Overview
Genymotion SaaS is transitioning to exclusively support arm64 architecture for all Android virtual devices.
arm64 architecture is a 64-bit version of the ARM architecture.
On March 30, 2026, the ability to create and start x86-based virtual devices will be restricted.
Why are you removing x86 devices?
The vast majority of physical Android devices today use arm64 processors.
Genymotion SaaS aligns the platform with the hardware end-users actually have to provide the most accurate and reliable testing environment.
This move also helps meet Google Play's mandatory 64-bit requirement for all apps.
The arm64 architecture ensures applications behave in Genymotion SaaS exactly as they will on end-user devices.
Alignment with end-user device behavior is critical for catching bugs and ensuring quality.
Will my tests run slower on arm64 virtual devices?
Arm64 virtual devices offer significant performance advantages.
Users will experience faster booting and saving times for virtual devices thanks to the new ARM servers.
What do I need to do to prepare?
The actions to take depend on how Genymotion is used.
- If only arm64 virtual devices are used, no action is required.
- If a user has custom device setups, a customized virtual device created by installing specific apps, adjusting settings, or using automated recipes must be recreated on the new arm64 OS images.
- For basic testing of apps written in Java/Kotlin, no action is required for the app itself.
- Testing must start using arm64 devices for basic testing.
- If an app uses native C/C++ code, recompile it to include the arm64-v8a architecture and use arm64 virtual devices.
ARM64 device errors and remediation
If unexpected errors occur with ARM devices, early arm64 Android OS images tagged as 'beta' may be in use.
To ensure full compatibility and benefit from the latest improvements, recreate the 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 be transitioned to a read-only state for a short grace period before being fully removed.
We strongly encourage you to begin transitioning your testing workflows now to avoid disruption.
Will this migration affect pricing or subscription cost?
No. This is a technical upgrade to our platform, and it will not change your current pricing or subscription plan.
There will be no cost change associated with this migration.