Android application frameworks overview

Revision as of 16:17, 8 February 2022 by Registered User (Merge articles)
Deletion.png This page is a candidate for deletion.
The supplied reason is: Remove Android related pages, only available on v2 .
-- Registered User (-) 15:28, 7 February 2022 (CET).
Wiki maintainers: remember to check if anything links this page before deleting it.

The diagram below gives an overview of the Android application frameworks (Linux user space components) that rely on Linux kernel.

This Linux kernel is based on the Android Common Kernel[1] following Google recommendation for its configuration[2].


It shows the main components grouped per functional domain, however it is not exhaustive.



OpenSTLinux OE legend.png


The Android framework is structured in several layers:

  • hardware interfaces providing a standard way to configure the underlaying driver, based on the Android HIDL (Hardware Interface Definition Language) mechanism
  • the Android core (ART virtual machine, useful daemons including vold, adbd, and debuggerd, and system services)
  • Android services (providing interfaces to the application = SDK)
  • Android applications (including the launcher)

The Android services are often implemented partly in native cpp, and partly in Java. The JNI (Java Native Interface) IPC mechanism is available to allow communication between the two worlds.

In addition to the standard Android services, a proprietary coprocessor service for Android has been introduced (for development purposes only). The CoproService is composed of two parts:

  • firmware management (check running firmware, start/stop firmware, get/set the firmware name)
  • TTY management (open/close and read/write the TTY interface). You must implement your own protocol on top of this.

1. References[edit source]