Frequently Asked Questions

View all 267 Q&As →

**talk more about Genymotion SaaS free trial** You need to request the trial after creating and validating your account. Click **Request Trial**, choose **Individual** or **Company**, then fill out and send the form. [How do I activate my free trial?](https://support.genymotion.

**“Online test”** Sí, Genymotion ofrece pruebas y automatización de tests online con **Genymotion SaaS**. También puedes usar un controlador de juegos en Android 12 o superior para probar cómo reacciona una app ante un gamepad. Detalles útiles: - **CloudBeat** centraliza la ejecución y el análisis de tests automatizados en entornos DevOps. [CloudBeat](https://genymotion.

**How to integrate using Appium Node?** Genymotion SaaS supports Appium-based automation, and there is a dedicated guide for running parallel tests with Appium on Android. See the tutorial here: [Parallel tests with Appium and Genymotion SaaS](https://www.genymotion.com/blog/tutorial/parallel-tests-appium-saas/). If you want a Node.

Example of a CircleCI pipeline to run Appium tests with Genymotion SaaS > **Objective**: Build the APK, start Genymotion Cloud devices, run Appium tests in parallel, and stop the devices. **Prerequisites** - Genymotion Cloud account (https://cloud.genymotion.

**How to use ARM-based virtual Android** Genymotion SaaS now uses arm64-only virtual devices. If your app is Java/Kotlin, switch to arm64 devices and you’re done; if it uses native C/C++, rebuild with `arm64-v8a`. See [What happened to x86/x86_64 devices in Genymotion SaaS?](https://support.genymotion.

Explore by Topic

All topics →

68 pages · 16 Q&As

Users configuring root access, webcam passthrough, firewalls, and network security settings for their virtual devices.

28 pages · 10 Q&As

Users running automated, parallel, or instrumented mobile tests using frameworks like Appium on virtual Android devices.

31 pages · 6 Q&As

Users integrating virtual devices into CI/CD pipelines using Jenkins, GitHub Actions, VDI environments, and biometric testing workflows.

223 pages · 60 Q&As

Users evaluating and deploying cloud-based or on-premise emulation infrastructure across providers like GCP using PaaS or SaaS models.

107 pages · 30 Q&As

Users getting Genymotion onto their computer: finding the right download, choosing between the VirtualBox and QEMU builds, running the installer, enabling virtualization (BIOS, VT-x, Hyper-V), and fixing installation or first-launch errors.

72 pages · 31 Q&As

Users checking whether Genymotion will run on their computer: supported operating systems and versions (Windows, macOS on Intel or Apple Silicon, Linux distributions, Chromebook), and the RAM, CPU and disk space it needs.

136 pages · 24 Q&As

Users creating, starting and managing virtual devices once Genymotion is installed: choosing a phone or tablet model, device settings and screen size, snapshots, and simulated hardware such as GPS location, battery and motion sensors.

166 pages · 12 Q&As

Users integrating the emulator with Android development tools like ADB, Android Studio, Magisk, and Xposed for app development workflows.

29 pages · 50 Q&As

Users exploring purchasing options, discounts, and deploying through cloud marketplaces like Alibaba Cloud or evaluating sales offers.

56 pages · 6 Q&As

Users operating and scripting virtual devices via command-line tools such as gmtool, gmsaas CLI, and the Genymotion Shell.

12 pages · 23 Q&As

29 pages · 36 Q&As

Users managing license keys, activation emails, EULAs, and purchasing or configuring license servers for personal or organizational use.

49 pages · 17 Q&As

Users enabling GPU acceleration, ARM64 compatibility, and hybrid graphics on Mac M-series or cloud AMI environments.

26 pages · 8 Q&As

Users managing authentication, SSO, account deletion, HTTP API access, and JavaScript SDK integration including EC2 and AAOS connectivity.

49 pages · 14 Q&As

Users choosing and deploying specific Android OS versions, including Android Automotive, for their emulation needs.