aosp-part-device-support

Summarize AOSP Part XIV device support chapters 57–62 across architectures.

122|30|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-device-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aosp-part-device-support
Source: https://github.com/aospbooks/aosp-internal-book/tree/main/agents/claude/skills/aosp-part-device-support
Command: npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-device-support

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Part XIV consolidates cross-architecture device support references across ARM (32/64), x86_64, and RISC-V, the AVD emulator stack, enterprise device policy (DevicePolicyManager), automotive/TV/Wear stacks (CarService and vehicle HAL), Print Services, and the Camera2 pipeline, enabling engineering reasoning about platform coverage and compatibility.

Core Features & Use Cases

  • Comprehensive coverage of chapters 57–62, including architecture support, emulator, device policy, automotive/TV/wear, print services, and camera pipeline.
  • Clear mappings between architectures, ABIs, toolchains, and runtime considerations, plus concrete file paths and interfaces referenced in the skill content.
  • Real-world use cases: assess cross-architecture impact, plan integration strategies, and onboard new platforms using the chapter references as a guide.

Quick Start

Open the Skill content and skim Chapters 57–62 to locate architecture sections and subsystem references, then follow the listed file paths to explore the described interfaces.

Frequently Asked Questions about aosp-part-device-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does AOSP device support differ across ARM, x86_64, and RISC-V architectures?

AOSP device support maps specific ABIs, toolchains, and runtime considerations to ARM32/64, x86_64, and RISC-V architectures. It contextualizes cross-architecture platform coverage by documenting key architectural decisions and interfaces for each.

How do I navigate the AVD emulator stack and DevicePolicyManager in AOSP?

Navigate the AVD emulator stack and DevicePolicyManager by skimming AOSP chapters 57–62. Follow the listed file paths and interface references to explore enterprise device policy and emulator configurations.

Does AOSP CarService integrate with vehicle HALs for Android Automotive?

Yes, AOSP CarService integrates with vehicle HALs to support the Android Automotive form-factor stack. This integration enables engineering reasoning about automotive platform coverage and compatibility.

What is the Camera2 pipeline and how does it fit into AOSP device support?

The Camera2 pipeline is a core subsystem summarized within AOSP device support chapters. It provides concrete file paths and interfaces to contextualize camera design decisions across supported architectures.

Can I use AOSP references to onboard new platforms and plan integration strategies?

Yes, you can use AOSP chapter references to plan integration strategies and onboard new platforms. The references guide cross-architecture impact assessments using documented file paths and interfaces.

What AOSP subsystems are covered for Android TV and Wear form factors?

AOSP subsystems for Android TV and Wear are covered alongside automotive stacks and print services. These form-factor stacks provide mappings for runtime considerations and platform compatibility.