- Non-Steam games on DroidDeck include GOG, Epic, and Amazon titles added through the built-in store integrations introduced in version 0.4.0.
- ARM64 Proton handles Windows games, while Linux-native titles run with fewer adjustments.
- Device requirements: Android 9 or newer with an Adreno 730-class or better GPU.
- Anti-cheat games may block launch or online play regardless of configuration.
- Start with defaults: test the recommended Proton version before changing compatibility settings.
What Non-Steam Games Mean on DroidDeck
DroidDeck is an open-source, SteamOS-style gaming platform for Android handhelds and high-performance Snapdragon devices. While its headline feature is bringing the Steam Big Picture experience to ARM64 hardware, version 0.4.0 expanded beyond Valve's ecosystem. The release added GOG, Epic, and Amazon Games integrations, giving Android handheld owners a way to install and launch non-Steam titles from a single console-style interface.
Non-Steam game support on DroidDeck covers three broad categories:
| Game Source | How It Runs | Setup Complexity | Notes |
|---|---|---|---|
| GOG titles | Native Linux build or ARM64 Proton | Low to Medium | DRM-free installs are the most flexible |
| Epic Games | Store integration + Proton | Medium | Requires Epic account sign-in |
| Amazon Games | Store integration + Proton | Medium | Catalog varies by region |
| Windows games (any source) | ARM64 Proton compatibility layer | Medium to High | Results vary by engine and DirectX version |
| Linux-native games | Direct execution | Low | Fewest compatibility adjustments |
Handheld gamers are not locked into a single store. DroidDeck's multi-store approach means a DRM-free GOG library, an Epic back catalog, and Steam purchases can coexist on one Android device with controller-friendly navigation.
Setup: Adding Non-Steam Games Step by Step
Before installing anything, confirm the device meets the baseline: Android 9 or higher, a compatible Snapdragon chipset with an Adreno 730 or newer GPU, and enough free storage for the runtime, prefixes, shader caches, and the games themselves.
Install and Initialize DroidDeck
Download the APK from the official DroidDeck download page or the GitHub Releases archive, complete the Android installation flow, and let the first-run environment setup finish before changing any settings.
Sign In to Your Store Accounts
In version 0.4.0 and later, connect GOG, Epic, or Amazon accounts through the built-in store integrations so your existing libraries appear in the DroidDeck game list.
Handle Android Process Restrictions
On Android 12 and newer, adjust the "Restrict child processes" setting in Developer Options if background processes are terminated during installation or gameplay.
Install the Game
Select a title from your connected library and let the first launch complete. Initial runs may take longer while prefixes and runtime components are prepared.
Test and Record Settings
Play for 10 to 20 minutes, note the working Proton version, resolution, and controller layout, and keep that record for future reinstalls.
Game installs need more space than the listed download size. Budget extra room for the compatibility prefix, shader cache, and updates to avoid failed installations mid-download.
Game Compatibility Categories
Not every non-Steam title behaves the same way. Sort expectations into four tiers before troubleshooting:
Usually Playable
- Linux-native builds need no Windows layer
- Verify controller detection
- Use default graphics profile first
Playable with Configuration
- Windows games via Proton vary by engine
- Test default Proton first
- Lower resolution before stacking changes
Needs Adjustment
- Launcher-dependent titles need extra runtimes
- Let first launch finish installing components
- Record working launch options
Often Restricted
- Kernel-level anti-cheat can block launch
- Online play may be unavailable
- Never disable security features to bypass
| Factor | Impact on Non-Steam Games | Adjustment |
|---|---|---|
| DirectX version | Older DX9/11 titles often run well through Proton | Try alternate Proton version on failure |
| Game engine | Unity and Unreal titles vary in ARM64 behavior | Test per game, keep per-game configs |
| Video codecs | Cutscenes may fail on missing codecs | Install required runtime components |
| System memory | Demanding titles stress limited RAM | Close background apps, lower settings |
| Anti-cheat | Kernel-level systems often block Proton | Check the game's Linux support status first |
A game launching is not the same as online play working. Anti-cheat compatibility is decided by each developer, and unsupported implementations can restrict matchmaking even when the single-player portion runs fine.
Performance Settings for Non-Steam Titles
Performance on DroidDeck depends on the Snapdragon chipset, Adreno GPU, Android version, driver, and Proton configuration working together. Build a stable profile instead of chasing peak numbers.
| Setting | Recommendation | When to Change |
|---|---|---|
| Resolution | Native when stable; scale down for demanding 3D | Frame-time spikes or stutter |
| Frame-rate cap | Set a cap the device can sustain | Long sessions or thermal throttling |
| Proton version | Default recommended build | Launch failures or rendering errors |
| esync/fsync | Leave at default | Diagnosing stutter or crashes, one at a time |
| Rendering API | Default driver path | Only when Vulkan/OpenGL comparison shows a clear issue |
Stacking Proton, resolution, driver, and launch-option changes together makes it impossible to identify which adjustment helped or broke the game. Keep a per-game configuration record.
Stable Performance Checklist:
- Confirm device meets Adreno 730+ GPU requirement
- Complete first-run initialization before tuning
- Test default Proton version before alternatives
- Monitor heat and battery after 10-20 minutes of play
- Record working per-game settings for reinstalls
Troubleshooting Non-Steam Game Issues
| Symptom | Likely Cause | First Fix |
|---|---|---|
| Game will not start | Incomplete runtime or prefix | Restart device, reinstall cleanly, check storage |
| Process killed mid-game | Android 12+ background limits | Disable battery optimization, adjust child process restriction |
| Black screen | Renderer or fullscreen mode conflict | Try windowed mode, lower resolution, test alternate Proton |
| No sound | Audio route changed after launch | Check media volume, reconnect Bluetooth audio, relaunch |
| Crashes after extended play | Thermal throttling or memory pressure | Lower resolution or frame cap |
When submitting issues to the DroidDeck GitHub Issues tracker, include the DroidDeck version, Android version, device model, exact symptom, and relevant logs. Complete reports get resolved faster.
FAQ
Q: Can DroidDeck run non-Steam games like GOG and Epic titles?
Yes. Starting with version 0.4.0, DroidDeck includes GOG, Epic Games, and Amazon Games store integrations, letting you install and launch non-Steam libraries from the same interface alongside Steam titles.
Q: What hardware do I need for non-Steam games on DroidDeck?
DroidDeck requires Android 9 or higher and works best with Qualcomm Snapdragon devices using an Adreno 730 or newer GPU. Mali, Tensor, and Xclipse GPUs currently have compatibility limitations.
Q: Do all Windows non-Steam games work through ARM64 Proton?
No. Results vary by game engine, DirectX version, launcher behavior, and available memory. Many titles run well with default settings, while others need Proton adjustments or may not launch at all.
Q: Why does my game close on Android 12 or newer?
Android 12 and later versions restrict background child processes. Adjust the 'Restrict child processes' Developer Options setting, disable battery optimization for DroidDeck, and keep the game in the foreground during play.