Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
2026-10-05 · Setup guide and analysis
Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
Every few months something promises Steam on Android and turns out to be a streaming app, a launcher skin or a Windows emulator with a Steam shortcut in it.
DroidDeck is not any of those. It installs Valve's own ARM64 Linux Steam client, runs it in Big Picture with Deck mode switched on, and plays Windows games through Valve's ARM64 Proton. It does that as an ordinary Android app, with no root and without wiping Android off your device. You can even set it as your Android launcher, so the handheld boots into Steam.
It is also moving extremely fast. The project is a few weeks old and has already shipped four numbered releases, with star and download counts that have multiplied several times over in the days since we first wrote this up. We have stopped quoting those numbers here, because any figure we print is wrong within a week.
The catch is the GPU requirement. It is still the thing that decides whether this is for you, though it has turned out to be softer than the flat refusal we and most other coverage reported.
The Short Version
- What it is: Valve's real ARM64 Steam client on Android, with ARM64 Proton for Windows games. Not streaming, not an emulator.
- What it needs: an Adreno 730 or newer, or an 8xx series Adreno. Android 9 or later. No root.
- What is now experimental rather than out: Adreno 6xx. DirectX 11 goes through DXVK 2 and may work, DirectX 12 can still crash.
- What it rules out: Mali, Xclipse, PowerVR and, oddly, Adreno 710. That is nearly every Anbernic Android handheld and every Dimensity device.
- Current version: 0.4.0, released 12 October 2026, GPL-3.0.
- If your chip is on the experimental or no list, Armada is the other route and its tested device list goes further down the stack.
- Space needed: about 3 GB for the Linux runtime, plus 1.1 GB more if you want the desktop and emulators, plus your games.
- One setting to change: Restrict child processes, in Android developer options, has to be off.
- It has no website. The project says so plainly and warns against any site offering downloads in its name. A site at droiddeck.app exists anyway.
- You bring your own Steam library. It ships no games and no Valve binaries.
Is DroidDeck Safe?
Yes, if you get it from the project itself. The risk is not the software, it is where you download it. DroidDeck is open source under GPL-3.0 and publishes SHA256 sums with every release, so the code is auditable and the file is verifiable.
Here is the full picture in the order that matters.
What it installs. A Linux runtime of about 3 GB, Valve's genuine ARM64 Steam client, and ARM64 Proton. Optionally another 1.1 GB for a KDE desktop and emulators. It ships no games and no Valve binaries of its own, and it does not replace Android or need root.
What it can access. It runs as an ordinary Android app, so it is inside the normal Android permission model rather than outside it. It does want one developer option changed, "Restrict child processes" turned off, which it needs in order to run the Linux processes it manages. That is a real change to a protective default, and it is worth knowing you made it.
The one documented problem, which the team found and fixed themselves. Every build up to and including 0.1.6 was signed with the public AOSP test key. Anyone at all could have signed an "update" with that key and had it install straight over DroidDeck. Version 0.1.7 moved to the team's own key with a signature rotation, so test-key builds are refused from then on. Run 0.1.7 or later.
What is genuinely unverified, and it is the actual hazard. The project states plainly that it has no website and warns against download links from any site claiming to be the DroidDeck team. A site at droiddeck.app exists anyway, presents itself as the project and offers APK downloads. We have not analysed what it serves and we are not characterising it. We are repeating what the developers said and leaving the arithmetic to you.
So the rule is simple. Install from the project's own releases, check the file against the SHA256 list published in that same release, and ignore every other source. We make no judgement about any specific binary we have not examined.
The longer version of this, including why the signing key mattered, is in there is no DroidDeck website further down.
Does Your Handheld Qualify
This is the first thing to check, because nothing else matters if the answer is no. The project's requirement is an Adreno 730 or newer, or any 8xx Adreno. It names Mali, Xclipse, PowerVR and Adreno 710 as unsupported outright.
We previously printed a flat "No" for the Adreno 6xx devices in this table, and that was too strong. The project's current wording is that Adreno 6xx is experimental, with DirectX 11 running through DXVK 2 and possibly working, while DirectX 12 games can still crash. That is a real difference for the many people on a Retroid Pocket 5, Flip 2 or similar, so the rows below have been corrected.
The Adreno 710 being excluded while the older 6xx parts are merely experimental looks like a mistake and is not. A higher model number does not guarantee a better position here, because what matters is the state of the open source Vulkan driver for that specific part rather than its performance tier.
Here is where that leaves the Android handhelds in our catalogue.
| Handheld | GPU | DroidDeck |
|---|---|---|
| AYN Odin 3 | Adreno 830 | Yes, and the fastest option here |
| AYN Odin 2 Portal Pro | Adreno 740 | Yes |
| Retroid Pocket 6 | Adreno 740 | Yes |
| Retroid Pocket Nova | Adreno 740 | Yes |
| AYN Thor | Adreno 740 | Yes |
| Retroid Pocket Duo | Adreno 722 | Below the 730 floor |
| Ayaneo Pocket S | Adreno A32 | Unclear, see below |
| Trimui Brick Hammer Pro U | Adreno A21 | Unclear, see below |
| Retroid Pocket 5 | Adreno 650 | Experimental |
| Retroid Pocket Flip 2 | Adreno 650 | Experimental |
| Mangmi Pocket Max | Adreno 650 | Experimental |
| Ayaneo Pocket Micro 2 | Adreno 650 | Experimental |
| Retroid Pocket Classic | Adreno integrated | Experimental at best |
| Anbernic RG 55G1 | Adreno A12 | No |
| Any Anbernic on a Dimensity or Unisoc chip | Mali | No |
The unclear rows are a real gap, not us hedging. Qualcomm's G series gaming chips use their own GPU names, like the Adreno A32 in the Snapdragon G3x Gen 2 and the A21 in the G2 Gen 1. The project's requirement list talks only about numbered Adreno parts, so it never says yes or no to the A series. Until someone tests one and reports back, treat those as unknown.
If you are on an Adreno 650, there is a better option than hoping. Armada, an ARM Linux distribution that boots straight into Steam, lists the Retroid Pocket 5 and the Retroid Pocket Flip 2 as tested devices. It is a much larger commitment than installing an APK, since it involves bootloader work and can brick a device, but it means the chip is not the thing stopping you. Our comparison of all five options works through that choice properly.
If you are shopping rather than checking, the cheap end of the yes list is the
or the , both on the Adreno 740. The on the Adreno 830 is the most headroom you can buy in this category. Our Snapdragon 8 Elite handhelds guide covers that tier in detail.DroidDeck on the Retroid Pocket 5, 6 and Flip 2
These three come up more than any other devices, and they do not get the same answer.
Retroid Pocket 6
Yes, fully supported. The Snapdragon 8 Gen 2 and its Adreno 740 sit comfortably above the Adreno 730 floor, so this is one of the devices DroidDeck is actually aimed at. The same is true of the Retroid Pocket Nova, which uses the same chip.
This is the cheapest straightforward entry into running real Steam games on Android. Budget about 3 GB for the Linux runtime, another 1.1 GB if you want the desktop and emulators, and then whatever your games need. Our Pocket 6 setup guide covers the rest of the device.
Retroid Pocket 5 and Flip 2
Experimental, which is a correction to what this page originally said. Both run a Snapdragon 865 with an Adreno 650, below the stated floor. We previously printed a flat "No" and that was too strong: the project's current wording is experimental, with DirectX 11 going through DXVK 2 and possibly working while DirectX 12 can still crash. There is a report of games failing to launch on a Flip 2.
The practical advice for these two is to use something else. Armada, the ARM Linux distribution that boots straight into Steam, lists both the Pocket 5 and the Flip 2 as tested devices. It is a far bigger commitment than installing an APK, because it involves bootloader work and the project states a real risk of bricking, but it can boot from an SD card so Android survives. Winlator, GameNative and GameHub all stay inside Android and work on this chip too.
The thing to take away is that the Adreno 730 figure is a DroidDeck limit, not a limit of your hardware or of ARM. If you have been told a Pocket 5 cannot run PC games, that is wrong. It cannot run this particular app well. Our comparison of all five routes covers which one suits an Adreno 650, and the Pocket 5 setup guide has a section on it.
What It Actually Is Under the Hood
Worth understanding, because it explains both the GPU rule and the bugs.
DroidDeck does not emulate anything. It builds a small Linux environment inside an Android app using proot, which lets an unprivileged process act as if it were root inside its own directory tree. Into that it puts Valve's genuine ARM64 Linux Steam client. It runs gamescope, the same compositor Valve uses on a Steam Deck, inside an in-app Wayland compositor. Windows games go through Valve's ARM64 Proton, which translates Windows calls into Linux ones, with x86 instructions handled by translation underneath.
Graphics land on Turnip, the open source Vulkan driver for Adreno hardware. That is the whole reason for the GPU rule. Turnip is mature on Adreno and does not exist in usable form for Mali, Xclipse or PowerVR. The hardware limit is really a driver limit.
If any of those layer names are unfamiliar, our translation layers explainer walks through what each one does and why stacking them costs performance.
Version 0.3.0 added a GPU drivers tab that detects your chip and keeps a matched pair of runtime and display drivers installed for it, including the project's own Turnip builds. That removes the most annoying part of this kind of setup, which used to be hunting down a driver package by hand.
What 0.4.0 Brought
The 12 October release is the biggest one so far, and it moves DroidDeck from a Steam client in a box to something much closer to a full SteamOS experience.
Other storefronts, properly. GOG, Epic Games and Amazon Games now have account sign in, browsable libraries, downloads and launching, all routed through Steam as non Steam games so Proton handles them like everything else. GOG and Epic titles also get cloud saves. That is the single biggest functional gap closed.
A real desktop. The old lightweight shell is gone, replaced by a SteamOS style KDE Plasma 6.7 desktop with a file manager, browser, terminal, the Steam desktop client, and a working Return to Gaming Mode. The desktop can now launch Windows executables, Linux programs, AppImages and scripts directly.
Steam's own touch controller. In beta, with per game Steam Input layouts, community configurations, an on screen editor and Steam Cloud syncing.
Up to four controllers. Connected Android gamepads now work independently, so local co-op and split screen multiplayer work through Steam Input.
Controller shape shifting. The built in controls can now present themselves as a Steam Deck, Steam Controller, Xbox 360, DualShock 4 or DualSense, switchable mid session without restarting Steam. Bluetooth Steam Controller support landed too, trackpads and all.
Per game compatibility profiles, covering Proton, FEX, DXVK, VKD3D, Windows components, environment variables and texture filtering, inheriting from your defaults.
Windows components install themselves now, chosen automatically from each game's storefront dependency information, including Visual C++ redistributables and .NET Framework.
Foldables are a first class target. Steam and games resize when you fold, unfold or rotate, and there is an optional touch gamepad below the game on an unfolded screen.
It got faster. The project reports its proot layer running up to 57% quicker in measured workloads, with lower idle CPU use and reduced controller input overhead.
What 0.3.0 Brought
The 2 October release is the one that first made people pay attention, and most of it was quality of life rather than raw speed.
Steam starts in about six seconds instead of about thirty one. That is the project's own figure. The practical result is that Offline mode now works, because Steam is no longer so slow to come up that it gives up on the check.
Your pad becomes a Steam Deck controller. In a Steam session the client reads your handheld as a Deck, with a real Quick Access button and your device's gyro, and games get Steam Input's virtual pads so community layouts reach them. On a dual-screen handheld the second screen can act as the Deck's back grips and trackpads, which is the single oddest and most inventive feature in the whole project.
The Deck performance overlay. MangoHud at levels one through four, with Adreno GPU load, CPU, clocks, temperatures, VRAM and battery. Quick Access shows battery life and time to full.
Decky Loader can be installed, so Steam Deck plugins work here too. If you have not used it, our Decky and Nexus guide covers what that ecosystem is.
Frame generation, with a condition. Lossless Scaling frame generation is wired in with 60, 90 and 120 FPS targets, but it reads Lossless Scaling out of your own Steam library and ships none of its shaders. No copy, no frame generation.
Linux apps from Flathub, in ARM64 builds, opening full screen from the front end with a controller. You can also point it at your own AppImage, a Flatpak ID, or the newest ARM64 AppImage in a given project.
Updates inside the app, on three channels: stable, preview, or a test build of an open change.
The Four APKs, Explained
Go to the releases page and you will find four APK files for the same version. Nothing on the page explains them, so people pick at random.
They are the same build. The only difference is the Android package name each one is signed under. One is DroidDeck's own name. The other three use the package names of PUBG Mobile, AnTuTu and Ludashi.
The project's own build file says why in one line: some phones only hand out their performance modes to apps with certain names. So if your handheld or phone has an OEM boost profile keyed to a game or a benchmark, installing the matching variant is how you get it.
Each variant is a separate app as far as Android is concerned. They install side by side and keep their own data, which means you can try one, then another, without uninstalling.
Start with the standard build. Only reach for a renamed one if you suspect your device is throttling DroidDeck and would not throttle a benchmark.
Setting It Up
The install is short. The one step that trips everyone is an Android developer option.
- Install the APK from the project's own releases page, and nowhere else. See the warning below.
- Turn off Restrict child processes in Android developer options. DroidDeck cannot start Steam with it on. On Android 12 and 13 that option often is not there, and first launch offers a "Fix it for me" button that automates the workaround.
- Install the Linux runtime from inside the app. Budget about 3 GB.
- Press Play and sign in. Steam downloads itself on first launch.
- Optionally add Desktop and apps, another 1.1 GB, which gets you the Linux desktop, the emulators and the Flathub store.
Then there is your library, which is the part nobody budgets for. Proton installs are large, and a handful of modern games will fill a 256 GB card on their own. A
is the sensible floor if you plan to keep more than two or three Windows games installed.What Goes Wrong
A couple of hundred open issues on a project this young is not a bad sign, it is what something getting real attention looks like. But they tell you what to expect, and that is more useful than a feature list.
Anti-cheat games do not work. This is structural, not a bug. Kernel level anti-cheat does not run here and will not.
Non-Latin text renders as blank boxes. The Linux runtime ships only one font family, so Chinese and Korean Steam interfaces come up as tofu. There are open requests for both.
Touch and mouse alignment drifts at non-native resolutions and forced aspect ratios, and the cursor can vanish entirely in some app modes.
Audio problems are device specific. Crackling is reported on at least one AYN device, and others report no audio at all.
Some devices just do not render. A VR headset on an Adreno 740 variant fails at graphics device creation, and a Samsung XR device comes up glitched on every driver. The project is honest that hardware validation is limited and that compatibility varies by device.
The desktop is software rendered, so treat the Linux desktop as a utility rather than somewhere to play anything.
Unsupported GPUs fail in the way you would expect. At least one report is simply a person with an Adreno 650 handheld whose games will not launch. Check the table above before you file that one.
There Is No DroidDeck Website
This part matters more than any feature.
The project's README carries a plain notice: DroidDeck does not have a stand-alone website, and you should not click download links from any site claiming to be the DroidDeck team. The only builds the team publishes are the ones attached to its own releases page.
A site at droiddeck.app exists anyway, presents itself as the project, and offers APK downloads. We are not linking it and we are not characterising what it serves, because we have not analysed the file. We are telling you what the developers said, which is that they publish no website, and leaving the arithmetic to you.
There is a concrete reason to care rather than shrug. The project's own development log records that every build up to and including 0.1.6 was signed with the public AOSP test key, which means anyone at all could have signed an "update" that would install straight over DroidDeck. Version 0.1.7 moved to the team's own key with a signature rotation, so a test key signed APK is refused from then on. That is a real attack surface they found and closed themselves, and it only holds if your copy came from them.
Install from the project's releases page, check the file against the published SHA256 list in the same release, and ignore everything else.
DroidDeck vs ROCKNIX vs Winlator
Three different answers to the same wish, and they are not really competing for the same person.
| DroidDeck | Armada | ROCKNIX Steam | Winlator | |
|---|---|---|---|---|
| Keeps Android | Yes, it is an Android app | Only if you boot it from an SD card | No, it boots a separate Linux OS | Yes |
| Root required | No | Boot loader work required | Boot loader work required | No |
| What runs Steam | Valve's real ARM64 client | Valve's real ARM64 client | Valve's real ARM64 client | Steam inside a Windows container |
| Windows games | ARM64 Proton | ARM64 Proton | ARM64 Proton | Wine plus Box64 or FEX |
| GPU requirement | Adreno 730+, 6xx experimental | Tested down to Adreno 650 | Snapdragon, varies by device | Adreno strongly preferred |
| Setup effort | Install an APK, flip one setting | Flash a card, flash a boot loader | Flash a card, flash a boot loader | Install, then tune containers |
| Risk of bricking | None | Real, stated by the project | Real | None |
| Best for | Trying Steam without giving anything up | A dedicated Steam handheld, or an older chip | Steam alongside a retro frontend | Windows games that are not on Steam |
Armada is the new entry there, and it is the one to look at if DroidDeck's GPU rule rules you out. The full five way comparison is in our landscape guide.
DroidDeck is the lowest commitment of the three by a wide margin. ROCKNIX asks you to flash a boot loader and run a different operating system, which our ROCKNIX Steam guide walks through. Winlator is a Windows compatibility layer rather than a Steam environment, and our Winlator setup guide covers where that fits.
The broader question of whether an Android handheld or a Linux one suits you is in Linux vs Android handhelds.
Should You Install It
If you own an Adreno 740 or 830 handheld, yes. It is free, it is an APK, it does not touch Android, and the uninstall is uninstalling an app. The worst case is a few GB of wasted download.
If you own anything on the no list, do not buy a new handheld purely for this. The project is weeks old, the issue list is growing faster than it is shrinking, and the thing that makes it good is a Valve client and a Valve translation layer that could change at any time. Buy a handheld for the games it already plays well. If you are on an Adreno 650 and determined to get there, look at Armada before you look at new hardware.
If you want a guaranteed Steam experience, buy a Steam Deck. That is not a dodge. This is an unaffiliated project running Valve software on hardware Valve never targeted, and it is remarkable that it works at all. A
is the version where everything is supposed to work and someone is accountable when it does not.Questions People Ask
What is DroidDeck?
An open source Android app that runs Valve's real ARM64 Linux Steam client in Big Picture, with Deck mode on, and plays Windows games through Valve's ARM64 Proton. It is not streaming and not an emulator. It needs no root and does not replace Android. Version 0.4.0 released on 12 October 2026 under GPL-3.0, adding GOG, Epic and Amazon storefronts and a full KDE Plasma desktop.
Which handhelds can run DroidDeck?
Anything with an Adreno 730 or newer, or an 8xx Adreno, on Android 9 or later. In practice that means Snapdragon 8 Gen 2 and newer handhelds: the Retroid Pocket 6, Retroid Pocket Nova, AYN Thor, AYN Odin 2 Portal Pro and AYN Odin 3. Mali, Xclipse, PowerVR and Adreno 710 are unsupported, which rules out almost every Anbernic Android handheld.
Does DroidDeck work on a Retroid Pocket 5 or Flip 2?
Experimental rather than no, and that is a correction to what this page said earlier. Both use the Snapdragon 865 with an Adreno 650, which is below the Adreno 730 requirement, but the project describes 6xx as experimental rather than unsupported. DirectX 11 goes through DXVK 2 and may work; DirectX 12 games can still crash. There is a report of games failing to launch on a Flip 2.
If you own one of these, Armada is the better route. It lists both the Pocket 5 and the Flip 2 as tested devices. See the Retroid Pocket 5 and Flip 2 section above.
Is DroidDeck safe to install?
The project is open source under GPL-3.0 and publishes SHA256 sums with every release, so verify the file against those. The important part is where you get it. The team says it has no website and warns against download links from any site claiming to be them, and builds up to 0.1.6 were signed with a public test key that anyone could have forged an update with. Use the project's own releases page and check the hash. We make no judgement about any specific binary.
Why are there four APK files?
They are the same build signed under four different Android package names: DroidDeck's own, plus PUBG Mobile's, AnTuTu's and Ludashi's. The project explains that some phones only give their performance modes to apps with certain names. Each installs as a separate app with its own data. Start with the standard one.
Do I need root for DroidDeck?
No. You do need to turn off Restrict child processes in Android developer options. If your device does not show that option, which is common on Android 12 and 13, the app offers a "Fix it for me" button on first launch.
How much storage does DroidDeck need?
About 3 GB for the Linux runtime and another 1.1 GB if you add the desktop and emulators, before any games. Proton installs are large, so a 512 GB card is a sensible floor if you want more than a couple of Windows games on it.
Can I play multiplayer games with anti-cheat?
No. Kernel level anti-cheat does not work in this environment and is not going to. Plan around single player games and multiplayer that does not use it.
Does DroidDeck replace Android like ROCKNIX does?
No, and that is its main advantage. It is an ordinary Android app you can install and uninstall. You can optionally set it as your Android launcher so the device boots into Steam, but Android is still there underneath. ROCKNIX boots a separate Linux operating system and needs boot loader work.
Is DroidDeck made by Valve?
No. It is an independent community project and says so. Steam and Proton belong to Valve, and the project ships no Valve binaries of its own. Nothing about it is endorsed or supported by Valve.
Related Reading
- ROCKNIX Steam Guide: Run Steam Games on the Retroid Pocket 6 and AYN Thor
- Winlator Setup Guide: Windows Games on Android Handhelds in 2026
- FEX, Box64, Proton, DXVK: What Translation Layers Actually Do
- Linux vs Android Handhelds: Which Should You Buy
- Snapdragon 8 Elite Handhelds
- Decky Loader and Nexus Mods on Steam Deck
- Recompiled Games on Android: Every Port You Can Install
- DroidDeck vs GameNative vs GameHub vs Armada
- GameNative Setup Guide
- Turnip Drivers Guide
Written 5 October 2026, updated 12 October 2026 for the 0.4.0 release. Version numbers, the GPU requirement, feature lists, the startup timing figure, the APK variant explanation, the signing key history and the no-website warning all come from the DroidDeck project's own README, release notes, development log and build files, retrieved 12 October 2026. We no longer quote star or download counts, because they changed several times over in the week after this was first published. Bug reports are summarised from the project's open issue tracker. Device GPUs come from our own catalogue and reviews.
Correction, 12 October 2026: this article previously marked every Adreno 6xx handheld as a flat "No" and gave the current version as 0.3.0. The project's own requirements now describe Adreno 6xx as experimental, with DirectX 11 likely to work through DXVK 2 and DirectX 12 still able to crash, and 0.4.0 has since shipped. The compatibility table and version references have been corrected, and a pointer to Armada has been added for readers on those chips. We have not run DroidDeck on any device and publish no performance figures of our own.

