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 are you removing x86 devices?
The vast majority of physical Android devices today use arm64 processors.
Genymotion SaaS is aligning the platform with the hardware end-users actually have.
This move ensures testing uses an accurate and reliable testing environment.
This move also helps users meet Google Play's mandatory 64-bit requirement for all apps.
The arm64 architecture ensures apps behave in the virtual environment exactly as they will on users' physical devices.
This behavior is critical for catching bugs.
This behavior is also critical for ensuring quality.
Will my tests run slower on arm64 virtual devices?
arm64 virtual devices offer significant performance advantages.
ARM servers are enabling faster booting for arm64 virtual devices.
ARM servers are enabling faster saving times for virtual devices.
What do I need to do to prepare?
The actions needed to take depend on how users use Genymotion.
- If users already use only arm64 virtual devices, no action is required on their side.
- If users have custom device setups, users need to recreate these setups on new arm64 OS images.
- arm64 OS images are already available.
- If users are doing basic testing of apps written in Java/Kotlin, no action is required for the app itself.
- If users do basic testing of apps written in Java/Kotlin, users need to start using arm64 devices virtuals devices.
- If users use native C/C++ code, users need to recompile it to include the arm64-v8a architecture.
- If users use native C/C++ code, users need to use arm64 virtual devices.
I'm already using arm64 virtual devices but I'm encountering errors. What should I do?
Unexpected errors with ARM devices can happen when users are using early arm64 Android OS images.
Early arm64 Android OS images were tagged as "beta".
To ensure full compatibility and benefit from the latest improvements, users need to 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, users will no longer be able to create or start x86 virtual devices.
Users' existing x86-based recipes will also fail.
Existing x86 virtual devices will be transitioned to a read-only state for a short grace period.
Existing x86 virtual devices will be fully removed after the read-only grace period.
Genymotion SaaS strongly encourages users to begin transitioning testing workflows now to avoid disruption.
Will this migration affect my pricing or subscription cost?
This migration is a technical upgrade to the platform.
This migration will not change current pricing.
This migration will not change the subscription plan.
There will be no cost change associated with this migration.
Related articles
- How to run applications and games for arm (arm64)?
- Genymotion Desktop and Hyper-V (Windows)
- I can't install or run an application/game in Genymotion Desktop
- How to enable kiosk mode with Genymotion SaaS (Cloud)?
- How to use Android Studio, Eclipse, VS Code, JetBrains Rider or any other IDE with Genymotion SaaS?