How do I install the Aosp Device Support skill?

Run npx skillmds@latest add aospbooks/aosp-device-support in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aosp Device Support safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aosp Device Support?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aosp Device Support free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aosp Device Support?

aospbooks (@aospbooks) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aosp Device Support by aospbooks — Agent Skill

Name: Aosp Device Support
Author: aospbooks

Aosp Device Support

AOSP Part XIV — Device Support. Use when reasoning about per-architecture support (ARM 32/64, x86_64, RISC-V, ABI matrix, toolchains), the QEMU-based Android emulator (AVD format, hardware acceleration, guest kernel), DevicePolicyManager (work profiles, fully-managed devices, COPE, enrollment), Android Automotive / TV / Wear (CarService, vehicle HAL, Leanback, TIF, Wear OS specifics), Print Services (PrintManager, IPP, PDF generation), or the Camera2 pipeline (Camera2 API, CaptureRequest/Result, camera HAL3). Chapters 59–62.

aospbooks c017084 2.2 KB Updated Sep 17, 2026

File contents

AOSP Part XIV — Device Support

How AOSP supports different CPU architectures, the emulator stack, enterprise device policy, and the form-factor-specific stacks (Auto, TV, Wear, Print).

Chapters in this Part

59-architecture-support.md — ARM (32/64), x86_64, RISC-V port, ABI matrix, per-arch toolchain and runtime considerations
60-emulator.md — QEMU-based Android emulator, AVD format, hardware acceleration (KVM/HAXM/HVF), guest kernel, Studio integration
61-device-policy.md — DevicePolicyManager, work profiles, fully-managed devices, COPE, restrictions, enrollment flows
62-form-factors.md — non-phone device form factors: Android Automotive (CarService, vehicle HAL) + the Software Defined Vehicle platform, Android TV (Leanback, TIF), Wear OS, and emerging Android XR
63-print-services.md — PrintManager, print services, IPP, default printer service, PDF generation
64-camera2-pipeline.md — Camera2 API, CameraDeviceImpl, CaptureRequest/Result, capture pipeline, camera HAL3

When to load which chapter

Question mentions ARM, x86_64, RISC-V, ABI, toolchains → 59-architecture-support.md
Question mentions emulator, AVD, KVM/HAXM/HVF, guest kernel → 60-emulator.md
Question mentions DevicePolicyManager, work profile, COPE, enrollment → 61-device-policy.md
Question mentions CarService, vehicle HAL, SDV, software defined vehicle, SOME/IP, Leanback, TIF, Wear OS, Android XR → 62-form-factors.md
Question mentions PrintManager, IPP, print service → 63-print-services.md
Question mentions Camera2, CaptureRequest, camera HAL3 → 64-camera2-pipeline.md

---name: aosp-device-supportdescription: AOSP Part XIV — Device Support. Use when reasoning about per-architecture support (ARM 32/64, x86_64, RISC-V, ABI matrix, toolchains), the QEMU-based Android emulator (AVD format, hardware acceleration, guest kernel), DevicePolicyManager (work profiles, fully-managed devices, COPE, enrollment), Android Automotive / TV / Wear (CarService, vehicle HAL, Leanback, TIF, Wear OS specifics), Print Services (PrintManager, IPP, PDF generation), or the Camera2 pipeline (Camera2 API, CaptureRequest/Result, camera HAL3). Chapters 59–62.---# AOSP Part XIV — Device SupportHow AOSP supports different CPU architectures, the emulator stack, enterprisedevice policy, and the form-factor-specific stacks (Auto, TV, Wear, Print).## Chapters in this Part- `59-architecture-support.md` — ARM (32/64), x86_64, RISC-V port, ABI matrix, per-arch toolchain and runtime considerations- `60-emulator.md` — QEMU-based Android emulator, AVD format, hardware acceleration (KVM/HAXM/HVF), guest kernel, Studio integration- `61-device-policy.md` — DevicePolicyManager, work profiles, fully-managed devices, COPE, restrictions, enrollment flows- `62-form-factors.md` — non-phone device form factors: Android Automotive (CarService, vehicle HAL) + the Software Defined Vehicle platform, Android TV (Leanback, TIF), Wear OS, and emerging Android XR- `63-print-services.md` — PrintManager, print services, IPP, default printer service, PDF generation- `64-camera2-pipeline.md` — Camera2 API, CameraDeviceImpl, CaptureRequest/Result, capture pipeline, camera HAL3## When to load which chapter- Question mentions ARM, x86_64, RISC-V, ABI, toolchains → `59-architecture-support.md`- Question mentions emulator, AVD, KVM/HAXM/HVF, guest kernel → `60-emulator.md`- Question mentions DevicePolicyManager, work profile, COPE, enrollment → `61-device-policy.md`- Question mentions CarService, vehicle HAL, SDV, software defined vehicle, SOME/IP, Leanback, TIF, Wear OS, Android XR → `62-form-factors.md`- Question mentions PrintManager, IPP, print service → `63-print-services.md`- Question mentions Camera2, CaptureRequest, camera HAL3 → `64-camera2-pipeline.md`

Frequently asked questions