Exceptionally, this wiki is under maintenance.
You can continue to browse it to discover the STM32MP1 series and associated ecosystems (STM32 boards, embedded software, development tools, trace & debug tools...) but contributors can not improve their favorite articles, during phase.
Thank you for your understanding.
- Last edited one year ago ago
Android application frameworks overview
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.
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.