Tech Nexus

Tech Nexus is your go-to hub for cutting-edge insights and technical knowledge sharing. Join our community of experts and enthusiasts to stay ahead in the ever-evolving world of technology.

Member-only story

Add New Product in AOSP Source Tree

--

image copied from internet

Building on the foundation of our previous discussions about compiling Android’s built-in products for verification, we now shift our focus to the process of adding our own products. Adding a new product allows you to customise the Android system for your specific device and use case, and that it also enables you to contribute to the open source community by sharing your product with other developers.

Adding a new product to the Android Open Source Project (AOSP) source code can be a daunting task, but it doesn’t have to be. In this article, we’ll guide you through the process of creating your own product step by step. Generally speaking, a product has four elements:

  1. AndroidProducts.mk: This file specifies the product configuration and outlines crucial details like the built-in software modules defined by PRODUCT_MAKEFILES in AndroidProducts.mk.
  2. BoardConfig.mk: This file contains hardware-related configurations, encompassing elements such as chip hardware settings and partition configurations. It’s pivotal for tailoring your product’s hardware requirements.
  3. Product.mk: This file encapsulates instructions pertaining to software modules and complements the definitions found in AndroidProducts.mk i.e. it contains software-related configuration of a product, such as which built-in software modules are specified…

--

--

Tech Nexus
Tech Nexus

Published in Tech Nexus

Tech Nexus is your go-to hub for cutting-edge insights and technical knowledge sharing. Join our community of experts and enthusiasts to stay ahead in the ever-evolving world of technology.

Budhdi Sharma
Budhdi Sharma

Written by Budhdi Sharma

As an AI Enthusiast & AOSP/AAOS/XROS/RTOS Engineer, I specialize in creating robust frameworks, and systems that seamlessly integrate with embedded systems.

Responses (1)