aosp-part-runtime

Name: aosp-part-runtime
Availability: InStock
Author: aospbooks

Analyze ART runtime and Native Bridge architecture questions.

122|30|Updated Mar 18, 2026

Search Tags:#jit #aot #garbage-collection #native-bridge #art-runtime #dex2oat #berberis

Ready to run

npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-runtime

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aosp-part-runtime
Source: https://github.com/aospbooks/aosp-internal-book/tree/main/agents/claude/skills/aosp-part-runtime
Command: npx skills add https://github.com/aospbooks/aosp-internal-book --skill aosp-part-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ART runtime understanding and the Native Bridge mechanics enable reasoning about how Android apps execute, optimize, and cross-ISA translate.

Core Features & Use Cases

ART architecture overview: core components like Runtime, ClassLinker, GC, JIT, AOT, and app images; Dex caches; JNI bridge.
Binary translation insights: Berberis, Houdini, cross-architecture execution, including interpreter, lite translator, and JIT paths.
Use Case: When diagnosing startup latency or performance bottlenecks in ART-powered apps or planning cross-ISA deployment strategies.

Quick Start

Load Chapter 18-art-runtime.md and skim its ART runtime sections to ground yourself.

Frequently Asked Questions about aosp-part-runtime

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

FAQPage Schema

How does ART runtime handle AOT and JIT compilation for Android apps?▼

ART runtime uses dex2oat for ahead-of-time compilation and a JIT compiler for runtime optimization. It generates oat, vdex, and odex files to improve startup latency and execution speed for Android applications.

What is the Native Bridge and how does cross-ISA translation work in Android?▼

The Native Bridge enables cross-ISA translation using components like Berberis and Houdini. It supports binary translation through interpreter, lite translator, and JIT paths to execute apps across different architectures.

How do I diagnose startup latency and performance bottlenecks in ART-powered apps?▼

Diagnose ART performance issues by analyzing runtime components like ClassLinker, GC, and app images. Understanding dex2oat compilation and JNI bridging helps identify specific bottlenecks causing startup latency.

Can I use Berberis for cross-architecture deployment on Android?▼

Berberis supports cross-architecture execution in Android via its interpreter, lite translator, and JIT translation paths. It handles safety and compatibility checks required for deploying apps across different instruction set architectures.

Why does garbage collection behavior change during ART runtime execution?▼

ART garbage collection behavior adapts during runtime to manage memory allocation and app execution efficiency. The GC component interacts with class loaders and dex caches to reclaim memory from objects no longer in use.

What are the limitations of Native Bridge translation for cross-ISA Android apps?▼

Native Bridge translation faces limitations in performance overhead and compatibility constraints when executing cross-ISA apps. Safety and compatibility checks within the translation pipeline may restrict certain native library operations.