Pocknix on the Retroid Pocket Flip 2 mini review

August 8, 2026

What a time to be alive, at least for those of us who are nostalgic. Unlike 10 years ago, almost everything is now readily available to us. At least when it comes to emulated games and old systems. The development of the scene is at least 20 times faster, while compatibility and the choice of handheld consoles for emulation, thanks in no small part to Android, among other things allow us to enjoy these things like never before.

OK, there is the historically massive jump in the price of RAM and flash memory in general, but it is what it is. We have options.

On July 22, 2026, I happened to see an announcement that Pocknix had been released to the public. I thought, hmm, maybe a better distro than ROCKNIX?

The developer was also publicly asking for someone to test it on the Retroid Pocket Flip 2. What a coincidence! That’s exactly what I’m using at the moment.

I quickly pulled out an old 64GB Kingston card, fired up Balena Etcher and entered the bootloader on my Flip 2. When that didn’t work (slow card, impossible to do anything), I unpacked a brand new Samsung Pro Plus 256GB and booted up.

What exactly is Pocknix?

Pocknix is not another Android launcher or an application that simply adds another way of running Windows games on Android. It is a complete Arch Linux ARM operating system designed for Snapdragon-based handhelds. It uses a Linux kernel based on ROCKNIX and provides a Steam gaming environment as well as a Plasma Mobile desktop environment.

And this is where the main difference between Pocknix and things like GameNative and GameHub comes in. GameNative and GameHub (or Winlator in general) are Android applications. Android is still the operating system underneath them, while the applications create and manage the environments needed to run Windows games. Pocknix takes a completely different approach.

Android is no longer the operating system running the game. You boot directly into Linux, Steam runs natively as an ARM64 application and Windows games are handled through Proton, FEX and the rest of the Linux gaming stack.

So instead of something like:

Android → GameNative/GameHub → compatibility layer → Windows game

you have something closer to:

Linux → Steam → Proton/FEX → Windows game

And that is probably the most interesting part of Pocknix.

Without getting too deep into Execution Pipelines, Android overhead and the differences between a Linux userspace and the Android Runtime, the short version is this:

GameNative and GameHub are Android solutions. They create an environment for each game and use the necessary compatibility layers inside that environment.

Pocknix flips the whole thing around. There is no Android userspace underneath it. You have an actual Linux userspace with Steam, Proton, Mesa and Turnip. Another important difference is how that userspace is organized. With solutions such as Winlator, each game can have its own container with its own Wine environment, Windows files, configuration and compatibility settings. Pocknix doesn’t work that way. The entire SD card is essentially your Linux system, so the games are running inside the same operating system environment rather than being placed into separate containers.

And that is the reason Pocknix is interesting. But that doesn’t automatically mean everything will work better. Quite the opposite, actually. This is where one of the biggest problems comes in. The drivers.

Pocknix uses Mesa and Turnip for Qualcomm Adreno GPUs, which means you are relying on Linux support for your particular SoC and GPU. On newer Snapdragon chips this may be less of an issue, but on the Snapdragon 865 things are a bit more complicated.

How to install Pocknix

The installation is fairly simple.

Download the latest image for your device.
Extract it. The image is in .zst format and you will need 7-Zip if your tool doesn’t support it directly.
Have an empty microSD card ready.
Use Balena Etcher to write the image to the SD card.

If you are using a Retroid Pocket 5 or Flip 2, you need to enter the boot menu. With the device powered off, hold the Power and Volume Down buttons together. From there, change the boot mode from Android to the option for booting from the SD card. This leaves Android on the internal storage, while Pocknix boots from the microSD card.

Once you have Steam running, you also need to select the appropriate ARM64 Proton build for individual games.

Open the game’s Properties → Compatibility, tick “Force the use of a specific Steam Play compatibility tool” and select Proton-GE 11 (ARM64) or Proton-CachyOS 11 (ARM64).

Why Pocknix?

One huge advantage is that with ARM64 Proton and FEX, Windows x86/x64 games can be executed on an ARM64 system. I won’t get into technicalities like the execution pipeline, Android overhead, bare metal POSIX versus Android Runtime architecture and all the other stuff that could easily turn this into a 5,000-word article by itself.

I’ll just say that the execution of the games themselves is much more direct. But there is also one huge downside, and that is the Linux graphics stack and the availability of suitable Mesa/Turnip versions.

Even though a large number of games can start, performance is what you actually see on the screen. That means that if you have a problem with the graphics stack, you don’t have a particularly simple solution.

If you are using something newer like the Retroid Pocket 6, this may not be such a big problem because of its much faster SoC. But the Retroid Pocket 5 and Flip 2, both using the Snapdragon 865, can definitely have performance problems in a number of cases.

