Playing Windows games on an Android phone has gone from being a novelty to something people can actually do in approximately two short years, and most of that movement has come about as a result of a single tool: Winlator. Winlator stacks Wine on top of x86/x86_64 translation layers like Box86 and Box64, with forks increasingly experimenting with components like Proton builds, FEXCore, Mesa Turnip, DXVK, and VKD3D. It turns a modern smartphone (typically Snapdragon-based) into something that can plausibly boot a PC game.

To get started, I originally thought that my Oppo Find N5 with the Qualcomm Snapdragon 8 Elite would be the perfect device. A relatively new, fast chip? It seemed the ideal candidate. However, as I went down the rabbit hole in an effort to play Portal 2, I discovered just how messy the entire world around PC gaming on a phone can be. The end result saw success at playing Portal 2 on the go, but with a caveat: it was on the Samsung Galaxy Z Fold 5 with the older Snapdragon 8 Gen 2, instead. Oh, and I had to use a community rebuild of a closed app that has been accused of copying code from at least two different open-source developers.

Does it work? Yes. I'm glad I ended up where I did, but it took a couple of weeks of trying forks I'd never heard of, reading Reddit threads, joining Discord servers, and learning that the most powerful chips on the market are actually the wrong ones for this whole hobby.

The newest Snapdragon is the wrong chip for this right now

It can work, but support isn't universal

The first thing that goes wrong on a Snapdragon 8 Elite is the Vulkan driver. The mature Mesa Turnip builds everyone has used for years on older Adreno GPUs don't cover the Elite's Adreno 830 in the same reliable way just yet, so upstream Winlator doesn't run out of the box. The accepted workaround is Vortek, an experimental driver that ships with newer Winlator builds to cover exactly this gap. Vortek loads on the Find N5, and games can render.

That's where my luck stopped, though. Performance is iffy at best, because Vortek only solves one part of the problem. Graphics are rendered via translation, sure, but the game still has to pass through CPU translation, graphics API translation, Wine/Proton, and the rest of the Winlator stack before anything useful happens on an Android phone. Still, the driver problem is partly solved, but the rest of the stack isn't fully there yet on the Adreno 830. I tried recent a8xx beta Turnip drivers Rob Clark (Qualcomm engineer, longtime Mesa contributor) is shepherding toward a full release sometime this year, but they didn't change the outcome either. There's an element of OEM madness likely at play here, too, as devices with the same SoC can work well on one company's "flavor" of Android and struggle on another.

Unfortunately, emulators like GameHub, Eden, and Winlator are very inconsistent on Snapdragon 8 Elite series chips right now, which is why 8 Gen 3 and even older 8 Gen 2 devices are preferred for this kind of work. I assumed for a long time that my problem was something I was doing wrong, but it turned out to be the relative newness of the silicon was the issue instead.

Winlator has fragmented into a confusing pile of forks, and I tried most of them

It's hard to keep up

The second you try to fix a problem with upstream Winlator, you discover "upstream Winlator" is barely the center of gravity anymore. There's Winlator CMOD by Stredohori, which ships device-specific build variants whose only job is to spoof package names so Android phones fire up their hidden "performance mode" (you can grab a build that pretends to be Genshin Impact on phones that boost for that game). CMOD was archived on May 12th, 2026, which is a separate problem.

Before I could even test a game, I had to learn which Winlator fork to use when. It was overwhelming, to say the least, so here are the major Winlator variants I had to sort through:

• There's a GLIBC variant by coffincolors.
• There's Winlator Ludashi by StevenMXZ, forked from Pipetto-crypto's Bionic build, focused on Unity and Unreal fixes, with experimental VKD3D for DX12.
• There's Winlator-Ludashi-cmod by Xoetch, a fork of a fork.
• There's Winlator101 by K11MCH1 for older devices.

Looking at that list, you can't tell me that this isn't reminiscent of "It's on Tubu. It's literally on Heebee. It's on Poodee with ads. It's literally on Dippy. You can probably find it on Weeno." Except it's for PC gaming on a phone, and at least the original meme did the courtesy of using significantly different names for all the made-up services.

Each fork also solves a different problem, and the one to run depends on your exact chip. The community recommendations I kept running into were StevenMXZ builds for Snapdragon 8 Elite, Mr Purple T25/T26 bundles for 8 Gen 2 and 8 Gen 3, and K11MCH1's R5 set for older 865/870 devices. None of this is signposted anywhere obvious, and it's the most frustrating example of the modern internet seemingly being gated behind Discord servers rather than forum posts.

With all of that said, I worked through most of it. I tried CMOD, I tried Ludashi, I tried upstream Winlator with Vortek, I tried multiple Turnip versions including the a8xx betas, I tried arm64ec versus x86_64 Wine, I tried a stack of different Proton versions and DXVK 2.14.1-gplasync, I cycled through Box64 dynarec presets and the environment variables that go with them.

My go-to benchmark was Portal 2, partly because it should be a relatively kind workload for any of this. The furthest it ever got was the Valve-guy launch sequence and the main menu before immediately closing. On some builds, Steam itself would launch with a black screen on top of a fork-and-driver combination I'd convinced myself was finally the magic one. Sideloaded games without Steam in the loop similarly struggled, and most of the time, nothing rendered at all.

That fragmentation is partly a strength of Winlator, but a curse for those who just want to play their favorite PC games on the go. You can use any fix you want for a niche issue, and the forks tend to be well-made, too. After enough nights of trying to get it working, I gave up on the Find N5 entirely, trying the Samsung Galaxy Z Fold 5 instead. Similar issues, similar problems, and in a last-ditch effort, I tried the app most people end up on when they don't want to deal with any of it: the controversy-laden GameHub.

