I Turned My Phone Into a Steam Deck — Proton 11 Wasn’t Enough

Added: 2026-05-09

[00:00:00]What you're looking at is Steam running natively on my phone.

[00:00:03]This is not cloud gaming or remote access. Everything is running directly on this phone.

[00:00:09]Recently Valve released Proton 11 with official arm support. So on paper, this should have been simple. Install Proton, launch Steam, and play games.

[00:00:19]And yes, those games are actually running on it. No streaming, no emulation, nothing happening on another device. It was not simple.

[00:00:27]I spent 7 days, went through three phones and four operating systems, and hit a kernel limitation that should have made this completely impossible.

[00:00:36]This is the actual story of what it takes to run Steam on an Android phone in 2026.

[00:00:42]And the answer is not what Valve's announcement made it sound like.

[00:00:46]A while back, I made a video about getting Linux running on Android.

[00:00:50]Someone left a comment asking about Steam on that same setup. That comment basically started this whole thing. I assumed it would be straightforward.

[00:00:58]Valve literally announced Proton 11 for ARM. So I spent 7 days trying to get real desktop Steam running natively on Android. I started with the proper approach, Ubuntu in Termux, Fexemu, Proton 11, the full stack. And technically, everything installed. Steam files, x86 rootfs, Fex itself. But every single time I launched Steam, instant crash, illegal instruction.

[00:01:24]I thought it was proot. So I rooted the phone, switched to a real crude environment, rebuilt the entire setup, same crash.

[00:01:34]That is when I finally found the actual problem.

[00:01:37]My phone kernel only supports 39-bit virtual memory.

[00:01:41]Fex needs 48-bit address space for x86 emulation.

[00:01:46]That was the wall. So instead of fighting Android, I removed it completely. I flashed postmarketOS, a native Linux distribution, directly onto the phone.

[00:01:56]Installed Fex on that. But then the next problem, postmarketOS runs Wayland and Steam expects a traditional X11 display server. So I added XWayland as a translation layer between them. And finally, Steam launched.

[00:02:11]Proton 11 beta showed up in the drop-down. I downloaded Brawlhalla, hit play.

[00:02:32]And waited. It never launched.

[00:02:35]So that left one option.

[00:02:37]I am not going to explain it right now.

[00:02:39]You will see it on screen.

[00:02:41]And this time Steam actually launched fully.

[00:02:45]Brawlhalla, No Room in Hell, Deadpool, all of them ran. That footage you saw at the start, that is this setup.

[00:02:53]And then the games actually ran.

[00:02:55]Brawlhalla was completely smooth, no lag, no stutter, nothing. No Room in Hell, same story. These are real PC games running on a 7-year-old phone and they felt like native apps.

[00:03:07]Deadpool is a heavier title. That one had some lag. But it was running on a Snapdragon 845.

[00:03:15]If a chip this old can do this, imagine what a current flagship would do with this setup.

[00:03:20]Now, why did Windows arm succeed where everything else failed?

[00:03:24]The kernel.

[00:03:26]On Android, the kernel is locked down and vendor modified.

[00:03:30]FEX emu needs 48-bit virtual address space for x86 translation. Android kernels on most phones cap at 39-bit and you cannot change that without recompiling.

[00:03:42]PostmarketOS gave me a proper Linux kernel, but Wayland and the FEX stack still could not deliver a working Steam session.

[00:03:49]Windows arm runs its own kernel entirely with its own memory model, its own DirectX translation layer through D3D metal, and its own X86 emulation built-in. It bypassed every single limitation that killed the Linux attempts. That is why it worked.

[00:04:05]Controlled with a Bluetooth mouse and keyboard, running on the same phone, sitting in front of an AC vent with a thermal pad mod on the chip to keep temperatures manageable.

[00:04:15]But I also tried Warframe.

[00:04:17]That one did not work because Warframe requires DirectX 12, and this setup only has DirectX 11 support. You can see that clearly in the recording.

[00:04:26]So, there is still a ceiling here. This project is not done. I am still pushing it every weekend, specifically trying to get Proton 11 working inside Android and to make this whole setup accessible for every Android user. Everything is going on GitHub, the findings, the scripts, the dead ends.

[00:04:43]Link is below. If you want to help, come build this with me.