Skip to content

Android

Saphira Linux androidDragon

Android development on Saphira with proper support: apk add android-tools installs ADB, fastboot and the platform tools (37.0.0_p1-r2) from the hatched repository, with Gradle and the JDK completing the build toolchain. Build here; run on the device the app was made for.

Available now from the hatched repository: apk add android-tools

Saphira Linux dragon mascot

Building on Saphira

Building an Android application on Saphira means using the SDK, build-tools and Gradle to assemble an APK or Android App Bundle. The output is a package destined for a phone, tablet or other Android device. This is a normal cross-target build: the host compiles and packages for a target it does not itself run.

# Assemble a release bundle for a device
./gradlew bundleRelease

Running on Saphira is a different thing

Running an Android application on Saphira would require an Android runtime or emulator on the Saphira host. Saphira does not provide that runtime. A phone app is built here and runs on the device it was made for; Saphira is the bench, not the device. This page does not claim that Android applications execute on Saphira, because that has not been built or tested as a Saphira feature.

WarningDo not expect to launch an Android app on Saphira itself. Use a real device or an emulator on a host that provides one, and drive it from Saphira with ADB over an intended connection.

Why the distinction matters

Treating build and run as one feature hides a real boundary: compiling and packaging for Android is a solved, ordinary Linux toolchain task; emulating or hosting the Android runtime is a separate, heavier capability that Saphira has not taken on. Stating the two separately keeps the documentation honest and keeps the build host focused on what it does well.