How frosty-aosp/vendor_frosty works
Frosty is an Android ROM configuration and customization repository: its README describes it as containing configuration files and modules. The apparent maintainer workflow is to select device or form-factor configuration and build a customized system image. The tree shows configuration, overlays, bundled media, and runtime modules, but the README and sampled source do not establish how the build connects them; those relationships are therefore not asserted here.
Main entry points: generate.py Ad host generation · main.cpp OverlayFS control · bfqio.c BFQ I/O priority · .hosts Hosts sources
Components 20
Product configuration
- Board configuration
config/BoardConfigLineage.mk - Product variants
config/common.mk - Package selection
config/frosty_packages.mk - Release settings
release - Permissions
config/permissions
System customization
- Resource overlays
overlay - Ad host generation
adaway/generate.py - Hosts sources
adaway/.hosts - Generated hosts file
adaway/.hosts
Bundled resources
- System audio
audio - Google audio
google - Boot animation
bootanimation - Charger UI
charger - Prebuilt assets
prebuilt/common
Runtime modules
- OverlayFS control
disable-overlays/main.cpp - BFQ I/O priority
libbfqio/bfqio.c - BFQ I/O API
libbfqio/include/bfqio/bfqio.h
Other components
- ROM maintainer
- Device partition metadata
- BFQ I/O cgroups
Connections 4
- Ad host generation → Hosts sources: reads sources
adaway/generate.py - Ad host generation → Generated hosts file: writes hosts
adaway/generate.py - OverlayFS control → Device partition metadata: updates metadata
disable-overlays/main.cpp - BFQ I/O priority → BFQ I/O cgroups: writes task IDs
libbfqio/bfqio.c