In this section, you will find all the available methods to deploy an application.
> More and more apps are only available for arm64. We strongly recommend using arm64 images, rather than x86_64, for best compatibility.
With an APK File
To deploy an application from an APK file to a virtual device, you can use one of the following methods:
- Drag'n Drop
- File upload
- Command Line (ADB)
Drag and Drop the .apk file to the virtual device display. This will install and open the applications automatically:
- Open the File upload widget
- Click BROWSE and select the APK file to deploy
- Click OK
- This will install and open the application automatically.
Connect the instance to ADB and run this command:
- adb install <application name>.apk
Warning
- If you don't use a universal APK, make sure it matches your instance image architecture:
- x86 or x86_64 for x86_64 images.
- arm (ARMv7) or arm64 (ARMv8) for arm64 images.
From Google Play Store (Open GApps)
The application you are developing or testing may require an interaction with Google Play Services (e.g.: in-app purchasing, advertising, etc.). If you really need them, you can use the packages provided by Open GApps.
Device content
- Version: 13.0.0
It is now possible to install the Open GApps package using the device content feature:
- Go to the Device content panel:
- In the Packages section, click next to the Open GApps package:
- The Open Gapps package will be automatically downloaded and installed. Reboot the instance when prompted.
Open Google Play Store:
- Google Play Store in Android App Drawer
- Version: 8.0.0
From your device display, open the File upload widget
- Click INSTALL OPEN GAPPS
- Click INSTALL
After the package is installed, reboot your instance.
Once done, you may have to wait a couple of minutes for the Google Apps to update themselves before opening them.
(optional) Open Play Store and .
Most modern Android apps are only available for arm64 now. Make sure to use an arm64 image or you may not be able to install many apps from Google Play Store. See Application for ARM/ARM64.
Applications for ARM/ARM64
More and more Android apps are only available for arm64 now, in accordance with Google requirements. If you use a x86_64 image, you will likely not be able to install many modern apps.
We therefore strongly recommend using one of our arm64 AMIs for best compatibility.
ARM translation tools for x86_64 images (unsupported)
x86_64 images are now considered obsolete. The following information has been left for legacy purposes. Please consider using arm64 images instead.
- The ARM translation tool must match your virtual device Android version.
- Using ARM translation tools alters the Virtual Device system: we cannot guarantee Genymotion stability nor provide any technical support if you use them. We highly recommend using arm64 images instead. DO IT AT YOUR OWN RISK!
- We do not distribute any ARM translation tools.
Web UI
Command Line
- Drag'n drop the ARM translation tools zip file to the device display, or use the File upload widget.
Once flashed, reboot the instance using the Power Off and Reboot feature:
To verify whether the ARM translation tools are properly install, you can use a third party app, such as Device Info, and verify that the available instruction sets (supported ABIs) are
- x86_64, x86, armeabi-v7a, armeabi
- ADB
- SSH
- Connect your instance to ADB and upload the ARM translation tools:
- adb push Genymotion-ARM-Translation_for_X.X.zip /sdcard/Download/
- Flash the ARM translation tools:
- adb shell "/system/bin/flash-archive.sh /sdcard/Download/Genymotion-ARM-Translation_for_X.X.zip"
- When flashing is complete, reboot the instance:
- adb reboot
- Verify the ARM tools installation:
- adb shell getprop ro.product.cpu.abilist
- x86_64,x86,armeabi-v7a,armeabi
- Configure SSH and upload the ARM translation tools to the instance:
- scp -i key.pem Genymotion-ARM-Translation_for_X.X.zip shell@{your_instance_ip}:/sdcard/Download/
- Flash the ARM translation tools
- ssh -i key.pem shell@{your_instance_ip} su -c "/system/bin/flash-archive.sh /sdcard/Download/Genymotion-ARM-Translation_for_X.X.zip"
- When flashing is complete, reboot the instance:
- ssh -i key.pem shell@{your_instance_ip} reboot
- Verify the ARM tools installation:
- ssh -i key.pem shell@{your_instance_ip} getprop ro.product.cpu.abilist
- x86_64,x86,armeabi-v7a,armeabi
Applications for ARM/ARM64 (continued)
More and more Android apps are only available for arm64 now, in accordance with Google requirements. If you use an x86_64 image, you will likely not be able to install many modern apps.
We therefore strongly recommend using one of our arm64 AMIs for best compatibility.
ARM translation tools for x86_64 images (unsupported)
x86_64 images are now considered obsolete. The following information has been left for legacy purposes. Please consider using arm64 images instead.
- The ARM translation tool must match your virtual device Android version.
- Using ARM translation tools alters the Virtual Device system: we cannot guarantee Genymotion stability nor provide any technical support if you use them. We highly recommend using arm64 images instead. DO IT AT YOUR OWN RISK!
- We do not distribute any ARM translation tools.
Web UI
Command Line
Drag'n drop the ARM translation tools zip file to the device display, or use the File upload widget.
Once flashed, reboot the instance using the Power Off and Reboot feature.
To verify whether the ARM translation tools are properly install, you can use a third party app, such as Device Info, and verify that the available instruction sets (supported ABIs) are x86_64, x86, armeabi-v7a, armeabi
- adb shell getprop ro.product.cpu.abilist
- x86_64,x86,armeabi-v7a,armeabi
[End of page excerpt]