Genymotion: 2025 Year in Review
As we wrap up another incredible year at Genymotion, we’re taking a moment to look back at the milestones that defined 2025.
Genymotion Releases
The Wait is Over: Android 16 beta is Now Available for Genymotion Desktop!
The wait is over! We are happy to announce that stable, production-ready images of Android 16.0 are now available across Genymotion’s cloud-based platforms.
Genymotion SaaS is moving to arm64
Dear Genymotion users, our mission is to provide you with the most powerful and reliable platform for testing, running, and demonstrating your Android applications. To continue delivering on that promise, we are making a significant, strategic evolution to your platform. Effective March 30, 2026, Genymotion SaaS will transition to exclusively support arm64 architecture for all Android virtual devices. On this date, the ability to create and start x86-based virtual devices will be restricted. We know that any change to your workflow requires consideration, and we want to be transparent about why this move is not just necessary, but a major step forward. Note This platform upgrade is a technical evolution, not a commercial one. Your current pricing and subscription plan will not change. Aligning with the real world for high-fidelity virtual devices The simple truth is that the mobile world runs on ARM. The vast majority of physical Android smartphones and tablets your users own are powered by arm64 processors. Testing on an x86 virtual device, while once a convenient proxy, is now like testing a sedan on a racetrack built for Formula 1 ; the environments are fundamentally different. This divergence can hide bugs and performance issues that will only surface once your app is running on physical devices. By focusing exclusively on arm64, we are closing this fidelity gap. We are committing to a platform where your test results are a precise reflection of how your app will perform in the real world, giving you greater confidence with every release. Keeping you compliant and competitive Google’s direction for the Android ecosystem is clear: since 2019, Google Play has mandated that all apps with native code must provide an arm64 version. This isn’t a suggestion ; it’s a requirement for being published on the world’s largest app store. By making arm64 our standard, we are ensuring you have the compliant infrastructure you need to succeed, right out of the box! Unlocking the next generation of apps This transition is also about the future. The arm64 architecture is the key to unlocking the next wave of mobile innovation. Its 64-bit design allows to address more than 4GB of RAM, which is critical for memory-intensive applications like high-resolution games, complex data visualization tools, and the demanding workloads of on-device AI and machine learning. For those working on intensive apps and games, arm64 GPU-accelerated virtual devices are also available on request. By providing a true arm64 environment, we are giving you the platform you need to not just test today’s apps, but to build and validate the cutting-edge apps of tomorrow. What you need to do We want to make this transition as smooth as possible for you, but you may need to perform some update on your workflow before March 30, 2026. 🙋♂️ For everyone: 👨💻 For developers: For more information and answers to common questions, please consult our FAQ here. We are incredibly grateful for the trust you place in Genymotion. By focusing our efforts on the arm64 architecture, we are confident to provide a more powerful, accurate, and future-proof platform that helps you build, test and share better applications. We are committed to supporting you through this transition, feel free to reach out if you have any questions.Thank you for being part of this journey with us. The Genymotion Team
Android 16 is on Genymotion Cloud!
The wait is over! We are happy to announce that stable, production-ready images of Android 16.0 are now available across Genymotion’s cloud-based platforms.
Genymotion’s ARM64 virtual devices are now officially live!
After a successful testing phase, we are officially releasing our final, production-ready ARM64 virtual devices on Genymotion SaaS!
gmsaas 1.15.0: Now with Native arm64 Support! 🚀
gmsaas 1.15.0 has been released! It introduces native arm64 wheels for Linux distributions and Apple Silicon Macs, and many more updates and fixes.
Find your perfect fit: Genymotion SaaS has a plan for every need
Genymotion SaaS plans have been updated with more options and offers to fit everyone’s needs. Check it out now!
Android Automotive is now available in beta!
Start your engine: a new version of our Android Automotive virtual device has been released! This update includes improvements such as baseband and network features, enabling more realistic connectivity simulations for testing and development. Genymotion Cloud Car (Android Automotive OS 14.0) is already available on both AWS marketplace and Azure marketplace, each offering a free trial option. Note If you have specific feature requirements or need a tailored solution for Automotive OS, our team is ready to collaborate and deliver the perfect solution for your project — just reach out! What’s new? In addition to the existing features of our Android Automotive virtual device, this new release add baseband and network emulation. This includes: What is Android Automotive? Android Automotive (AAOS) is a specialized version of Android designed for In-Vehicle Infotainment (IVI) systems. It requires developers to follow automotive UI guidelines. Our emulator bridges the gap for developers who lack access to real vehicle hardware. It integrates a customizable Vehicle Hardware Abstraction Layer (VHAL) over gRPC protocol, allowing you to read/write vehicle properties programmatically and test your applications in a fully virtualized automotive environment. You can simulate GPS location changes and vehicle movement, making it easy to test route-based applications, navigation features, and geofencing scenarios. You can find an example below where you replay GPS traces by injecting the coordinates within the virtual device. In a real vehicle, the Vehicle HAL is communicating with various vehicle sensors and ECUs (Electronic control Units) to retrieve and expose the values of these parameters. As you may not have access to any real hardware. You can use Genymotion to dynamically adjust vehicle parameters such as speed, fuel level, and engine state to test use cases responses under various driving conditions. This is only the tip of the iceberg ! For more details and examples, please refer to our tutorial. What’s next? Head over to AWS Marketplace or Azure Marketplace to try out the latest version of Genymotion Android Automotive virtual device today! Find out more in our latest release note. If you have any specific requirements, or need a tailored solution, our team is ready to collaborate with you. Contact us to discuss how we can help and build the perfect solution for your project. Again, thank you for being part of this journey! We can’t wait to hear your feedback!
Genymotion Desktop 3.9.0 is out! 🎉
We are extremely pleased to introduce the latest release of Genymotion Desktop, packed with a ton of groundbreaking features and enhancements!
Android Automotive for Genymotion Device Image
Buckle your seat belt: our first Android Automotive device for Genymotion Device Image has just been released! You can now run virtual devices in the cloud that mirror the behaviors of vehicles embedding the Android Automotive operating system. You can already get Android Automotive OS 14.0 image on AWS marketplace with a free trial. For the moment, this is an alpha version, and more features will be added in future releases. What is Android Automotive? Android Automotive (AAOS) is a version of Android that is made specifically for vehicle IVI (In-Vehicle Infotainment) systems. You can find more information about it on the official documentation. This OS brings new challenges for Android application developers. In fact, they need to implement a specific version of their application which follows the Automotive UI guidelines, for example with bigger buttons. In addition to that, they often face the impossibility to have access to a real vehicle hardware setup, thus the need for a practical emulator for their developments and tests. Our Android Automotive device aims at fulfilling these needs by behaving as much as possible like a real vehicle. It provides some mocking features which were already present on our smartphone virtual devices (GPS, Networking, Disk IO, screen captures, etc.). It also introduces a new customized VHAL that let you connect through gRPC protocol and read/write all vehicle properties directly from within the virtual IVI emulator or though an external client. For more details and examples, please refer to this tutorial. What’s next? Head to AWS marketplace to start a virtual device with Android Automotive right now. Also, if you require a custom solution tailored to your operating system or unique needs, our team is ready to collaborate with you. Contact us to discuss your requirements and let us help you design and build the perfect solution for your project. Thank you for being part of this journey with us! We can’t wait to hear your feedback!
