Lichii & Fritchii on Android: APK Status & Handheld Guide

Neither zortos293/Lichii nor Frizti/Fritchii publishes an official Android APK. Mainline Lichii ships desktop builds for Windows, Linux and Apple Silicon macOS only — its build 316 notes state plainly that “Lichii ships no Android build” (#1552) — and Frizti’s Fritchii fork ships Windows x64 .zip archives only. Because searches for “Lichii Android”, “Lichii emulador Android” and “Fritchii Android” are heavily targeted by fake lichii.apk malware pages, this guide breaks down the exact upstream status, how lichii-linux-aarch64 relates to ARM64 Linux handhelds vs Android, and which verified alternatives actually exist on November 17, 2026.

Advertisement

Lichii Emulator Guide / Android status & APK guide

Nintendo Switch 2 Joy-Con controllers in their grip beside the empty dock

Security warning: Never install a file named lichii.apk or fritchii.apk from third-party APK mirrors, YouTube descriptions, Telegram channels or “Switch 2 APK + BIOS” blogs. Neither upstream project distributes an Android package, and no legitimate project bundles keys, firmware or games.

Official Android status: Lichii vs Fritchii vs forks

Every project in the Lichii / Eglantine Switch 2 family publishes its code and binaries openly on GitHub, making it straightforward to verify what exists and what does not:

Advertisement
Project / packageRepositoryOfficial Android APK?What actually ships & why
Lichii (mainline)zortos293/LichiiNo official APKShips 12 desktop files (Windows x86_64, Linux x86_64, Linux ARM64, macOS ARM64) in build 316. Keeps inherited Eden Kotlin source in src/android/ (3.1%), and build 316 notes confirm no Android build is released (#1552).
Fritchii (Frizti)Frizti/FritchiiNo Android buildShips Windows x64 Fritchii-v5.8.4-Windows-x64.zip (72.6 MB) only, tuned exclusively for desktop Ocarina of Time. Zero Android or ARM packages exist.
Lichii Linux ARM64zortos293/LichiiNot an Android applichii-linux-aarch64-pgo.AppImage (137.8 MB) & .tar.gz (148.7 MB) are desktop GNU/Linux ARM64 binaries (glibc 2.39+), not Android APKs.
Hokkaido (community fork)pavelgajdo/HokkaidoIndependent fork APKSeparate open-source GPL-3.0 fork by pavelgajdo (called “Lichii for Android” until 0.5.0). Publishes app-mainline-release.apk (79.9 MB in android-0.7.0, package ID dev.lichii.android) on GitHub Releases.
Third-party “Lichii.apk” sitesNon-GitHub domainsFake / malware riskUnrelated lookalike sites bundling adware, WebView survey traps, trojans or fake “Switch 2 BIOS + keys” archives.

How lichii-linux-aarch64 relates to ARM64 handhelds vs Android

A common point of confusion on GitHub Releases is seeing lichii-linux-aarch64-pgo.AppImage and assuming aarch64 means Android phones (since modern Android phones also use 64-bit ARM processors). Under the hood, they target completely different operating-system stacks:

  • GNU/Linux ARM64 (glibc 2.39+) vs Android (Bionic): lichii-linux-aarch64.AppImage and lichii-linux-aarch64-pgo.tar.gz are compiled on Ubuntu 24.04 ARM64 against GNU glibc 2.39+, desktop Qt 6.8.3 (X11 / Wayland), SDL3 and desktop Vulkan loaders. Android uses Google’s Bionic C library, Binder IPC and SurfaceFlinger — Android’s package installer cannot install an .AppImage, and Android’s shell cannot execute a glibc binary directly.
  • Where lichii-linux-aarch64 actually works: ARM64 Linux single-board computers, ARM64 Linux laptops, and dual-boot ARM64 handhelds running a mainline desktop distribution (such as Ubuntu 24.04 ARM64, Fedora 40+ ARM64 or Arch Linux ARM with glibc 2.39+, Mesa Turnip / PanVK Vulkan 1.3 drivers, and ideally 12–16 GB RAM). Installation steps are in our Linux & macOS guide.
  • Why Termux (proot) and Winlator struggle on Android phones:
    • Termux proot-distro: running lichii-linux-aarch64 inside unprivileged proot intercepts every filesystem syscall, breaks ARM64 fastmem / NCE page-table signals, and contends with Android’s phantom-process and low-memory killer when a Switch 2 game requests its 12GB DRAM layout.
    • Winlator / MiceWine / Box64 with Fritchii-v5.8.4-Windows-x64.zip: trying to run Frizti’s Windows x64 lichii.exe inside an Android x86-64 container translates Switch 2 ARM64 guest code → x86-64 JIT → Box64 ARM64 host code while routing Vulkan through winevulkan → Turnip. Even on flagship 16 GB Snapdragon phones, compiling Fritchii’s 120,461 shaders or loading Hyrule Field exhausts address space or triggers driver resets.

How to spot fake lichii.apk and fritchii.apk malware sites

Copycat domains buy rankings for “lichii android apk”, “emulador lichii android” and “fritchii apk download”. On desktop, open issue #545 on zortos293/Lichii already documented a lookalike domain (lichii.org) serving a modified archive that spawned node.exe from %TEMP%; mobile scam sites use the exact same playbook. Close the tab immediately if you see any of these signs:

  1. The file is named lichii.apk, fritchii.apk or switch2-emulator.apk: neither zortos293/Lichii nor Frizti/Fritchii produces an APK, and even the independent Hokkaido fork names its GitHub asset app-mainline-release.apk.
  2. Small 8–30 MB file size or “cloud Switch 2” claims: fake APKs are usually tiny WebView wrappers or dropper stubs that demand Accessibility, SMS, Notification or “Install unknown apps” permissions to push adware or steal session tokens.
  3. “Human verification” surveys, Telegram/Discord gates, or paid “VIP early access”: upstream’s README states that every legitimate release is free, public, and hosted directly on GitHub Releases without surveys or passwords.
  4. Bundled “Switch 2 BIOS”, prod.keys, firmware or preloaded ROMs: legitimate open-source emulators never include copyrighted Nintendo system files or games. “All-in-one APK + BIOS” downloads are a classic malware lure (more checks on Is Lichii safe?).

Verified Android fork and handheld alternatives

Depending on the device in your hands, you have two genuine, auditable open-source options:

  • On an ARM64 Android phone or tablet (Android 13+, Vulkan 1.3, 8–16 GB RAM) → Hokkaido (pavelgajdo/Hokkaido):
    • Maintained openly under GPL-3.0 by pavelgajdo as a GitHub fork of zortos293/Lichii (258 stars, 26,193 downloads across 12 releases + rolling pre-release on November 17, 2026).
    • Newest release android-0.7.0 (November 17, 2026) publishes app-mainline-release.apk (79.9 MB, SHA-256 verified on GitHub) under package ID dev.lichii.android, embedding Banana Native v0.3.41 as a selectable per-game second engine alongside Hokkaido’s engine plus 0–3 Frame skip (#19) and Switch 2 RAM cleanup on game stop (#634).
    • Realistic expectations from Hokkaido’s own notes: requires 0.5x resolution in Handheld mode with NCE and a custom Turnip (Snapdragon Adreno) or Mesa RADV Xclipse driver; Pokémon Pokopia reaches ~40 FPS on 8–12 GB phones with its sky fixed in 0.6.6 (#17), Fast Fusion enters races in 0.6.5+, Fire Emblem: Fortune’s Weave is playable via temporal FSR 3.1 (0.6.2+), and Ocarina of Time reaches 60 FPS in hardware-decoded AV1 movies and 15–20+ FPS in Kokiri Forest (16 GB RAM recommended since 0.6.5 so Android does not kill the app).
  • On handheld gaming PCs (Steam Deck OLED, ASUS ROG Ally X, Lenovo Legion Go) → Desktop Lichii, Fritchii or CheezyEmu:
    • x86_64 handhelds with 16–24 GB unified RAM run full desktop Switch 2 emulators at 30–60+ FPS without mobile memory killers: use native Linux Lichii build 316 or CheezyEmu on SteamOS/Bazzite, or run Windows Fritchii natively on ROG Ally / Legion Go (and via Proton on SteamOS — see Steam Deck setup).

Recommended SDL3 controllers

Lichii reads gamepads through SDL3 (including HID command 300 motion). Standard Xbox pads have no gyroscope, so games that use motion aiming or tilt steering (such as Mario Kart World or Ocarina of Time) need a DualSense or aSwitch-style pad, while TMR/Hall sticks prevent drift:

ControllerGyro in Lichii (SDL3)Why pick itAmazon
Sony DualSenseYes (USB-C & Bluetooth)Confirmed working in Mario Kart World (#523); full SDL3 gyro on Windows, macOS & LinuxView on Amazon →
GameSir Cyclone 2Switch mode / PCTMR electromagnetic sticks (no drift) + Hall/micro-switch triggers for PC & Switch 2View on Amazon →
8BitDo Ultimate 2 BluetoothSwitch modeNintendo ABXY layout, TMR sticks and charging dock for Switch 2 & WindowsView on Amazon →
Xbox Wireless ControllerNo gyroPlug-and-play XInput on Windows & Steam Deck (named in upstream Deck notes)View on Amazon →

As an Amazon Associate, this site earns from qualifying purchases. Full button profiles and Linux udev rules: controller setup guide.

Advertisement
A heap of fresh lychees with their pink, bumpy shells, on a white ground
Lychees (Litchi chinensis).

Common questions

Does an official Lichii or Fritchii Android APK exist?

No. Neither zortos293/Lichii nor Frizti/Fritchii publishes an official Android APK. The Lichii build 316 release notes explicitly state “Lichii ships no Android build” (#1552), and every Fritchii release is a Windows x64 .zip only. Any website offering an “official Lichii.apk” or “Fritchii.apk” is fake.

Why is there an android folder inside zortos293/Lichii on GitHub?

Lichii inherited Eden and yuzu’s Kotlin/JNI src/android/ directory (~3.1% of repository code), so the source files remain in the tree, while zortos293/Lichii’s CI workflow (release-binaries.yml) only compiles Windows x86_64, Linux x86_64/ARM64 and macOS ARM64 desktop packages.

Can I run lichii-linux-aarch64-pgo.AppImage on an Android phone?

Not natively. lichii-linux-aarch64-pgo.AppImage and .tar.gz are compiled for desktop GNU/Linux on ARM64 hardware (glibc 2.39+, X11/Wayland, desktop Vulkan), whereas Android uses Google’s Bionic libc and SurfaceFlinger. Those files target ARM64 Linux SBCs, laptops, and handhelds booted into mainline Ubuntu 24.04 / Fedora / Arch ARM64.

Does Fritchii or Lichii work in Winlator, MiceWine or Termux on Android?

In practice it is a poor fit for Switch 2 titles. Switch 2 games require the 12GB DRAM guest memory layout, heavy Ampere/mesh-shader translation and fastmem mmap regions: proot in Termux breaks fastmem page faults and adds syscall overhead, while running Windows x64 Fritchii inside Winlator / Box64 adds x86-to-ARM + winevulkan overhead that stalls during the 120,461-shader compile or runs out of mobile RAM.

What is the real open-source Android fork of Lichii?

Hokkaido (github.com/pavelgajdo/Hokkaido, called “Lichii for Android” up to android-0.5.0) is an independent GPL-3.0 GitHub fork maintained by pavelgajdo that compiles the native ARM64 Android app (app-mainline-release.apk, package ID dev.lichii.android) with Android MediaCodec AV1 decoding, Turnip / Xclipse custom GPU driver loading, and mobile memory caps. See our Hokkaido Android fork guide for exact GitHub links and SHA-256 hashes.

How do I spot fake Lichii APK malware sites?

Avoid any site that offers a file named lichii.apk or fritchii.apk, claims “BIOS / prod.keys / firmware included”, asks you to complete a survey or install a “verification” app, links to MediaFire/Mega/Telegram instead of GitHub Releases, or ships a tiny 10–25 MB APK stub. Open issue #545 on zortos293/Lichii already documented lookalike domains bundling malicious scripts.