#Genymotion visual studio android

If you haven’t been using android emulator for some time. We are now having a faster test execution time, better command line tools.Īlso with the latest Android Emulator, things have gone a notch up. This feels more of a virtual box beating qemu thing. So I’ve settled for 3GB of ram for an emulator.įrom the benchmarks, you can see that Android emulator beats Genymotion expect for in Geekbench4.

I noticed that giving emulator less ram caused a lot of Google API crashes.

I’ve used a Nexus 5 system image with Google APIs.

There are a few more details that are of great importance. This brings us to the conclusion that the best one is x86 with Google APIs.īefore we pit our winning emulator against Genymotion. Well, I’ll tell you the problem with every one of them.Įmulator with Google APIs is more stable, things tend to crash without them. The winner of the competition is x86 with Google APIs I did some research and benchmarking with these combinations and this is what we came up with. The biggest question of all is x86 or x86_64 and with Google APIs or without them. The first time you try to set-up one of these it gives you so many options that you’ll feel like you are in Subway restaurant.

#Genymotion visual studio manual

This was a manual task, imagine doing it on a CI infrastructure with lots of machines.

They needed a periodic restart because of memory issues.

Genymotion takes ~23 minutes to run all the tests.Ī few other problems faced with Genymotion. My use case is to run integration tests on them (mostly espresso), just over 1100 tests. But when you get into the nitty-gritty of the situation, you’ll find Android emulator to be superior. The task at hand was to get rid of Genymotion used in CI infrastructure and machine.Īt a quick glance it seems like a stupid move as Android emulators are slow and buggy. I’m using Genymotion in CI infrastructure and on my machine. Let’s jump to how the situation is today. But it is quite stable & fast compared to plain old android emulators which run on qemu.

Then came along Genymotion, which is just an Android VM running in a virtual box. Now you can run x86 Android emulator on an x86 machine.Īndroid emulators were still slow from what people wanted. Then came along the x86 images of Android which are way faster as they get rid of the ARM to x86 platform change. What can you expect out of an ARM emulator running on an x86 machine? Every instruction had to be converted from ARM to x86 architecture which makes it really slow. But they were too slow to use, the reason being a change of architecture. Long ago Android emulator was the only way to go.

Psst: I have some benchmarks down the line, stick around. But it is slower when running tests compared to certain Android emulators.Ī little background on the subject and then we’ll jump to the good stuff. They have other products like Genymotion on Cloud & Genymotion on Demand which are not being considered here. Wherever I say Genymotion I mean Genymotion Desktop. running tests.Īll benchmarks were done on a mid-2015 MacBook Pro. Use x86 (32 bit) image with Google APIs, 3GB ram, quad-core CPU.ĭisclaimer: I’ve tested my use case which to me looks the general use case i.e. TL DR: Android emulator is faster than Genymotion when configured right. Based on this I’ll be evaluating all the android emulators along with Genymotion.

I’ve gathered some data around the most common use case in my experience. I’ve seen most of the discussion ending in favour of Genymotion. There has always been a debate about which android emulator to choose or to go with Genymotion.