![]() This means that it can work with virtually any emulator (such as Genymotion, which runs via VirtualBox). The way the development environment (Android Studio) connects to the emulator is via ADB (Android Debug Bridge). The emulator also provides GPU acceleration (it must be manually enabled for each emulator device) which allows it to use your physical GPU for rendering instead of emulating these operations in software. There are also Google API versions of these images (they include various Google apps such as Google Play Services) which can be used if these components are needed by your app.įor development purposes, the x86 system images are your best bet as performance is vastly improved by the emulator not having to emulate the ARM architecture - you need to use HAXM (by intel, also available in the Android SDK) to get any real speed benefits with x86 images though. For most recent Android versions, there are 2-4 different system images - arm, arm 64-bit, x86, and x86 64-bit (the 64-bit ones are Lollipop only, and fairly experimental at this stage of the game ). The way it works depends on what kind of system image you use it with. It is in fact included with the Android SDK (which is in turn included in Android Studio) and used by various development environments. ![]() The emulator used by Android Studio is the exact same one used with Eclipse. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |