![]() The difference in emulator speeds will expose timing issues in your tests.This means for local tests you may need to explicitly configure the IP address of the machine the emulator should connect to. You cannot use the special 10.0.2.2 IP address with Genymotion to access localhost on the machine you are running the emulator from.However, be warned there are some noticable differences between Genymotion and the default Android emulators: Genymotion also runs Robotium tests visibly faster, and with a smoother UI. The Genymotion startup time is around 5 seconds (compared to at least 30 seconds for the Android emulator). I've been investigating whether to use Genymotion, with a particular focus on running automated Robotium tests. This means it now covers all relevant android versions except Froyo (v2.2), which at this time accounts for only 1-2% of all devices :) Update: As of January 2014, Genymotion supports Android v2.3.7 as well as v4.3 (with v4.4 in preview). Also, the integration of Google Apps/Services in Genymotion is fantastic.Ĭompatibility is the only downside, since Genymotion only provides v4.1+ images there is no way to test compatibility on older android versions - but for these tests I just use the standard android emulator (which is fine since it is not as frequent as normal testing). However, take these with a grain of salt because benchmark scores will vary greatly depending on the host system.Īs for the items you want benchmarks for, not sure that camera/gps can even be benchmarked (what would you test), and networking is perfect since it uses VirtualBox, which has always had great virtual network support.Īs a graphics/game developer, I find Genymotion unparalleled for running OpenGL code - on Genymotion it runs much smoother framerate wise, than using an x86+HAXM+HW GPU android emulator. So I have to start the run again or remember to start the VM from Android Player before debugging.Have a look here for some informal benchmark comparisons. The only hiccup is that Visual Studio doesnt wait long enough for the emulator to start before attempting to deploy the app. Visual Studio will start the selected VM when I debug the default blank android app. ![]() Both of the VM devices I created in Android Player are visible in the drop down of the run menu. Installing Virtuallbox 5.1.2 after installing Android player seems to have resolved this.ĮDIT: I havent had a chance to test integration with Visual Studio yet.Įverything seems to be working as expected within Visual Studio. There seems to be some incompatibilities between Windows 10 Home and Virtualbox 5.0.4 that Android player installs. I had problems starting the android VMs, even after restarting the host. There is a free version for personal use only (with limited functionality), or a paid option that provides more capability.Īndroid player link has changed to here: In any case, its worth a shot.Īnother option is GenyMotion. So bugs may be present.įrom what I can see on the download page, it doesnt appear like you need Xamarin to actually use it. It should be noted that (at time of writing) this is still in Preview by the looks of things. They decided to create their own emulator to get around this, and it can be found here. Primarily that it was slow, and clunky, and they were getting a lot of complaints about it from Xamarin users (despite it not being their product/fault). Is there an alternative Android emulator for Visual Studio on Windows 10 Homeīoth the below options come with the caveat that I have not used either.Īpparently Xamarin had issues with the default Android Emulator.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |