What is happening to x86 devices in Genymotion SaaS?

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.
• To provide the most accurate and reliable testing environment possible, we are aligning our platform with the hardware your end-users actually have.
• This move also ensures you can meet Google Play's mandatory 64-bit requirement for all apps.
• The arm64 architecture ensures your app behaves in our virtual environment exactly as it will on your users' physical devices, which is critical for catching bugs and ensuring quality.

Will my tests run slower on arm64 virtual devices?

• On the contrary, our arm64 virtual devices offer significant performance advantages.
• Thanks to our new ARM servers, you will experience faster booting and saving times for your virtual devices.

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 settings, or using automated recipes will need to recreate these setups on our new arm64 OS images, which are already available.
• For basic testing of apps written in Java/Kotlin: No action is required for your app itself, but you will need to start using our arm64 devices virtuals 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.

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 our early arm64 Android OS images, which were tagged as "beta". To ensure full compatibility and benefit from the latest improvements, please 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 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 any disruption.

Will this migration affect my 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.