How lineageos/android_vendor_lineage works
Main Components
a. Build System Layer
• Build/ directory components including core, soong, and target
• Tools/ and vars/ directories for build configuration
• Release/ directory for release management
b. Device Support Layer
• Overlay/ directory structure for device-specific customizations
• Prebuilt/ components
• Vars/devices connection to specific device support
c. System Customization Layer
• Config/ directory containing various configuration types
• Bootanimation/ and charger/ customizations
• Spn/ (Service Provider Name) configurations
Component Relationships
• Build System → Device Support (compilation flow)
• Device Support → System Customization (device-specific modifications)
• Config → Overlay (system modifications)
• Release → Build System (release management)
Architectural Patterns
Following patterns:
• Layered architecture (build → device → customization)
• Modular device support (overlay system)
• Configuration management (config files)
• Build automation (workflows)
Key Technologies
• Android build system (soong)
• Device Tree Overlays (RRO/OMS)
• Build configuration (Android.bp, Android.mk)
• Release management tools
Implementation Details
• Component name
• Key subcomponents
• Primary responsibilities
• File types handled
Additional Elements
Include:
• GitHub workflow integration (.github/workflows)
• Build artifact generation paths
• Configuration inheritance flows
• Device-specific customization paths
This system design should help developers understand how LineageOS components interact to create a custom Android distribution that can be built for multiple device targets while maintaining consistent customization capabilities.