Aldeniz Rashidov, www.aldeniz.eu

In this section, I will introduce you how to create Android Virtual Device (AVD) for debugging of your applications with Android emulator in Eclipse. Eclipse is an integrated development environment, which used to develop Android and Java applications and provides the ability to create, compile, and set up Java programming code.

1. Preparing to install a virtual device

Some of the packages (images) in the different Android SDK APIs are used for debugging of applications on the Android emulator and need to be installed (Figure 1).

Fig. 1. Packages in Android SDK, needs for applications debugging

For example in API 24, these are the following packages:

• Android TV Intel x86 Atom System Image;
• ARM 64 v8a System Image;
• ARM EABI v7a System Image;
• Intel x86 Atom_64 System Image;
• Intel x86 Atom System Image.
• Google APIs ARM 64 v8a System Image;
• Google APIs ARM EABI v7a System Image;
• Google APIs Intel x86 Atom_64 System Image;
• Google APIs Intel x86 Atom System Image.

Usually, these packages are installed further from Android SDK Manager before starting the emulator. You may install the additional packages from an Android SDK by launching an Android SDK manager using Android SDK manager from Window menu in Eclipse (fig 3).

In case of you will start the emulator on PC with AMD CPU and will developed application for phone or tablet then can choice package ARM EABI v7a System Image. If you use PC with Intel CPU and will developed application for phone or tablet then can choice packageIntel x86 Atom_64 System Image or package Intel x86 Atom System Image. The packages-images, which names begins with prefixes Google APIs (for example Google APIs Intel x86 Atom System Image) are choices when in your application are used services or functions of Google.

When you use Intel x86 Atom_64 System Image or Intel x86 Atom System Image is necessary to add the package Intel x86 Emulator Accelerator (HAXM installer) (fig. 2). Otherwise, with this image, the emulator will not be start. Choosing and downloading of package will not installed HAXM. To be use HAXM you must install it from folder extras (
{SDK_FOLDER}\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm.exe) of Android SDK.

Fig. 2. Package Intel x86 Emulator Accelerator (HAXM installer)

When SDK Manager for any reason does not allow you to download this package, you may use an address https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager-end-user-license-agreement from site of Intel® with resources for Android (Intel® Hardware Accelerated Execution Manager, https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager?page=3 ). The package is archived (haxm-windows_v6_1_1.zip), and must be extracted in some folder and then installing with intelhaxm-android.exe.

When is not possible starting the emulator withIntel x86 Atom_64 System Image or Intel x86 Atom System Image on PC with Intel CPU you can be use package (image) for AMD CPU, which is more slowly by speed in this case.

Option to startup Emulator without use the Intel x86 Emulator Accelerator package is only available when if from command prompt (console) in tools folder of SDK run:

C:\Users\IEUser\android-sdks\tools> emulator -avd name -memory 512 -no-accel -gpu off

name is name of Android Virtual Device (AVD), which you created in AVD Manager (Windows menu of Eclipse).

You can use this option if your computer or system does not support virtualization, or when using the emulator via VMware or Virtual Box.

2. Starting of Android Virtual Device manager using Android Virtual Device Manager from menu Window в Eclipse

Фиг. 3. Starting of Android Virtual Device manager

3. Defining of new physical device

Before create a new virtual device, you need to specify the physical device on which it will be based. You can select a device from the list in the Device Definitions section of AVD Manager (for example, Galaxy Nexus by Google) or define your own (fig. 4). Defining a new physical device is done by using the button Create Device.

Fig. 4. Defining of new physical device

Must be defined the basic parameters for the device – diagonal size, resolution, sensors and more (fig. 5).

Fig. 5. Defining of parameters of the new physical device

4. Creating of the new virtual device

Creating new virtual devices is done by using the buttonCreate (fig. 6)from Android Virtual Devices section in AVD Manager. It is possible to clone an already created virtual device after you mark the desired virtual device and use the Edit button.

Fig. 6. Creating of new virtual device

Some of the most important parameters to be established are the following (fig. 7):

• Name of virtual device (AVD Name);
• Based physical device (Device);
• Android version (API) (Target);
• Package-image for a corresponding CPU (CPU/ABI);
• Using keyboard of PC (Hardware keyboard present);