GameHub is the easy way in, but it carries a lot of baggage

Controversy after controversy

GameHub is made by GameSir, the controller-hardware company. Its internal Windows emulator is called GameFusion, which GameSir describes as self-developed while admitting it borrows "UI components from Winlator to maintain ecosystem compatibility." It hit around five million users by November 2025, and according to TheMemoryCore, 70 to 80 percent of those users are in China. On a Snapdragon 8 Elite handheld, it can apparently run Cyberpunk 2077 at 720p Low with FSR 3 at 60-plus FPS. It's close enough to a plug and play experience, but it's also closed source. That's bad enough, but it has a lot of problems, too.

The first major issue is the trackers. The original GameHub APK shipped with a ton of invasive permissions including location, microphone, camera, and contacts, none of which an offline emulator has any business asking for. It contained a lot of telemetry-related files and SDKs, including Firebase, Google Analytics, and Chinese trackers Umeng and JPush. GameSir blamed Chinese-market privacy defaults and stripped many of them from the global Google Play build.

The second issue is code-attribution. After GameSir dared its critics to decompile the app on Discord, several developers actually did. StevenMX, the maintainer of Winlator Ludashi, publicly accused GameSir of shipping his Vulkan renderer without attribution, and a developer called leagoo says he's "95.7% certain" that a Vulkan graphics wrapper inside GameHub is his, pointing to a few different code samples as evidence. In one instance, a specific six-element push_constants table where two entries are unused apparently appears identically in both binaries. Termux X11 code was also alleged to have been included in the app.

Some of the projects GameHub is accused of drawing from are permissively licensed, where reuse may be allowed with attribution, while others may carry stronger source-disclosure obligations. Either way, the core complaint from developers is not just reuse, but reuse without visible credit or compliance. GameSir's official line is that GameFusion is independently developed.

The third and final issue is the company's history. GameSir previously released EggNS, a Switch emulator for Android the community said contained code from Yuzu and Skyline without attribution, required registration to use, and was gated behind ownership of a specific GameSir controller before it was pulled entirely. It's understandable why the Winlator community has seen EggNS and may feel as if history is repeating itself.

The response was pretty interesting, though. The community rebuilt GameHub without its trackers, dubbing it GameHub Lite. GameHub Lite was originally put together by a developer called Clippy and is now maintained by Producdevity, who also runs EmuReady and contributes to GameNative, a project led by developer Utkarsh Dalal. Producdevity reverse-engineered GameHub and applied code-modification patches to remove unnecessary permissions, tracking, add offline support, and so much more. Oh, and all of this shrinks the APK from 118MB to 52MB. The cleaned-up app apparently runs faster on equivalent hardware than the official build does, which makes sense. Removing trackers, unnecessary permissions, and background services gives the emulator fewer things to fight while it's already trying to pretend your phone is a Windows PC.

The legal status is, generously, ambiguous. Lite reverse-engineers a closed proprietary app that is itself accused of incorporating open-source code without visible attribution or compliance. GameSir hasn't responded to a request for comment from Android Authority, but Producdevity has since shifted most of its focus to GameNative, an open-source rebuild with a PlayStation-style UI. It also has native integration with Steam, GOG, and Epic libraries. GameNative is still pre-1.0, and the more practical answer if you want something running today is still GameHub Lite.

The older phone won, and by a comfortable margin

The Snapdragon 8 Gen 2 is better supported overall

The Galaxy Z Fold 5 has a Snapdragon 8 Gen 2 in it. On paper it's the slower phone. In practice, it ran GameHub Lite the first time I opened it, with minimal driver-picking steps, no forks to rifle through, and no absurd amount of research required. The biggest problem turned out to be OneUI 8.5, but thanks to a Redditor, I discovered that switching to turnip_v26.2.0_b3 fixed that.

The thing with those older SoCs is that Mesa Turnip has matured significantly, and GameHub Lite's inherited DXVK and VKD3D defaults are sensibly tuned for that chip. I probably could have just as easily gotten things working using Winlator (or one of the dozen forks), but the thing is that GameHub Lite just... worked. The cleaned-up build also helps, as it cuts background tasks that would otherwise eat into headroom.

If I could have got it working, the Snapdragon 8 Elite is apparently a very capable PC emulation SoC. I've seen tests showing GameHub on the Snapdragon 8 Elite being able to get 60 FPS in Cyberpunk 2077, which is pretty impressive. My Fold 5 isn't pushing those numbers, though it's still fairly capable as well.

The Rob Clark a8xx Turnip driver should eventually bring the Snapdragon 8 Elite up to par with older chips, but right now, that's not the case. That driver is months away at least from being capable of doing that in a ubiquitous fashion, and realistically the practical answer is to use an older Snapdragon and a fork instead.

It's funny, though. PC game emulation on Android is held together by a handful of unpaid maintainers all building their own software, each meeting niche needs for different hardware and software. At the same time, they're improving a closed-source app that may or may not be standing on top of their own code.

I'll be honest, it's a bit of a messy system right now, and I wouldn't recommend getting into it unless you're happy to experiment and play around with things to get it just right. However, tools like GameNative are improving fast, translation layers like FEX and Proton are continuously improving, and upstream Winlator continues to get better and better. The situation has been improving day by day, and technically speaking, you can already put in the work and play your AAA games anywhere in the world with a flagship smartphone. It's incredibly impressive, and I'm excited to see what comes next.