Actinis Chimera
Coming soon

arm64 on x86_64, through Native Bridge.

A Native Bridge for Android. arm64 apps run on x86_64 hosts through Chimera's interpreter and translation tier, using Android's Native Bridge interface.

chimera · native bridge · build + runtime
# AOSP device build · include Chimera as the Native Bridge
building libchimera.so
linking into system image
image ready · flashable
$ adb logcat · runtime, after boot
I nativebridge detected foreign ABI · arm64-v8a
I nativebridge loading via Chimera
app running on x86_64 · unmodified
$_
What it is
// chimera.md

Chimera is a Native Bridge for Android: arm64 app code is loaded through Android's own guest linker and executed on x86_64 by Chimera's interpreter and translation tier, without a separate emulator beside the runtime.

It implements the Native Bridge interface Android has shipped for years, so x86_64 Android systems can integrate arm64 app compatibility as part of their platform.

Chimera is layered: a shared host runtime core plus thin platform frontends. The finished product has an Android/bionic frontend for AOSP devices and a Linux/glibc frontend so Drion can host arm64 Android apps on Linux with the same translator.

Under the hood

One runtime core, thin platform frontends

01 · Shared core

Platform-neutral runtime

Runtime lifecycle, guest ELF loading, namespace policy, proxy dispatch, and execution-engine coordination live in a single core that doesn't depend on Android properties or glibc launcher assumptions.

02 · Android frontend

NativeBridge frontend

An Android/bionic frontend exports libchimera.so as the system Native Bridge and ships into the system image alongside the guest ARM64 payload. The interface stays Android-native, so platform integration is explicit and testable.

03 · Linux frontend

Host Android apps from Drion

The Linux/glibc frontend will let Drion use the same translator to run arm64 Android apps on Linux hosts. One translator, two host worlds — a direct bridge between the Actinis runtime products.

04 · Correctness first

Interpreter before translation

Chimera brings up an interpreter first, then a translation tier with code caching. We're optimizing for apps that load and run unmodified — not for synthetic benchmarks.

05 · Scope, by design

Not trying to be QEMU

ARM64 guest, x86_64 host, Android-shaped guest payload. Not a generic ARM64 userspace emulator. No ARM32. No x86 guest.

Who it's for

Built for x86_64 Android where arm64 app compatibility has to be part of the platform.

01

x86_64 Android builds

AOSP-based device builds and emulator products that need arm64 app compatibility on x86_64 hardware with platform-owned integration and validation.

02

Cloud Android operators

Hosts running Android on x86 servers — including ourselves — that need predictable system-image integration and owned compatibility behavior.

03

Android platform forks

LineageOS-class projects, research platforms, and vendor-controlled builds that need arm64 compatibility as part of their own platform stack.

Development status

Active development. No public release yet.

Chimera is being actively built, but it is not available as a public release today. Join the waitlist for release updates.

// not released yet
Waitlist

Know when Chimera ships

We'll email when there is a meaningful product update or preview path. No drip campaigns.