hal-vendor-interface-expert

To ensure AIDL compliance when adding an Android HAL interface, you must align binder domains, VNDK boundaries, and service registration with verified AIDL definitions. This process involves checking VINTF manifest declarations and frozen Android.bp versions to prevent interface violations.

Vendor binder calls are misrouted during HAL migration due to misaligned binder domains and incorrect VNDK boundary scoping. Resolving this requires inspecting AIDL versions, querying registered HALs, and enforcing binder domain restrictions across hardware/interfaces/ and vendor directories.

You can check VNDK membership for vendor modules by using guided tooling commands to inspect the system/vndk/ directory. This prevents Treble breaches by explicitly forbidding vendor modules from linking to non-VNDK libraries during HAL development.

The best way to declare VINTF manifests for Treble compliance is to use targeted commands to find VINTF manifests and verify them against frozen interface versions. This ensures hardware and vendor interface boundaries remain strictly scoped and compliant.

You cannot add new HIDL interfaces when migrating Android HALs because operational guardrails explicitly forbid this action. You must instead align with verified AIDL definitions and regenerate HAL APIs when bumping interface versions.

To bump interface versions and regenerate HAL APIs in Android.bp, you inspect AIDL versions and execute commands to regenerate the APIs. This maintains frozen Android.bp version requirements and ensures VINTF manifest declarations remain valid.