The Skin is a parameter that used to achieve the closest visual identity to the actual device and usually provided by the manufacturer. For example, Samsung offers skin for its devices at http://developer.samsung.com/galaxy/emulator-skin# . Installing of some skins is done after as downloaded archive file is unzipped into a separate subfolder of the skins folder on a selected platform in SDK. The downloaded Samsung Galaxy S4 image (Galaxy_S4_White.zip) can be unzipped for use with the API 24 in a folder {SDK_FOLDER}\platforms\android-24\skins\galaxy_s 4. The parameters for RAM, internal storage and SD Card should be set according to your preferences and the real possibilities of the system.

Fig. 7. Parameters at creating of new virtual device

5. Launch the selected virtual device and launch of Android emulator

Starting of Virtual devices is done by using the Start button (fig. 8) in Android Virtual Devices section from AVD Manager. Before booting the Android emulator, you can change some parameters in Launch Options dialog box. Launching emulator is performed using the Launch button (fig 9).

Fig. 8. Launching of the created virtual device

Fig. 9. Starting of emulator

Launching of Android emulator take up to a few minutes, depending on your system resources (fig. 10 and fig. 11).

Fig. 10. Launching of android emulator

Fig. 11. Successfully launched Android emulator

Aldeniz Rashidov, www.aldeniz.eu

In this section, I will introduce you how to install the Android Application Development Toolkit (Android SDK) in Eclipse under Windows OS. Eclipse is an integrated development environment, which used to develop Android and Java applications and provides the ability to create, compile, and set up Java programming code.

A. Installation of Android SDK through Eclipse

1. Choice of option Install new SDK in dialog window, which visualize after successfully installation of Eclipse IDE (fig. 1). It is necessary setup folder for installation of Android SDK. Button Finish start processing of installation on last SDK version. In case that SDK installed, in filed Existing Location, you can set base folder.

Fig. 1. Installation of Android SDK

2. Choice of the base (required and mandatory) packages on Android SDK for installation and accept of the license agreements (fig. 2). The button Install chooses next step at process of installation.

Fig. 2. Choice of the base (required and mandatory) packages by Android SDK

3. Choice of additional packages of SDK for installation (fig. 3 and fig. 4). Notice for installing these packages is generate from installation process, because there are necessary for developing and testing Android applications (fig. 3).

Fig. 3. Notice for installation of additional packages of SDK

Fig. 4. Choice of additional packages for installation

In case of you skip to select these packages and closes the reminder window, you can later use the option Android SDK Manager from menu Windows of Eclipse to continue. The additional packages are important at developing and testing of the Android applications and without them practically is not possible to continue.

Figure 5 shows packages, which provides features for development of application for versions 7.1.1, 7.0 and 5.0.1 of Android.

The base package in each separate version, which provides development of applications, is SDK Platform. When developing apps for different versions of Android, you need to select the appropriate package of SDK Platform for the version you want. It is recommended to add an SDK platform for some older versions of Android, such as 5.0.1 (API 21).

Here is a preview of the more important features of some versions:

• API 25 (Android 7.1.1)
  – New Professional Emoji; Round Icon Resources; Improved VR Thread Scheduling; Image Keyboard Support.

• API 24 (Android 7.0)
  – Multi-window Support; Notification Enhancements; Multi-locale Support; More Languages.

• API 23 (Android 6.0)
  – Runtime permissions; Doze mode and App Standby; Text Selection; BoringSSL; APK Validation.

• API 21 (Android 5.0)
  – Massive changes; Material design style; Screen capturing and sharing; Multiple network connections.

• API 19 (Android 4.4)
  – New NFC smart card capabilities; Printing framework; Storage access framework; New ways to build beautiful apps; Screen recording.

• API 18 (Android 4.3)
  – Notification Listener; Contacts Provider; Restricted Profiles; Solution for digital rights management (DRM); Rotation animations.

• API 14 (Android 4.0)
  – Spell Checker Services; Text-to-speech Engines; Social APIs in Contacts Provider; Voicemail Provider; Android Beam (NDEF Push with NFC); GridLayout, Popup menus.

• API 11 (Android 3.0)
  – Native Fragments & Action Bar; Drag and drop; Split touch events; WebViewFragment; JSON utilities.

The Google APIs package, at each separate versions, provides integration of the applications with Google services. Google USB Driver is use at debugging of Google Nexus devices. Android Support Repository provides important additional functions at application development. Google Play services integrate functions for work with Google Maps, Google+ etc.

Some of the packages (images) are used for debugging of application with the Android emulator:

