BOTWRecompAndroid: Breath of the Wild Recompiled for Android in Seven Days

By Indie Kings | October 31, 2026

Updated October 31, 2026: BOTWRecompAndroid puts The Legend of Zelda: Breath of the Wild on Android by recompiling the game's code instead of emulating a Switch. The repository appeared on October 24, 2026 and shipped v0.2.7-beta on October 31, with playable progress reported on one phone and a long list of known bugs.

Image: Great Plateau background artwork from the BOTWRecompAndroid repository.

A port that refuses the emulator label

The README opens with a blunt correction: this is not Switch emulation. The game code is recompiled into C for the phone or, in the experimental Native Mode, runs directly on the phone's ARM64 CPU. The Switch's NVN graphics API is translated to Vulkan. The distinction is technical, not cosmetic.

An emulator imitates a console's hardware and runs the original binary. A static recompiler turns the game's instructions into source code that can be built for another target. BOTWRecompAndroid still needs the game's extracted files, but the phone is not pretending to be a Switch. That is why the project can support a specific set of game versions instead of a general library of Switch titles.

The project is built on LAS Recomp by peiikai, a recompilation of Link's Awakening, and LASRecompAndroid, the Android port by the same developer. It supports four versions of Breath of the Wild: 1.0.0, 1.6.0, 1.8.2 and 1.9.0. Recompiled Mode builds the game code once on the phone. Native Mode skips that build. Native Mode has been tested with 1.0.0 and 1.9.0, while 1.6.0 and 1.8.2 still need testing there.

The timeline is short. GitHub metadata puts repository creation at October 24, 2026, seven days before v0.2.7-beta. That is not seven days of clean polish. It is seven days of beta releases, issue reports and fixes, with 109 open issues at the time of writing.

Android is the only application target. Desktop ports and packaging were discontinued on October 22, 2026, though Windows, Linux and macOS can still host the Android build tools. The app needs Android 11 or newer, ARM64 and Vulkan. The README says a Mesa Turnip driver can perform better than the system driver on Adreno phones and includes a Vulkan driver selector for that reason.

The status section is unusually specific. The game is playable from the title screen into the world, with saves, on the tested POCO F7 Ultra with an Adreno 830 GPU and a Mesa Turnip driver. Performance and compatibility vary by device. GPUs that have not been tested on physical hardware should expect bugs, especially Mali hardware, which the developer says he could not test.

The feature list is wider than a proof of concept. It includes optional 60 fps on supported game versions, experimental 60 fps in-engine cutscenes, an unlocked aspect ratio, internal and output resolution controls, FSR 1 or Snapdragon GSR 1 upscaling, FXAA or SMAA, touch controls, physical controllers and gyro. Saves can be imported from a ZIP or an emulator save folder. Mods are supported, including mods that add files and DLC mod folders.

What beta 20 fixes, and what it still breaks

v0.2.7-beta is the twentieth beta, and the release notes are published in Portuguese and English. The headline fixes are controller gyro, a warning for DLC mods, an overlay that no longer shows through the pause menu, and GPU work for Mali and Adreno. The notes are written like a debugging log, with issue numbers attached.

The gyro fix addresses three separate problems. With Motion sensor set to Phone, the controller's sensors are not turned on at all. On a USB-C controller that holds the phone, aiming stopped after a few shots until the controller was reconnected. In Auto mode, a controller now counts as a gyro only after it shows a real turn of about 30 degrees per second. Controllers without gyros that send noise, such as the GameSir X2 Type-C, no longer silence the phone's sensor. The log also warns when gyro readings stop while the game is using the sensor.

The DLC warning is narrower but useful. The Relics of the Past mod closes the game at the title screen when the Expansion Pass is not installed. The developer reproduced the problem on 1.6.0 and found that it gets past the title screen with the DLC present. The Mods menu now warns when a mod for the DLC is enabled without it.

The GPU changes are the most technical part. Mali render targets are created without a mutable format, which lets the driver compress them with AFBC and save bandwidth. Passes that begin by clearing their targets now use the clear as the pass load, so a tile GPU does not read a target from memory only to erase it. Shader changes taken from TOTKDroid produce more loops and conditionals instead of a state machine when code jumps out of a region, remember the last range found in the global memory table, and remove a barrier between back-to-back dispatches. Game thread yields no longer call the system yield, which cost about 30 microseconds each.

On the POCO with Adreno 830, those GPU changes were a tie at 60 fps, with the image checked in the world and in the menus. The expected gain is on Mali GPUs, which the developer could not test. That is an honest limit, not a benchmark. Readers with a Mali device are being asked to report whether anything changed.

The known issues matter as much as the fixes. On 1.0.0, enemies can leave black lines and streaks when they die, and the game can close during a fight. The release notes recommend 1.8.2 or 1.9.0 for now. Other issues include short grass appearing only up close, water reflections that move with the camera, a black pause menu background on Qualcomm's stock driver, and terrain that sometimes stretches into vertical curtains after a tower activation. Loading a save made after the tower is active clears the curtain effect.

