Monday , November 29 2021

Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer

Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer – Java SDK, we have to install Android SDK, which provides us all the necessary functionalities related to Develop, Design, Test and Debug our Android Application on our Local Computer.

Step by Step guide to install Android Emulator in Windows 8/10 - Android Developer
Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer

First of all we have to download Appropriate “Android Package” according to the Installed Operating System on our Computer System from the “All Android Studio Packages” section as per the following figure from http://developer.android.com/sdk/index.html:

Since we are using Windows Operating System and around 95% of users use Windows Operating System, Google has also created a Recommend Installer for Windows Operating System, which we do not have any configuration on installing. Rather, we are able to use Android-Studio in the same way that we use Visual-Studio, Eclipse or NetBeans.

When we install “Android SDK Tools” on our Computer System, an Emulator named “AVD Manager” is also installed under the “Tools” Directory, which emulates an Android Device on our Local Computer System. So that we can test our developing Android application by creating a Specific Android Device Virtually on our Computer System.

Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer

The advantage of this tool is that even if we do not have that Android Device available for which we are developing our Android Application, we can still test our application for that our application on that Specific Device Which way will Execute.

We can create emulators for as many Android devices as we need and wish, and all the emulators we create are stored under “Android Virtual Device (AVD)”, which we call “AndroidSDKFolder \ tools \ AVD Manager Add / Edit / Configure through the “.exe” tool.

To create a new emulator, we have to click the “Create…” button that appears on this Dialog Box, which results in a new Dialog Box Display as follows, where we have various configurations related to our new Android Virtual Device (AVD). Have to specify:

The detailed description of various options of this Dialog Box that we have to set is as follows:

AVD Name

Here, we have to specify the name of our newly created AVD. This is the name we use to test our Newly Created Android Application at Command Prompt and give the Instruction to the Computer System on which Emulator we have to run and test. So it is better that the name should be Short and Easy to Remember.

Device

When we install Android SDK Tools, some Android devices related configurations are also installed, which can directly create devices with related configuration without specifying any manual configuration.

For example, if we want to test our Android Application on Google’s “Nexus 7 (2012)” Device, then we do not need to specify any manual configuration to create an emulator related to this device, rather than this Screen With the “Device” Combobox, we can directly select the Emulator Configuration of this Android Device from the Predefined Device List as shown below:

Target

In this section, we select the Android platform on which we want to test our Android application. Generally, we should always test our application on the latest Android platform. However during development, we can test our application on more than one Android platform and select a specific Android platform from this Combobox as per the following picture for our emulator:

CPU / ABI

In this Combobox, we do not have to select anything, because as soon as we select the Target Platform, the associated Appropriate Value gets the CPU / ABI Automatically Fill.

Keyboard

This is a checkbox, which we check and instruct to add the keyboard with the emulator, so that we can input the text data into our emulator. Whereas if our application does not need to get any kind of Text Data Input, we can also keep this checkbox unchecked.

Skin

As skin, we specify the Screen Resolution of our Target Device. This is also a Combobox, from where we can select a Predefined Screen. For example, if we select a skin named WQVGA800 here, it means that the Screen Resolution of the Target Device for our application is 800 x 480.

Front Camera / Back Camera

Through these two options, we can specify the Front Camera and Back Camera of our Target Device. Generally in Emulators which are Camera.

Memory Options

Under Memory Options, we specify the memory of our Target Device. It is to be noted here that although the memory of our Target Device may be very low or very high, but the memory of our Emulator should be kept as much as it is sufficient. Because by specifying more memory than capacity, the speed of our computer system slows down considerably.

For example, if the total RAM installed on our computer system is 4GB, we cannot allocate 1GB of memory in this memory options, otherwise our emulator will be quite slow. Anyway, for Android Development it is necessary to have at least Core i3 4th Generation Processor and Computer System with 8GB RAM, otherwise the emulators do not work properly and are quite slow.

Internal storage

If the Target Device has Internal Storage, then the Internal Storage in the Emulator is also specified in this section.

SD Card

Like Internal Storage, we can install SD card as external storage in almost all Android devices and if the SD card is to emulate in the emulator too, then its size is specified here.

Although 2GB size is quite normal size as internal storage and SD card, but when we specify 2GB storage for an emulator, this storage is reserved on our Hard Disk Derive.

So it is better that the size of Internal Storage and SD Card should not be specified more than 16MB or 32MB, because anyway there are very few applications which are so large.

However, we can increase the storage size of our emulator by increasing it whenever needed.

Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer

Not only this, the higher the size of storage of the emulator, the worse their performance. Therefore the size of storage should be kept as minimum as possible.

In this way, by specifying the various confutation of the AVD Emulator related to our Target Device, as soon as we click on the “OK” button, we have another Dialog Box Display as per the following figure, which is different from our Newly Create AVD. Display configurations:

As soon as we click on the OK button that appears on this Dialog Box, our new AVD Emulator Device is created, which we can see in our Android Virtual Device (AVD) Manager Dialog Box as shown in the next figure:

All the Emulators we create are visible in this Dialog Box. So any emulator that we have to start to test our Android application, select it and click on the “Start…” button that appears on this Dialog Box, resulting in a name named “Launch Options” as per the following figure. And there is Dialog Box Display:

In this Dialog Box, we can Rescale the size of our Emulator Device Screen by checking the “Scale display to real size” checkbox. While clearing the Exist data beforehand, you can check the “Wipe user data” checkbox to start the emulator.

Lastly, as soon as we click on the “Launch” button that appears on this Dialog Box, there is a Splash Screen Display as per the following picture, which indicates that our Android Emulator is starting:

And finally our emulator starts.

When this emulator is fully loaded, then it begins to appear as follows, however the time it takes for this emulator screen to display depends entirely on the Capabilities of our Computer System i.e. Speed ​​and RAM of Processor and Android For development, we always need a computer system with high configurations, which has at least 8GB of RAM:

Step by Step guide to install Android Emulator in Windows 8/10 – Android Developer

In this way, now we can test our Android applications on this emulator and test our application by running it on this emulator in the same way that we run it on our Android Device.

Read Also – Guide to Android App Architecture Extensions

About dmtechnolab

Check Also

Simplified Coding

Android Espresso Tutorial – Testing Fragment in Isolation – Android Coding by DMTechnolab

Welcome to another tutorial in the Android test series. And this post is called Android …

Leave a Reply

Your email address will not be published. Required fields are marked *