JNTU MCA 2019 ANDROID MOBILE APPLICATION DEVELOPMENT Previous Question Paper (April/May - 2019 - R15)

Android OS design is built upon several core architectural features that ensure efficiency, security, and scalability:

• Linux Kernel: Android is built on top of the Linux kernel, which serves as the hardware abstraction layer. It manages low-level system services such as memory management, process management, and networking, while providing a secure foundation for drivers.
• Application Framework: This layer provides the building blocks for developers, including components like Activity Manager, Content Providers, and Resource Manager. It allows applications to reuse system components and share data seamlessly.
• Dalvik/ART Runtime: Android uses the Android Runtime (ART) to execute applications. Unlike traditional virtual machines, ART uses ahead-of-time (AOT) compilation to improve execution speed and battery efficiency by compiling bytecode into machine code during installation.
• Hardware Abstraction Layer (HAL): The HAL provides standard interfaces that expose device hardware capabilities to the higher-level Java API framework. This allows the Android system to function across diverse hardware configurations without requiring changes to the core OS code.
• Security and Sandboxing: Every Android application runs in its own process with a unique user ID. This sandboxing mechanism ensures that applications are isolated from one another and the underlying system, preventing unauthorized access to data or system resources.

To create a fragment in Android, you must define a class that extends the Fragment class (or one of its subclasses like ListFragment or DialogFragment). The process involves the following key steps:

1. Create a Java or Kotlin class that extends android.app.Fragment or androidx.fragment.app.Fragment.
2. Override the onCreateView() method, which is the most critical lifecycle method. This method returns the View hierarchy associated with the fragment.
3. Inside onCreateView(), use the LayoutInflater object to inflate the XML layout file defined for the fragment.
4. Optionally, override other lifecycle methods such as onCreate(), onPause(), or onDestroyView() to manage the fragment's state and resources.

Once the class is defined, the fragment can be added to an Activity's layout either statically by declaring it in the Activity's XML layout file using the <fragment> tag, or dynamically at runtime using the FragmentManager and FragmentTransaction API to add, replace, or remove fragments within a container view.