• Android TV ARM EABI v7a System Image;
• Android TV Intel x86 Atom System Image;
• Android Wear ARM EABI v7a System Image;
• Android Wear Intel x86 Atom System Image;
• ARM EABI v7a System Image;
• Intel x86 Atom_64 System Image;
• Intel x86 Atom System Image.

In case of you will start the emulator on PC with AMD CPU and will developed application for phone or tablet then can choice package ARM EABI v7a System Image. If you use PC with Intel CPU and will developed application for phone or tablet then can choice packageIntel x86 Atom_64 System Image or package Intel x86 Atom System Image.

Fig. 5. Recommended packages for installation

When you use Intel x86 Atom_64 System Image or Intel x86 Atom System Image is necessary to add the package Intel x86 Emulator Accelerator (HAXM installer) (fig. 6). Otherwise, with this image, the emulator will not be start. Choosing and downloading of package will not installed HAXM. To be use HAXM you must install it from folder extras (

{SDK_FOLDER}\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm.exe) of Android SDK.

Fig. 6. Package Intel x86 Emulator Accelerator (HAXM installer)

When SDK Manager for any reason does not allow you to download this package, you may use an address https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager-end-user-license-agreement from site of Intel® with resources for Android (Intel® Hardware Accelerated Execution Manager, https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager?page=3 ). The package is archived (haxm-windows_v6_1_1.zip), and must be extracted in some folder and then installing with intelhaxm-android.exe.

When is not possible starting the emulator withIntel x86 Atom_64 System Image or Intel x86 Atom System Image on PC with Intel CPU you can be use package (image) for AMD CPU, which is more slowly by speed in this case.

Option to startup Emulator without use the Intel x86 Emulator Accelerator package is only available when if from command prompt (console) in tools folder of SDK run:

C:\Users\IEUser\android-sdks\tools> emulator -avd name -memory 512 -no-accel -gpu off

name is name of Android Virtual Device (AVD), which you created in AVD Manager (Windows menu of Eclipse).

You can use this option if your computer or system does not support virtualization, or when using the emulator via VMware or Virtual Box.

4. Accepting of license agreement for installation of additional packages (fig. 7). The button Install choose the next step at process of installation.

Fig. 7. Accepting of license agreement for installation of packages

B. Self-install of Android SDK

1. Download of Android SDK from https://developer.android.com/studio/index.html (fig. 8 и fig. 9).

Fig. 8. Download of Android SDK for specific OS version

Fig. 9. Download of Android SDK for specific version and accepting of license agreement

2. Creating of base folder on Android SDK (for example c:\eclipse\android-sdk) (fig. 10)

Fig. 10. Creating of base folder on Android SDK

3. Creating of folder tools into the base folder on Android SDK (c:\eclipse\android-sdk\tools) (fig. 11).

Fig. 11. Creating of folder tools into the base folder on Android SDK

4. Opening downloaded file tools_r25.2.3-windows.zip and extract it in folder tools on Android SDK (fig. 12).

Fig. 12. Opening downloaded file tools_r25.2.3-windows.zip

5. Execution of the file android.bat from folder tools, which will install Android SDK in console mode (fig. 13).

Fig. 13. Installation of SDK from console

6. Installation of additional packages from Android SDK Manager, which is open automatically at process of installation (fig. 14). You can use the instructions for installing packages from SDK Manager in p. 3.

Fig. 14. Installation of packages from Android SDK Manager

7. Starting of Eclipse and choosing of option Use Existing SDKs in dialog window, which visualize after successfully installation of Eclipse IDE (fig. 1). In filed Existing Location, you can set base folder of Android SDK, which created in p. 2.

If the dialog box not appear, the location of the SDK is setting by using the option Preferences from Windows menu of Eclipse. Then choose the location of the Android SDK in the SDK Location field of the Android menu (fig. 15).

Fig. 15. Setup location of Android SDK

Aldeniz Rashidov, www.aldeniz.eu

Contents:
I. Installation of Eclipse under MAC OS X
II. Installation of Eclipse under Windows

I. Installation of Eclipse under MAC OS X

In this section I will you introduce how install the integrated development environment (IDE) Eclipse under OS MAC OS X. Eclipse is an essential tool used at development of Android and Java applications and provides the ability to create, build and setup program code in Java.

1. Download Eclipse from address https://www.eclipse.org/downloads/(fig. 1).

Fig. 1. Installation Eclipse Neon

