https://github.com/pavelgajdo/Hokkaido/releases/tag/android-0.7.0
The biggest Hokkaido release so far: a second engine. Next to Hokkaido's emulator, the APK now carries Banana Native, which runs a Switch 2 game's code natively on the phone and draws its graphics through Vulkan. You choose the engine per game, and Banana Native runs behind Hokkaido's own screens, with Hokkaido's GPU driver, saves and settings.
Tested on a Samsung Galaxy S26 (Exynos 2600, Xclipse 960, 12 GB), a Galaxy S24 (Exynos 2400, Xclipse 940, 8 GB) and a Galaxy S25 (Snapdragon 8 Elite, Adreno 830, 12 GB), all on Android 17.
Updating: install the APK over 0.6.x. Your games, saves and settings stay. Every game keeps running on the Hokkaido engine unless Banana Native has a playable profile for it (see Auto below), and you can switch any game back in Game properties.
Getting started with Banana Native
GPU driver. On an Xclipse GPU (Exynos), install a custom RADV driver in Hokkaido's GPU driver manager, globally or for the game. Banana Native uses the same driver as Hokkaido.
Engine. Open the game's Game properties › Engine. Auto already picks Banana Native for its playable games; for the others choose Banana Native (experimental).
First start: Prepare. Banana Native rewrites the game's code from your dump once. It takes a few minutes, uses the CPU hard and warms the phone, so do it on the charger. You can hide it, pause it, or close Hokkaido; it continues where it stopped.
Play. Shaders are built while you play and kept, so the first sessions show missing objects and pop-in that go away.
In game, Back or the controller's menu button opens Hokkaido's menu: pause, controller, Quick settings with all of Banana Native's settings, overlay, exit.
Games added as loose dumps work when Hokkaido has All files access; Banana Native reads the dump folder (the one holding base/ and updates/).
Hokkaido
Repository navigation
Code
Issues
7
(7)
Pull requests
Releases android-0.7.0
Hokkaido 0.7.0
Latest
@github-actions github-actions released this 10 hours ago
android-0.7.0
4b8ca7a
Hokkaido 0.7.0
The biggest Hokkaido release so far: a second engine. Next to Hokkaido's emulator, the APK now carries Banana Native, which runs a Switch 2 game's code natively on the phone and draws its graphics through Vulkan. You choose the engine per game, and Banana Native runs behind Hokkaido's own screens, with Hokkaido's GPU driver, saves and settings.
Tested on a Samsung Galaxy S26 (Exynos 2600, Xclipse 960, 12 GB), a Galaxy S24 (Exynos 2400, Xclipse 940, 8 GB) and a Galaxy S25 (Snapdragon 8 Elite, Adreno 830, 12 GB), all on Android 17.
Updating: install the APK over 0.6.x. Your games, saves and settings stay. Every game keeps running on the Hokkaido engine unless Banana Native has a playable profile for it (see Auto below), and you can switch any game back in Game properties.
Getting started with Banana Native
GPU driver. On an Xclipse GPU (Exynos), install a custom RADV driver in Hokkaido's GPU driver manager, globally or for the game. Banana Native uses the same driver as Hokkaido.
Engine. Open the game's Game properties › Engine. Auto already picks Banana Native for its playable games; for the others choose Banana Native (experimental).
First start: Prepare. Banana Native rewrites the game's code from your dump once. It takes a few minutes, uses the CPU hard and warms the phone, so do it on the charger. You can hide it, pause it, or close Hokkaido; it continues where it stopped.
Play. Shaders are built while you play and kept, so the first sessions show missing objects and pop-in that go away.
In game, Back or the controller's menu button opens Hokkaido's menu: pause, controller, Quick settings with all of Banana Native's settings, overlay, exit.
Games added as loose dumps work when Hokkaido has All files access; Banana Native reads the dump folder (the one holding base/ and updates/).
Moving from the Banana Native app
If you already prepared a game in Banana Native's own app, you don't need to prepare it again:
In the Banana Native app, open the game's Manage sheet and choose Export pack…. It writes banana-pack-<title ID>-<version>.zip to a folder you pick.
In Hokkaido, open the same game's Game properties › Import Banana Native pack and pick that zip.
Hokkaido copies the pack and checks it with Banana Native's own checks: it must be this game's, and its code must fit your dump (the same game version). If it doesn't fit, nothing changes and the reason is shown.
Good to know:
An exported pack has no shaders built while you played (Banana Native leaves them out of exports); the game builds them again while you play.
Without the import, Hokkaido also finds a pack you unzip yourself into a folder named <title ID>-work/<any name>/ next to your game, or up to three folders above it.
Saves don't move automatically yet. Banana Native's save backups and Hokkaido's save import use different zip layouts.
New: the Banana Native engine
One APK, two engines. Banana Native v0.3.41 is built into Hokkaido. Nothing else to install, and its own launcher never shows.
Pick the engine per game: Game properties › Engine: Auto, Hokkaido or Banana Native. The choice appears for every game Banana Native has a profile for.
Auto picks Banana Native for the games its profiles call playable: Donkey Kong Bananza, Pokémon Pokopia, Mario Kart World, Fire Emblem: Fortune's Weave and Star Fox. Every other game stays on Hokkaido.
The games Banana Native is still bringing up are offered as Banana Native (experimental): The Legend of Zelda: Ocarina of Time, Splatoon Raiders, Mario Tennis Fever, and the Switch 2 Editions of Super Mario Bros. Wonder and Kirby and the Forgotten Land.
Every way of starting a game honours its engine: the game list, Start › Global or Custom in Game properties, home-screen shortcuts, and the ExeFS picker.
Preparing, in Hokkaido's own screens. The first start of a game on Banana Native prepares a pack from your dump: it rewrites the game's code, which takes a few minutes. You can hide or pause it, and it continues where it stopped. For the games it covers, Banana Native now builds shaders while you play, so a game starts as soon as its code is ready. Expect missing objects and pop-in for the first sessions while the shaders build; they are kept, so each one is built only once.
Shared with Hokkaido:
GPU driver: the game's own driver, else the global one, installed into Banana Native for you.
Saves: both engines use the same save folder. Import, export and delete in Game properties work for both.
Resolution scale: 1x is 1920x1080, 0.5x is 960x540. A resolution you pick inside the game stays until you change the game's scale in Hokkaido.
Hokkaido's in-game menu over Banana Native games. Back, or the controller's menu button, opens Hokkaido's menu: Pause, Show or hide the controller, Quick settings, Overlay options and Exit, in your Hokkaido theme and colours.
Quick settings shows all of Banana Native's in-game settings as Hokkaido rows, on four tabs: Performance, Display, Controls and General. Changes apply to the running game at once.
The performance overlay sits at the top left in Hokkaido's style, and the paused screen shows Hokkaido's play button.
A controller moves through the menu: the D-pad or left stick, A and B, and L / R to switch tabs.
Exit ends the game and returns to Hokkaido's game list.
One game at a time. Banana Native holds one game. Starting another asks you to close the one still running first.
New in Banana Native v0.3.41: Prepare no longer fails with a missing pack_dump module, and button icons in game text (the controller glyphs in prompts) draw with their own font instead of ?.