{"id":265,"date":"2023-05-16T12:47:52","date_gmt":"2023-05-16T12:47:52","guid":{"rendered":"https:\/\/itnotes.apjsoftwares.com\/?p=265"},"modified":"2023-05-16T12:47:52","modified_gmt":"2023-05-16T12:47:52","slug":"1-5-android-emulator-working-with-androidmanifest-xml","status":"publish","type":"post","link":"https:\/\/itnotes.apjsoftwares.in\/index.php\/2023\/05\/16\/1-5-android-emulator-working-with-androidmanifest-xml\/","title":{"rendered":"1.5 Android emulator, working with AndroidManifest.xml"},"content":{"rendered":"\n

Android Emulator<\/strong><\/h2>\n\n\n\n

The Android emulator is an Android Virtual Device (AVD), which represents a specific Android device. We can use the Android emulator as a target device to execute and test our Android application on our PC. <\/p>\n\n\n\n

The Android emulator provides almost all the functionality of a real device. We can get incoming phone calls and text messages. It also gives the location of the device and simulates different network speeds. <\/p>\n\n\n\n

Android emulator simulates rotation and other hardware sensors. It accesses the Google Play store, and much more<\/p>\n\n\n\n

Testing Android applications on emulators is sometimes faster and easier than doing on a real device. For example, we can transfer data faster to the emulator than to a real device connected through USB.<\/p>\n\n\n\n

The Android emulator comes with predefined configurations for several Android phones, Wear OS, tablet, Android TV devices.<\/p>\n\n\n\n

Requirement and recommendations<\/strong><\/h3>\n\n\n\n

The Android emulator takes additional requirements beyond the basic system requirement for Android Studio. These requirements are given below:<\/p>\n\n\n\n

    \n
  • SDK Tools 26.1.1 or higher<\/li>\n\n\n\n
  • 64-bit processor<\/li>\n\n\n\n
  • Windows: CPU with UG (unrestricted guest) support<\/li>\n\n\n\n
  • HAXM 6.2.1 or later (recommended HAXM 7.2.0 or later)<\/li>\n<\/ul>\n\n\n\n

    Install the emulator<\/strong><\/h3>\n\n\n\n

    The Android emulator is installed while installing the Android Studio. However some components of the emulator may or may not be installed while installing Android Studio. <\/p>\n\n\n\n

    To install the emulator component, select the Android Emulator component in the SDK Tools tab of the SDK Manager.<\/p>\n\n\n\n

    Run an Android app on the Emulator<\/strong><\/h3>\n\n\n\n

    We can run an Android app from the Android Studio project, or we can run an app which is installed on the Android Emulator as we run any app on a device.<\/p>\n\n\n\n

    To start the Android Emulator and run an application in our project:<\/p>\n\n\n\n

    1. In Android Studio, we need to create an Android Virtual Device (AVD) that the emulator can use to install and run your app. To create a new AVD:-<\/p>\n\n\n\n

    1.1 Open the AVD Manager by clicking Tools > AVD Manager.<\/p>\n\n\n\n

    1.2 Click on Create Virtual Device, at the bottom of the AVD Manager dialog. Then the Select Hardware page appears.<\/p>\n\n\n\n

    1.3 Select a hardware profile and then click Next. If we don’t see the hardware profile we want, then we can create or import a hardware profile. The System Image page appears.<\/p>\n\n\n\n

    1.4 Select the system image for the particular API level and click Next. This leads to opening a Verify Configuration page.<\/p>\n\n\n\n

    1.5 Change AVD properties if needed, and then click Finish.<\/p>\n\n\n\n

    2. In the toolbar, choose the AVD, which we want to run our app from the target device from the drop-down menu.<\/p>\n\n\n\n

    3. Click Run.<\/p>\n\n\n\n

    Working with AndroidManifest.xml<\/strong><\/p>\n\n\n\n

    The AndroidManifest.xml file contains information of your package, including components of the application such as activities, services, broadcast receivers, content providers etc.<\/p>\n\n\n\n

    It performs some other tasks also:<\/p>\n\n\n\n

      \n
    • It is responsible to protect the application to access any protected parts by providing the permissions.<\/li>\n\n\n\n
    • It also declares the android api that the application is going to use.<\/li>\n\n\n\n
    • It lists the instrumentation classes. The instrumentation classes provide profiling and other information. This information is removed just before the application is published etc.<\/li>\n<\/ul>\n\n\n\n

      This is the required xml file for all the android applications and located inside the root directory.<\/p>\n\n\n\n

      A simple AndroidManifest.xml file looks like this:<\/strong><\/p>\n\n\n\n

      <manifest xmlns:android=”http:\/\/schemas.android.com\/apk\/res\/android”  <\/p>\n\n\n\n

          package=”com.javatpoint.hello”  <\/p>\n\n\n\n

          android:versionCode=”1″  <\/p>\n\n\n\n

          android:versionName=”1.0″ > <\/p>\n\n\n\n

          <uses-sdk  <\/p>\n\n\n\n

              android:minSdkVersion=”8″  <\/p>\n\n\n\n

              android:targetSdkVersion=”15″ \/>    <\/p>\n\n\n\n

          <application  <\/p>\n\n\n\n

              android:icon=”@drawable\/ic_launcher”  <\/p>\n\n\n\n

              android:label=”@string\/app_name”  <\/p>\n\n\n\n

              android:theme=”@style\/AppTheme” >  <\/p>\n\n\n\n

              <activity  <\/p>\n\n\n\n

                  android:name=”.MainActivity”  <\/p>\n\n\n\n

                  android:label=”@string\/title_activity_main” >  <\/p>\n\n\n\n

                  <intent-filter>  <\/p>\n\n\n\n

                      <action android:name=”android.intent.action.MAIN” \/>  <\/p>\n\n\n\n

                      <category android:name=”android.intent.category.LAUNCHER” \/>  <\/p>\n\n\n\n

                  <\/intent-filter>  <\/p>\n\n\n\n

              <\/activity>  <\/p>\n\n\n\n

          <\/application>    <\/p>\n\n\n\n

      <\/manifest><\/p>\n\n\n\n

      Elements of the AndroidManifest.xml file<\/strong><\/p>\n\n\n\n

      The elements used in the above xml file are described below.<\/p>\n\n\n\n

      <manifest><\/strong><\/p>\n\n\n\n

      manifest is the root element of the AndroidManifest.xml file. It has a package attribute that describes the package name of the activity class.<\/p>\n\n\n\n

      <application><\/strong><\/p>\n\n\n\n

      application is the subelement of the manifest. It includes the namespace declaration. This element contains several sub elements that declares the application component such as activity etc.<\/p>\n\n\n\n

      The commonly used attributes of this element are icon, label, theme etc.<\/p>\n\n\n\n

      android:icon<\/strong> represents the icon for all the android application components.<\/p>\n\n\n\n

      android:label<\/strong> works as the default label for all the application components.<\/p>\n\n\n\n

      android:theme<\/strong> represents a common theme for all the android activities.<\/p>\n\n\n\n

      <activity><\/strong><\/p>\n\n\n\n

      activity is the subelement of application and represents an activity that must be defined in the AndroidManifest.xml file. It has many attributes such as label, name, theme, launchMode etc.<\/p>\n\n\n\n

      android:label<\/strong> represents a label i.e. displayed on the screen.<\/p>\n\n\n\n

      android:name<\/strong> represents a name for the activity class. It is a required attribute.<\/p>\n\n\n\n

      <intent-filter><\/strong><\/p>\n\n\n\n

      intent-filter is the sub-element of activity that describes the type of intent to which activity, service or broadcast receiver can respond to.<\/p>\n\n\n\n

      <action><\/strong><\/p>\n\n\n\n

      It adds an action for the intent-filter. The intent-filter must have at least one action element.<\/p>\n\n\n\n

      <category><\/strong><\/p>\n\n\n\n

      It adds a category name to an intent-filter.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Android Emulator The Android emulator is an Android Virtual Device (AVD), which represents a specific…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[9],"tags":[],"_links":{"self":[{"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/posts\/265"}],"collection":[{"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/comments?post=265"}],"version-history":[{"count":1,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/posts\/265\/revisions"}],"predecessor-version":[{"id":266,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/posts\/265\/revisions\/266"}],"wp:attachment":[{"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/media?parent=265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/categories?post=265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itnotes.apjsoftwares.in\/index.php\/wp-json\/wp\/v2\/tags?post=265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}