Android Operating System Architecture and Features

Unlike the standard Java Virtual Machine (JVM) used in desktop environments, which is stack-based, Dalvik is a register-based VM. This design makes it highly optimized for mobile devices that have limited memory and CPU power. A key feature of the Dalvik VM is that it enables every Android application to run in its own dedicated process with its own instance of the virtual machine.

The execution process follows a specific workflow: Java .class bytecode is translated into Dalvik Executable (DEX) bytecode, which the Dalvik VM then interprets.

4. Application Framework

The Application Framework provides high-level APIs and classes that developers use to build apps. It acts as a bridge between the underlying runtime and the final application. Important components include:

• Activity Manager: Manages the lifecycle of applications and maintains the "back stack" to ensure smooth navigation between screens.
• Package Manager: Keeps track of all applications installed on the device.
• Window Manager: Manages the windows that serve as Java programming abstractions on top of lower layers.
• Content Providers: Allows one application to share data (such as contacts or addresses) with another.

5. Applications

The topmost layer consists of the actual software used by the end-user. This includes everything from system apps like "Settings" and "Contacts" to third-party games and browsers.

Development Tools: Emulators and IDEs

To build these applications, developers use Integrated Development Environments (IDEs) like Eclipse or Android Studio. Because testing on physical hardware for every possible device configuration is impractical, developers use the Android Emulator.

The emulator is a prototype that simulates hardware and software features, allowing developers to test apps without a physical device. It utilizes Android Virtual Device (AVD) configurations to represent specific device setups, such as different screen sizes or memory capacities.

Student Tip: While emulators are incredibly powerful for testing compatibility across different API levels and screen sizes, they have limitations. They cannot fully simulate physical constraints like battery depletion, real-world GPS accuracy, or hardware-attached peripherals like USB or Bluetooth devices.

Evolution and the Jelly Bean SDK

Android versions have historically been identified by dessert-themed codenames, such as Cupcake, KitKat, and Jelly Bean. The Jelly Bean (Android 4.1) release was a major milestone that introduced several transformative features:

• Project Butter: This initiative was designed to make the user interface faster and more responsive. It introduced "CPU Touch Responsiveness," which uses the speed and direction of a user's finger to predict movement and increase performance.
• Near Field Communication (NFC): Enabled two NFC-enabled devices to share data simply by tapping them together.
• Face Unlock: Improved security by allowing the device to unlock when it detects the user's face.
• Google Now: A context-aware information service that provides "just the right information at just the right time" via information cards (e.g., weather, transit, or sports).