Hokkaido
Switch 2 emulator for Android, called Lichii for Android until version 0.5.0 per the upstream README. The README documents an arm64 phone with Android 13 or newer and Vulkan 1.3, with tested device notes for Exynos Xclipse and Snapdragon Adreno hardware. APKs publish through the upstream GitHub releases page, including an android-latest pre-release rebuilt from every commit.
- Android
Getting started
Check your phone
Hokkaido needs an arm64 phone on Android 13 or newer with Vulkan 1.3. If your stock driver reports a lower Vulkan version, install a newer driver such as a Turnip build for Adreno through the app's GPU driver manager.
Install the APK
Download app-mainline-release.apk from the latest android-* release and install it. You may need to allow installs from your browser or file manager. Installed copies update in place and keep their games, saves and settings. The android-latest pre-release rebuilds from every change and is for testing.
Add your games and a GPU driver
Games, keys and firmware are not included. Use dumps from your own legally owned copies. Xclipse phones should install the custom Mesa RADV build for Xclipse through the GPU driver manager, Snapdragon phones the 8gen V39 Patched Adreno driver.
Pick the engine and settings
Open Game properties and choose the engine: Auto picks Banana Native for profiled-playable games. Set 0.5x resolution on the Hokkaido engine, keep Handheld mode and the NCE CPU backend, and close other apps so Android does not kill the game on low memory.
Prepare Banana Native packs on a computer
Packing on a computer is faster than on the phone. Run scripts/bananative.bat on Windows or scripts/bananative.command on macOS, pick the game folder or .nup, then copy the pack from <title ID>-work/android-pack next to the game on the phone and use Import pack.
Collect a log when something breaks
The Hokkaido engine writes Android/data/dev.lichii.android/files/log/eden_log.txt. Diagnostic switches go into env.txt as KEY=VALUE lines. Check logs for personal information before uploading, and include your phone model, Android version, GPU driver and engine in issue reports.
Game compatibility
-
The Legend of Zelda: Ocarina of Time -
Pokémon Pokopia -
Fire Emblem: Fortune's Weave -
Orbitals -
Fast Fusion
Support detail for each title lives on its game page, with its own last-checked date.
Overview
Hokkaido is a Switch 2 emulator for Android, maintained on GitHub by pavelgajdo on the nx2 branch. The README records that the project was called Lichii for Android until version 0.5.0 and continues the work of yuzu, Sudachi, Eden, Eglantine and Lichii. Since version 0.7.0 it also embeds a second engine, Banana Native, which runs game code natively on the phone. APKs ship through android releases on GitHub, and an android-latest pre-release rebuilds from every commit.
System and game requirements
- An arm64 phone with Android 13 or newer and Vulkan 1.3, per the upstream README
- games, keys and firmware are not included and must come from your own console
- spare memory headroom, since Android may close games when the phone runs low
Features described by the developer
- Per the project's own documentation: an arm64 Android build requiring Android 13 or newer and Vulkan 1.3
- tested device notes covering Samsung phones with Exynos 2600 and 2400 chips and Xclipse GPUs
- a tested Snapdragon 8 Elite device with an Adreno GPU running a patched driver
- a custom Mesa RADV build used on Xclipse phones
- an embedded Banana Native engine since version 0.7.0, with the first prepare step documented as taking a few minutes
Related projects
What do the status and evidence badges mean?
Status groups
| Public build | The project provides a directly downloadable Switch 2 build. |
|---|---|
| Early release | A public release with limited testing or known issues. |
| Experimental / source | A proof of concept, or a project you build yourself from source. |
| Demo | A small homebrew demo or a developer showcase. |
| Reference | Development information, runtime context or an auxiliary tool. |
Evidence levels
| developer_reported | The claim comes from the project's own documentation, changelogs or release notes. |
|---|---|
| project_focus | The project describes this as its goal. It is not necessarily working today. |
| unverified | We have not yet confirmed the claim from a primary source. |
Reported capabilities apply to the specific build and settings the project tested. A release sync on this site never re-verifies compatibility.