How to select an ARM-based Android Virtual Device (AVD) in Genymotion?

• Brief answer: Create or start an Android virtual device (AVD) that uses arm64 architecture. Genymotion SaaS is now arm64-only, with x86 devices restricted after March 30, 2026. When you create or run a device, choose an arm64 OS image (arm64-v8a) and ensure you’re using arm64 devices for your workflows. If you relied on x86 recipes, recreate them using arm64 OS images.

• What to do:
• In Genymotion SaaS, choose an arm64-based virtual device image when creating or starting a device.
• Use the arm64 OS images provided; if you previously used x86, recreate any custom setups or automated recipes for arm64.
• If your app uses native C/C++, recompile for arm64-v8a to ensure compatibility.
• If you’re using CI/CD or automation, ensure your pipelines start arm64 devices.

• Important deadlines: After March 30, 2026, you will not be able to create or start x86 devices, and existing x86 workflows may fail.

Sources:

• What is happening to x86 devices in Genymotion SaaS [Genymotion support article] — https://support.genymotion.com/hc/en-us/articles/30419556610333
• Genymotion SaaS is moving to arm64 (official blog) — https://genymotion.com/blog/genymotion-saas-is-moving-to-arm64
• Genymotion’s ARM64 virtual devices are now officially live! (announcement) — https://genymotion.com/blog/genymotion-arm64-devices

Follow-up: Do you currently rely on any CI/CD pipelines or specific automated recipes that you’ll need to migrate to arm64?