Simply put, the Snapdragon 865 needs good driver and software optimization, and it also doesn’t have the raw GPU power of newer chips.

Now, someone will say that Pocknix and other Linux distros also have ways of using custom Turnip drivers, and that’s true. But it is much more complicated than doing the same thing on an Android emulator.

To explain how, I would need to write an entire tutorial just for that. In short, it looks something like this:

[ ANDROID ]

App
↓
AdrenoTools dynamic hook
↓
Custom Turnip .so
↓
Android graphics stack
↓
Kernel


[ POCKNIX ]

Game / Proton
↓
Mesa / Vulkan
↓
Turnip / vulkan-freedreno
↓
DRM / KMS
↓
Linux Kernel

This is a simplified overview rather than an exact execution pipeline, but it shows the important difference.

With Pocknix, the graphics stack is system-wide. That means that updating or replacing Mesa/Turnip components isn’t simply a matter of downloading a .so file and selecting it from an emulator menu. You are dealing with system Linux packages.

And since the majority of our visitors aren’t really familiar with Linux, let alone Arch Linux package management, I don’t think anyone would read that tutorial even if I wrote it. You can prove me wrong in the comments.

Testing some games

I tested several games: Factorio, Fallout: New Vegas, Fallout 4, Core Keeper, Skyrim and Vampire Crawlers.

The results were… different.

Let’s start from the beginning.

Factorio worked exceptionally well. Almost 60 FPS all the time, except when I brought out the Spidertron and started destroying nests. Performance dropped a little at that point, but it was still above what I expected. One particular problem is that Factorio doesn’t have native controller support, so the gameplay was a combination of the touchscreen and the physical buttons.

Not ideal, but the result was satisfactory.

Next I decided to try Fallout: New Vegas. Although I have successfully played it through GameNative, I ran into a problem here. Some particle effect simply didn’t agree with the graphics stack on the Retroid Pocket Flip 2. Performance was terrible. At one moment I was getting 60 FPS and at another 5. I tried everything I could think of, including different settings and resolutions, but nothing helped. In its current state, the game is simply unplayable.

Disappointed by Fallout: New Vegas, I decided to try my luck with Fallout 4. But no luck there either. The game simply refused to start without giving me any specific indication of what the problem was.

Skyrim was next. I know I’ve always had problems with sound when trying to play it through Winlator and GameNative, specifically with dialogue and character voices. Surprisingly, that problem didn’t exist here.

I don’t want to speculate whether the difference is somewhere in ALSA, DirectSound translation or something else, but the fact is that the audio worked properly this time. Performance was somewhat worse, though. Luckily, at 720p I was able to maintain a stable 30 FPS. That’s perfectly fine for Skyrim on this hardware. And yes, sorry I forgot to take in-game screenshots. Boo.

One of my favourite indie games lately has been Vampire Crawlers, a spin-off of the popular Vampire Survivors. There were no problems here either, it ran mostly between 30 and 40 fps with occasional dips in the mid 20’s. And that’s fine for this type of game.

Finally, I tried the game that has been taking up most of my free time for the last two weeks, Core Keeper. It looked great and was stable, but unfortunately I was getting only 10 to 15 FPS regardless of the settings. I messed around with Proton, but no luck. Perhaps it will improve in the future?

A few words beyond Steam

What certainly makes Pocknix interesting is the fact that, besides the Steam client, there is a whole operating system running in the background. And yes, using the power button you can enter the Plasma Mobile desktop mode, where you’ll find a bunch of preinstalled emulators as well as the desktop edition of ES-DE.

All you have to do is copy your ROMs to ~/Emulation and start playing.

There is no point in wasting space listing all the emulators because the developer is constantly adding new ones and updating the existing. In short, this means that moving to this OS doesn’t mean you have to forget about retro games. The emulators are there and they work.

Even more interestingly, Pocknix allows games marked as Favorites in ES-DE to appear in the Steam library, meaning you can launch them directly from Steam Game Mode.

So, should you switch to Pocknix?

At this point, I wouldn’t. At least not permanently. And I’m not saying that as criticism.

Pocknix is still in its early stages and the project is moving very quickly. In fact, two new updates were released while I was working on this article. That alone tells you where we are with the project.

If you want something that you install once and simply forget about, you should probably wait. But if you have a spare microSD card, Pocknix is definitely worth trying. That’s probably the best thing about it right now. You don’t have to commit to anything.

Grab an empty microSD card, flash the latest version and see what happens. If the games you play work, great. If they don’t, pull the card out, boot back into Android and continue as before.

And considering how quickly this project is developing, I wouldn’t be surprised if some of today’s “doesn’t work” games become tomorrow’s “runs at 60 FPS.” Fingers crossed.

LINK
https://github.com/shuuri-labs/pocknix-os

_{Dejan Balalovski}