Skip to content

Basic Steps

In this section, you will find the basic steps to setup, launch, use and save a virtual device instance.

Start virtual devices

Caution

  • Closing your web browser or logging out will not stop your running virtual devices. They have to be stopped manually or they will keep running until the Frontend inactivity timeout or the maximum run duration are reached.
  • By default, no timeout happens for virtual devices started with gmsaas. You must specify the --stop-when-inactive option, or they will keep running until manually stopped.
  • Changes are not automatically saved - see save a virtual device.

From the main page

To quick-start a virtual device from the Virtual devices page, click Start button and choose the default or custom recipe you want to start from:

To see all the recipe properties, see Recipes.

Start a virtual device from a default recipe

  1. From the Default table in the Recipes page, select a recipe that matches the device you wish to emulate.
  2. Click Play

Start a virtual device from a custom (saved) recipe

From the Custom in the Recipes page, click Play next to the saved device you wish to start:

Running virtual devices are shown in the Virtual devices page.

Access a virtual device display

From the Virtual devices page, click on the desired running virtual device.

Stop a virtual device

Danger

Closing your web browser or logging out will not stop your running virtual devices. They have to be stopped manually or they will keep running until the Frontend inactivity timeout or the maximum run duration are reached.

To stop a running device, click Stop from the device display left bar menu:

You can also stop it from the Virtual devices page; click on the desired virtual device.

If you are an organization manager, you can also stop a running virtual device even if you are not its owner. You can before notify to the device owner by selecting Message owner.

Save a virtual device

Changes are not automatically saved. As a result, any modification to a virtual device has to be saved manually.

Create a new custom recipe

From a fresh virtual device (default recipe), you can save a recipe from it once your setup is done:

  1. From the virtual device display, click Save in the left bar menu
  2. Name your recipe and click CREATE

You can also do it from the Virtual devices page:

  1. Click on the desired virtual device
  2. Name your recipe and click CREATE

This will stop the running virtual device and start the recipe saving process. Your recipe will then appear as "saving" until the process is complete - this may take a few minutes.

Once finished, your saved recipes will appear in the Custom table on the Recipes page.

Update a custom recipe

To save changes of a virtual devices created from a custom recipe, click Save in the left bar menu. You can either save the changes to your current custom recipe, or create a new custom recipe:

You can also do it from the Virtual devices page:

  1. Click on the desired virtual device
  2. Save the changes: update your current custom recipe or create a new custom recipe

Your recipe will appear as saving until saving is complete. This can take a few minutes.

Deploying an application

Warning

  • Genymotion SaaS virtual devices architecture is x86 - it cannot run applications with ARM code natively. Please refer to Applications with native ARM code for more details.
  • Genymotion SaaS does not support applications for arm64/aarch64.

To deploy an application to a virtual device, you first need to create and launch a new instance or launch a saved instance. Then, use either one of the following methods:

Drag and drop

Access the virtual device display and drag and drop the application APK file into the virtual device window:

File upload widget

See Features and Emulated Sensors - File Upload.

With ADB

Connect ADB to your virtual device with gmsaas and run the following command:

adb install <application.apk>

From Google Play Store

Google Apps are not installed by default - you need to install the Open GApps package and Google Play Store will be available.

Installing Open GApps

The application you are developing or testing may require an interaction with Google Play Services (e.g.: in-app purchasing, advertising, etc.). However, for Intellectual Property reasons, Google Apps (Gmail, Drive, Calendar...) and Google Play services are not included in Genymotion virtual devices by default. You need to install the Open GApps package.

Disclaimer

GENYMOBILE SAS assumes no liability whatsoever resulting from the download, install and use of Google Play Services within your virtual devices. You are solely responsible for the use and assume all liability related thereto. Moreover, GENYMOBILE SAS disclaims any warranties of any kind, either express or implied, including, without limitation, implied warranties of merchantability, or fitness for a particular purpose regarding the compatibility of the Open GApps packages with any version of Genymotion.
In no event shall GENYMOBILE SAS or its affiliates, or their respective officers, directors, employees, or agents be liable with respect to your download or use of the Google Play Services and you release GENYMOBILE SAS from any liability related thereto. You agree to defend, indemnify and hold harmless GENYMOBILE SAS for any claims or costs related to your use or download of the Google Play Services.

  1. From your running virtual device display, click on the File upload widget and INSTALL OPEN GAPPS.
  2. Click INSTALL
  3. Wait for the package to upload and install.
  4. When done, you will be prompted to reboot the virtual device.
  5. (Optional) Open the Play Store and configure your account.

Application is not available

If an application is not available or cannot be installed from Google Play Store (Your device isn't compatible with this version), it is probably only available for ARM. See below for more details.

Applications for ARM

Genymotion SaaS virtual devices architecture is x86 (32-bit). To deploy applications for ARMv7 (32-bit), you must install an ARM translation tool which matches your virtual device Android version.

Read carefully

  • For legal reasons, we cannot distribute any ARM translation tools.
  • We cannot guarantee Genymotion SaaS (Cloud) operations after installing ARM translation tools. Do it at your own risks!
  • There are no ARM translation tools for Android 10 and above.
  • ARM translation tools cannot interpret applications with arm64/aarch64 code. For more information, please refer to this article: How to run applications for arm64/aarch64 (armv8) with Genymotion?

1. Flash the ARM translation tools

  1. Drag'n drop the ARM translation tools zip file to the device display
  2. Once flashed, reboot your virtual device

  1. Connect your instance to ADB with gmsaas
  2. Upload the ARM translation tools zip file to the device:

    adb push Genymotion-ARM-Translation_for_X.X.zip /sdcard/Download/
    
  3. Flash the tools:

    adb shell "/system/bin/flash-archive.sh /sdcard/Download/Genymotion-ARM-Translation_for_X.x.zip"
    
  4. Once complete, reboot the virtual device:

    adb reboot
    

2. Verification

You can use a third party application, such as Device Info, and verify that the available instruction sets (Supported ABIs) are x86, armeabi-v7a, armeabi:

Device Info

Alternatively, connect your instance to ADB with gmsaas and use the following ADB command:

adb shell getprop ro.product.cpu.abilist

This should return x86,armeabi-v7a,armeabi. If not, the installation has failed.

3. Install your application

Install your APK file using Drag'n drop, File upload or with adb.

Google Play Store

If you wish to install an application for ARM from Google Play Store, the ARM translation tools must be installed before the Open GApps package. Otherwise, the application will be unavailable in Play Store.

4. Save your device

Back to top