Android Overview

The Mediatek Android projects, provides the source code for Android, allowing developers and manufacturers to customize and build their own versions of the OS. Genio platforms,designed for high-performance and versatile applications,leverage Android to deliver robust and customizable Android experiences.

Genio Platforms

MediaTek’s Genio platforms provide a comprehensive range of solutions for Android IoT applications, from entry-level to high-performance devices. Each platform is designed to meet specific performance and connectivity requirements, ensuring that developers can choose the right solution for their IoT projects.

Genio platforms are a series of advanced hardware solutions optimized for various applications, including IoT, automotive, and consumer electronics. These platforms are equipped with powerful processors, extensive connectivity options, and support for multimedia and AI capabilities. By integrating Android, Genio platforms offer a flexible and scalable foundation for developing innovative Android-based solutions.

  • Some supporting packages, based on the collection of Android project, are patched for compatibility.

  • Certain hardware drivers and supporting software are provided as proprietary packages that allow redistribution to be used with MediaTek Genio chipsets. Please read the license terms before using these components.

../../_images/android_architecture.png

Major components in Android

MediaTek Single System Image (MSSI)

This section will provide an explanation of the MediaTek Single System Image (MSSI).

The goal of MSSI is to separate the platform-independent common parts into the system image (+product image), while the platform-specific parts converge into the vendor image. This achieves a single System Image that can simultaneously support multiple platforms (Vendor image), thereby saving the cost of developing and maintaining multi-platform systems.

System module

This refers to the modules that will be compiled into system.img/product.img in the system project, including AOSP & MediaTek’s System Modules.

  • All jar modules & almost all APK modules

  • Some native so/bin

  • Configuration/resource files (e.g., *.prop file, *.xml)

Vendor module

This refers to the modules that will be compiled into non-system.img/product.img in the vendor project. These images include vendor.img, odm.img, recovery.img, boot.img, as well as other images defined by MediaTek (e.g., MD, scp, sspm, tee, etc.).

  • AOSP provides libraries used by MediaTek vendor modules

  • AOSP implement vendor modules (e.g., AOSP implemented HAL)

  • MediaTek implemented HALs

  • Sub-systems (e.g., consys, MD, tinysys, tee, etc.)

  • Configuration/resource files (e.g., *.prop, *.xml)

MSSI Interface Policy

For MSSI to be compatible with vendor images for multiple platforms, the Vendor Interface it uses needs to be common, otherwise it would be difficult to achieve this.

../../_images/mtk_single_system_image.png

MediaTek Single System Image(MSSI)

The usual requirements are:

  1. The interface should exist on all platforms.

  2. If a platform does not support it, its related interface should still be callable, but it needs to return an exception value for dynamic selection.