Android (AOSP)

Only for experiments that check whether the Android framework boots on RISC-V — don't treat it as a usable system.

Based on

AOSP (Linux kernel + Android framework)

Upstream

The AOSP mainline keeps a riscv64 target (build/target/product/aosp_riscv64.mk, module_riscv64.mk) but only validates it on the Cuttlefish virtual device; in 2024 the Android Common Kernel/GKI removed RISC-V support, and Google says work continues in AOSP.

Versions

Android 17 (AOSP, 2026-06) · main (trunk_staging)

Doc languages

en

Checked

2026-11-01

• QEMU virt (virtual machine) Official Cuttlefish (cvd) is the only official way to run it and needs qemu >= 8.1 (9.0+ is steadier for the V extension)

• google/android-riscv64 (status, lunch targets, Cuttlefish steps) Doc en
• AOSP: Building Android Doc en
• AOSP: Cuttlefish usage (the only way to run riscv64) Doc en

• No official phone/dev-board images, only the emulator
• The NDK riscv64 ABI is still provisional, so .so files you build now may not be compatible later
• Booting to the desktop takes about 10 minutes even on a fast host
• With RISC-V gone from ACK/GKI, vendors get no long-term kernel support, which rules out mass production

• source.android.com/docs/setup/download
• github.com/google/android-riscv64
• source.android.com/docs/setup/build/building
• source.android.com/docs/devices/cuttlefish/get-started

The full source list and how each claim is judged: Sources