How google/android-riscv64 works
Project type and purpose
• This is *not* a code-heavy application but rather a *meta-project* for tracking, discussion, and documentation of Android support on the RISC-V 64-bit architecture within the AOSP ecosystem.
• Its purpose is to centralize issue tracking, document build/test instructions, and coordinate contributions via AOSP.
File structure
• Top level only contains:
• LICENSE, README.md
• docs/ (with contributing and code-of-conduct)
• No src/ or frontend/backend directories — this is purely documentation and coordination.
• No build scripts here; all build lives in AOSP.
README for additional insights
• Describes:
• Where the real work happens (AOSP upstream)
• How to download, configure, and build AOSP for riscv64
• Use of Cuttlefish (QEMU-based emulator) to run ART (Android Runtime) and shell tools
• How to connect (adb, VNC) and submit patches (mailing list, AOSP contribution process)
a. Main components to show:
• GitHub “Android/riscv64” documentation repo
• AOSP upstream repository (platform/system, build, external, etc.)
• Developer’s Host Build Environment (Linux) with cross-toolchain
• Cuttlefish emulator (QEMU) instance
• Android runtime components inside emulator (ART, shell & utilities)
• Android NDK (provisional riscv64 ABI)
• External services: SIG-Android mailing list, Google’s issue trackers, AOSP Gerrit
b. Relationships and interactions:
• Developer clones docs repo and reads instructions
• Developer runs repo sync to fetch AOSP source
• Build environment compiles AOSP for riscv64 (invoking build/envsetup.sh, lunch, make)
• The built system image is fed into Cuttlefish (launch_cvd)
• Within emulator, ART and shell tools execute; developer connects via adb/vnc to test
• Bugs/issues flow from developer → GitHub issues / SIG-Android mailing list → AOSP Gerrit → code reviews → AOSP master
• NDK updates flow from AOSP into Android ABIs documentation
c. Architectural patterns/design principles:
• *Separation of concerns*: documentation vs. code hosting
• *Upstream-downstream flow*: all patches go upstream to AOSP, not via this GitHub repo
• *Emulation layer*: cuttlefish/QEMU abstracts hardware
• *Modular Android layers*: build system, runtime (ART), shell utilities, libraries
d. Key technologies/frameworks:
• AOSP build system (Soong/Bazel-like, Android.bp)
• Cuttlefish emulator (QEMU 8.1+)
• ART (Android Runtime)
• Android shell and core libraries
• adb, vncviewer for connectivity
• RISC-V 64 toolchain (gcc/clang cross-compilers)
• Mailing list infrastructure (lists.riscv.org) and Google Gerrit