2. By using the button Download 64 bit is performed confirmation of download or choose an alternative server for downloading Eclipse (Fig. 2).

Fig. 2. Confirmation before downloading of Eclipse

3. Select folder to store the installation file eclipse–inst–mac64. tar.gz. The file downloads
all necessary components of Eclipse. The direct address of the file is https://www.eclipse.org/downloads/download.php?file=/oomph/epp/neon/R2a/eclipse-inst-mac64.tar.gz&mirror_id=1208.

Fig. 3. Select folder to store the installation file

4. Open the downloaded (archive) file eclipse–inst–mac64.tar .gz. Unarchive file into the current (or another) directory. Open the file with name Eclipse installer (Fig. 3).

5. At first start of the installation file is required to confirm with button Open, that you agree to run the file that is downloaded from the Internet (Fig. 4).

Fig. 4. Confirmation for opennig of the installation file

6. The installation file checks for necessary tools to work with Eclipse. Checks whether is installed extension Java Development Kit (JDK) on platform Java Runtime Environment (JRE). JDK expands JRE with tools for developing of Java applications.

Fig. 5. Check for Java Development Kit (JDK)

7. Download of Java Development Kit (JDK) from http://www.oracle.com/technetwork/java/javase/downloads/(Fig. 6). The direct link to download Java SE Development Kit 8u121 is http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html.

Fig. 6. Download Java Development Kit

8. Choosing a version Java SE Development Kit 8u121 for OS X. Before download the file jdk-8u121-macosx-x64.dmg for MAC OS X x64 you need to agree with license terms for use of the JDK (Fig. 7) as select button Accept License Agreement.

Fig. 7. Download verion Java SE Development Kit 8u121 for MAC OS X

9. Start the downloaded (image archive) file jdk-8u121-macosx-x64.dmg and launch the setup file JDK 8 Update 121.pkg (Fig. 8).

Fig. 8. Start of installation file with Java Development Kit

10. Installation of JDK 8 Update 121 (fig. 9 and fig. 10).

Fig. 9. Start the installation of JDK 8 Update 121

Fig. 10. Successfully installed JDK 8 Update 121

11. Restart of the Eclipse installation process by file Eclipse installer (fig. 3 and fig. 11).

Fig. 11. Installing of Eclipse after installation of JDK

12. Selecting the version for install according to the application and the specifics of programming. In the event that you will develop applications for the Android OS, it is desirable to choose a version Eclipse for Android Developers (Fig. 12).

Fig. 12. Selecting the version Eclipse for Android Developers

13. Installing a version Eclipse for Android Developers (fig. 13).

Fig. 13. Installing a version Eclipse for Android Developers

14. Accepting the license agreement to install a version of Eclipse for Android Developers (fig. 14).

Fig. 14. Accepting the license agreement to install a version of Eclipse for Android Developers

15. Successfully installed version Eclipse for Android Developers (fig. 15).

Fig. 15. Successfully installed version Eclipse for Android Developers

16. Launch of Eclipse for Android Developers (fig. 16) after using of button Launch (fig. 15).

Фиг. 16. Launch of Eclipse for Android Developers

17. Set the working area (working directory) of Eclipse (Fig. 17). The work area can be changed each start time of Eclipse in case the option Use this as the default and do not ask again not be selected.

Fig. 17. Set the working area (working directory) of Eclipse

18. Configure of the Android SDK, required to develop applications for Android. Eclipse offers to download Android SDK or select the folder in which is installed version of the Android SDK (Fig. 18).

Fig. 18. Configure of the Android SDK for use with Eclipse

19. Home screen of Eclipse (fig. 19 and fig. 20).

Fig. 19. Home screen of Eclipse – choice of operation

Fig. 20. Home screen of Eclipse – workspace

Mobi&Learn APK unit is free application and can be used only with Mobi&Learn platform.
It is used from mobile devices as smartphones, tablets and etc. for learning goal.
After registration in Mobi&Learn platform (http://mobilearn.aldeniz.eu) educators may test their courses with Mobi&Learn APK unit. With Mobi&Learn APK unit registered users (students) in Mobi&Learn system can upload courses (created from educators or from them) on the their mobile devices via identity number and security code supplied from from author of course. Some of courses are free and do not need by security code.

The free (this) version of Mobi&Learn system has any more limitations:
– create one course,
– down to 3 lessons,
– down to 3 sections and
– down to 3 resources for course, lesson or section.

Download Mobi&Learn APK: