Android Emulator for App Testing & Development
Genymobile provides Genymotion: a powerful Android emulator for PC, Mac, and Cloud environments . Trusted by leading companies including Verizon, Tinder, Meta, and IBM, Genymotion enables developers and QA teams to test Android applications at scale with virtual device simulation, GPS, battery, and network condition testing capabilities.
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.
You pay **$0.60 per hour for each instance**, plus AWS cloud platform fees. So if you run multiple instances at the same time, the cost adds up per instance, not per image. Details: - Genymotion Device Image pricing is **$0.60 / hour per instance, without cloud platform fees**. - The AWS page says **billing is the same for using 1 instance for 5 hours or 5 instances for 1 hour**.
Yes, Genymotion offers online testing and test automation with **Genymotion SaaS**. A game controller can also be used on Android 12 or later to test how an app reacts to a gamepad. - **CloudBeat** centralizes the execution and analysis of automated tests in DevOps environments. [CloudBeat](https://genymotion.
Genymotion SaaS is optimized for CI/CD, but genymotion.com's documentation only lists GitHub Actions, CircleCI, Bitrise, Jenkins, and Detox. There is no documented native GitLab CI/CD integration. It can still be used in a GitLab pipeline if the job can call the available command-line or API-based flows, but that exact setup is not documented.
Custom pricing is available, and you should contact sales at [sales@genymobile.com](mailto:sales@genymobile.com). The cloud pricing page lists **Premium** as a tailor-made plan with custom pricing and says to contact sales. It also offers annual billing and volume-oriented options on [Genymotion Android Emulator in the Cloud](https://genymotion.com/product-cloud).
Yes. Genymotion devices can be rooted dynamically, and only some Android images support it. You can use rooted images to inspect what happens on the device, while Android 14 in Genymotion SaaS is un-rooted by default: [Mobile Testing and Development](https://genymotion.com/mobile-testing-development) and [I can't install or run an application/game in Genymotion SaaS](https://support.genymotion.
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.
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.
If Genymotion Desktop is being configured, the system requirements depend on the operating system and version, such as Windows, macOS Tahoe/Sequoia, or Linux x86_64. Relevant device and virtualization settings are described in [Virtual Devices Settings](https://docs.genymotion.com/usage/desktop/vd_settings); to download Desktop, use only the [Genymotion Desktop 下载页](https://www.genymotion.
These are the most-asked questions. For all 265 Q&As with complete answers, see llms-full.txt.
Step-by-step CLI guides that AI coding assistants can execute directly in your terminal. Each runbook contains copy-paste commands for common workflows.
Users configuring root access, webcam passthrough, firewalls, and network security settings for their virtual devices.
Users running automated, parallel, or instrumented mobile tests using frameworks like Appium on virtual Android devices.
Users integrating virtual devices into CI/CD pipelines using Jenkins, GitHub Actions, VDI environments, and biometric testing workflows.
Users evaluating and deploying cloud-based or on-premise emulation infrastructure across providers like GCP using PaaS or SaaS models.
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.
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.
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.
Users integrating the emulator with Android development tools like ADB, Android Studio, Magisk, and Xposed for app development workflows.
Users exploring purchasing options, discounts, and deploying through cloud marketplaces like Alibaba Cloud or evaluating sales offers.
Users operating and scripting virtual devices via command-line tools such as gmtool, gmsaas CLI, and the Genymotion Shell.
Users managing license keys, activation emails, EULAs, and purchasing or configuring license servers for personal or organizational use.
Users enabling GPU acceleration, ARM64 compatibility, and hybrid graphics on Mac M-series or cloud AMI environments.
Users managing authentication, SSO, account deletion, HTTP API access, and JavaScript SDK integration including EC2 and AAOS connectivity.
Users choosing and deploying specific Android OS versions, including Android Automotive, for their emulation needs.