The charger monitor component is located at adk/src/domains/power/charger_monitor.
Application-specific folders (e.g. \earbud) The application folders, e.g. \earbud , contain the application specific code and workspaces. Structure Taking \earbud as an example, application-specific folders use this structure: \earbud \src \workspace
The common app task component is located at adk/src/common/app_task.
The Goals Engine component is located at adk/src/topologies/common/goals_engine.
The handset service is located at adk/src/services/handset.
The Handover Decision Making Algorithm (HDMA) component is located at adk/src/services/peer/hdma.
The core Headset component is located at adk/src/topologies/headset_topology/procedures.
The Headset topology is located at adk/src/topologies/headset_topology.
The ADK application framework follows certain rules that are triggered by events to achieve certain goals. Events, Rules, Goals, and Procedures build the Bluetooth topology and ensure it works in a specific way.
Enumerations The naming convention for enumerations is the same as in original VM standard, but doxygen comments must be used. There is no difference between local and public (non-message) enumerations.