Updating is simple. Installing over 0.2.x does not require rebuilding the game code. Shaders recompile once, so the first minutes may stutter. The release notes also say the controller gyro fixes and the Mali changes could not be tested on the developer's own hardware, which is a reminder that a beta release is a request for device reports as much as a product.

The AI-written disclaimer is the story

The README carries a note that is still unusual in homebrew: the project is made almost entirely with AI, specifically Claude through Claude Code, directed, tested and reviewed by a human. That sentence changes how the seven-day timeline should be read. Code generation was fast. Device testing, issue triage and regression checking were not.

The release notes show the division of labor. They cite issue numbers, describe how a bug was reproduced, name the game version and the GPU, and admit which fixes were not tested on physical hardware. The AI wrote code; the human decided what counted as working. That is a different workflow from a prompt that produces a demo and disappears.

The legal side is separate from the engineering. The app includes no game files or DLC. It does not open NSP or XCI files and does not use prod.keys. Users need their own legally obtained, extracted exefs and romfs. That describes what the repository distributes. It does not settle whether recompiling a commercial game for a new platform is permitted where a reader lives, and this article does not give legal advice.

Installation has real friction. You need the APK, an extracted game folder, and either a copy of the data or in-place access. Copying needs roughly 16 GB more storage. In-place use has been available since 0.2.3-beta, requires Android all-files access, and requires the source folder to remain available. Recompiled Mode also needs space for generated code, and the README's developer script estimates about an hour for the game code build.

The project credits a long list of prior work, including LAS Recomp, SavageWindRecomp for the 1.8.2 reference, MacNativeGames for fixes and notes, and the zeldaret botw decompilation for background on the game's code. That lineage matters because a seven-day port is not seven days of invention. It is a new target built on years of reverse engineering and recompilation work by other people.

The result is a beta that runs on one phone, with a clear list of what breaks. That is more useful than a polished trailer. A reader can check the known issues against their own device and game version before spending an evening on setup.

Project card

The card is a snapshot taken on October 31, 2026. Star counts and issue counts move quickly on a repository this young. The technical rows are the ones that decide whether the app runs on a given phone.

FAQ

Is BOTWRecompAndroid an emulator?
No. It recompiles the game code into C, or runs the game's ARM64 code in Native Mode, and translates NVN graphics calls to Vulkan. The README explicitly says it is not Switch emulation.

Which game versions work?
Recompiled Mode supports 1.0.0, 1.6.0, 1.8.2 and 1.9.0. Native Mode has been tested with 1.0.0 and 1.9.0. The 0.2.7 release notes recommend 1.8.2 or 1.9.0 because 1.0.0 can crash in combat.

Do I need to own the game?
Yes. You need your own legally obtained extracted exefs and romfs. The app does not open NSP or XCI files, does not use prod.keys, and includes no game files or DLC.

What phone do I need?
Android 11 or newer, ARM64 and Vulkan. The project was tested mainly on a POCO F7 Ultra with an Adreno 830 and a Mesa Turnip driver. Mali changes in 0.2.7 were not tested on physical Mali hardware.

How much storage does it need?
Copying the game data needs roughly 16 GB more storage. In-place use avoids that copy but requires Android all-files access and the source folder must stay available. Recompiled Mode also needs space for generated code.

Is it stable enough for a full playthrough?
It is a beta. The developer reports playable progress from the title screen into the world with saves on the tested phone, but the known issues list includes combat crashes on 1.0.0 and several visual bugs. Treat it as a device-specific experiment.

Bottom Line

BOTWRecompAndroid is a static recompilation of Breath of the Wild for Android, not a Switch emulator. In seven days the project went from a new repository to a v0.2.7-beta that boots the game on a POCO F7 Ultra, with four supported game versions, two execution modes, save import, mod support, upscaling and controller gyro. It also carries 109 open issues, a combat crash on 1.0.0, and fixes that the developer could not test on Mali hardware.

Our take: the interesting part is not that a phone can run Zelda. It is that the README credits an AI model for most of the code while a human did the testing, issue triage and release notes. That is a new kind of homebrew pipeline, and the beta's long known-issues list is the part that makes it credible.

Sources

• GitHub mamcjr/BOTWRecompAndroid README, supported versions, modes, installation, features, known issues and credits, accessed October 31, 2026
• GitHub release v0.2.7-beta, fixes and known issues, published October 31, 2026
• GitHub API metadata for mamcjr/BOTWRecompAndroid, stars, forks, issues, creation date and license, accessed October 31, 2026
• GitHub peiikai/LASRecomp and mamcjr/LASRecompAndroid, the recompiler and Android port named in the project credits

Related: Breath of the Wild Decomp: 20 Percent Code and a Documentation Mission | Zelda Wind Waker HD Recomp: A World Editor and 20 Releases in 16 Days | TLG-Port: The Last Guardian Runs Native on Windows Without an Emulator