Android glossary Overview

There are some frequently used terms in the Android mobile phone operating system. We need to be proficient in the learning process to better use this system to help us meet some requirements. Let's take a look at the several common Android terms we have summarized here.

• The Android debugging procedure is correct.
• Introduction to Android root file system applications
• Android database operation tips
• Android lifecycle concepts
• Overview of Android Defects

1. apk Extension: apk is the extension of the Android package. An Android package contains all files related to an Android Application. xml files, application code (dex files), resource files, and other files form a compressed package. A project can only be packaged and compressed into one apk file.

2. dex Extension: the Android program is compiled into a. dex (Dalvik Executable) file, and then packaged to generate an apk file that can be directly installed.

3. Application: A collection of one or more Activity, service, listener, and Intent receivers. An application has a file list and is packaged into an apk file. 4. Action: Describe the Intent of the Intent transmitter. An activity is a string value assigned to the Intent.

5, ADB Android Debug Bridge): a command line-based debugging program that comes with the SDK. It provides a device browsing tool, a copy tool on the device, and debugging the forwarding port function.

6. content source: the content source in Android terminology is a class that is built on the class ContentProvider to process the content request strings in the specified format and return the data in the specified format.

7. Dalvik Android: Virtual Machine name. The Dalvik virtual machine is a virtual machine that can only explain the execution of dex files. The dex file is optimized for storage performance and memory management. The Dalvik virtual machine is a register-based virtual machine that can run Java classes that have been converted by the "dx" tool that comes with Dalvik. Virtual machines run on Posix-compatible operating systems and rely on underlying functions (such as thread and low-level memory management ). Dalvik's core class library is intended to be very similar to the Java standard version, but it is obviously more suitable for small mobile devices.

8. Intent: Intent is an Intent class, which contains many fields that describe what the caller intends to do. The caller sends the intent to the Android intent processor. The intent processor traverses the intent filters of all applications to find the Activity that best matches the intent. Intent fields include desired actions, types, Data, MIME types of data, a processing class, and other constraints.

9. intent-filter: Activity and intent Receiver include one or more filters in their file list, it is used to describe what type of intent or information they can process or want to receive. An intent filter lists a series of requirements, such as the data type that the intent or information must meet, the requested action, and the URI format. For the Activity, Android searches for the Activity with the highest matching intention and Activity filter. For the message, Android forwards the message to all receivers that match the intent filter.

10, Intent Receiver (Receiver): A listener is a class that broadcasts information from Context. broadcastIntent.

11. layout resources: an XML file that describes the Activity screen layout.

12. File List: an XML file in the application that describes multiple activities, Intent filters, services, and other content in the package. You can open AndroidManifest. xml to view its contents.

13. resource: the entire Android term provides users with XML, bitmap, or other files. It is imported into the build program and loaded by code later. Android supports multiple types of resources, please refer to the detailed description in Resources. The resource file defined by the program should be saved in the res/subdirectory.

14. Service: A class that runs a variety of fixed tasks in the background, such as playing music or detecting network activities.

15. URIs: Android uses a URI string to request data (such as a mailing list) and actions (such as opening a webpage in a browser ). Strings can have different formats. The URI of all request data must start with "content. Valid URI strings are processed by appropriate programs on the device. For example, URI strings starting with "http: //" are processed by the browser.

16. AIDL (AndRoid Interface Description Language): It is an interface Description Language. the compiler can generate a piece of code through the aidl file and use a pre-defined interface to implement internal communication between two processes.

17. JNI: java local programming Interface, short for Java Native Interface. It enables java code to interwork with applications and libraries written in other programming languages. Most other programming languages are c, c ++, and assembly languages .)

The above is all the Android terms we have summarized for you.