Hokkaido on Android: APK, drivers and the two engines
Latest release
android-0.7.1Published 2026-11-19· 1 package below
Copies a prompt your AI agent can run to install Hokkaido.
Which package should I choose?
Each release ships one APK named for the android-* tag. Install it and allow installs from the browser or file manager when Android asks. The android-latest prerelease rebuilds on every change to the development branch, newest fixes and newest bugs together. An installed copy updates in place and keeps its games, saves and settings.
| Package | Architecture | Size |
|---|---|---|
| app-mainline-release.apk ↗ | Android | 77.3 MB |
What this build needs
An arm64 phone with Android 13 or newer and a Vulkan 1.3 driver. The app manages GPU drivers itself: Xclipse phones take the custom RADV build through its driver manager, Snapdragon phones a patched Adreno driver, and the embedded Banana Native engine requires the custom build outright on Xclipse. Logs for problem reports live in Android/data/dev.lichii.android/files/ (log/ for its own engine, logs/ for Banana Native).
Getting started
Check your phone
Confirm an arm64 device on Android 13 or newer with Vulkan 1.3 support.
Get the APK
Download from the upstream GitHub releases page. The android-latest pre-release updates in place and keeps games, saves and settings.
Load your own game
Use dumps from your own legally owned copy. The README notes game status varies per title and recommends 0.5x resolution on the main engine.
Troubleshoot
Upstream documents diagnostic switches through a files/env.txt file, early shader pop-in in Banana Native sessions and pink distant textures in some Ocarina of Time areas.
Common problems
-
The phone reports Vulkan 1.1 on a Snapdragon 8 Gen 1 tablet
Some stock drivers advertise an older Vulkan. Install a Turnip build through the app's GPU driver manager. Settings alone cannot meet the requirement.
-
A black picture on a Mali phone in one game
The stock driver is the cause, and players report faux123's PanVK driver draws correctly through the same manager (issue 22).
-
Games close during play
Android kills apps for memory, so close other apps before starting. The repository's tested-devices table is the honest baseline: other phones may work untested.
-
An Xclipse phone runs slowly
Install the custom RADV build. Samsung's own driver works but is slower on these phones, and it lacks the memory maps Banana Native needs.
How it differs
Hokkaido is the Android entry of the Eglantine lineage and the only catalog project carrying two engines: its own emulator and an embedded Banana Native, picked per game, sharing screens, driver, saves and settings. It began as Lichii for Android and kept in-place updates through the rename before 0.5.0.
Recent upstream releases
- Hokkaido 0.7.1 ↗ Published 2026-11-19 · 1 package
See every release on the upstream page ↗
Last checked 2026-11-22. Release data fetched 2026-11-22. A release sync refreshes metadata from upstream; it does not re-verify compatibility.
Download FAQ
What is android-latest?
A prerelease rebuilt automatically from every development change. Stable tags install over it and keep your data.
Will it run on my phone?
The repository lists its tested devices: Samsung Xclipse phones with the custom RADV build and a Snapdragon 8 Elite with a patched Adreno driver. Anything else is untested, and Mali phones need a community driver for at least one game.
Before installing
- Choose the engine per game in Game properties
- Auto picks Banana Native where its profiles call a game playable and its own engine for the rest.
- Run a game's first Prepare on the charger when the Banana Native engine handles it.
- Check logs for personal information before uploading, and never attach games, keys or account data.