- DroidDeck shutting down Steam when launching a game is usually caused by Android background process restrictions
- Android 12+ devices may need the "Restrict child processes" developer setting adjusted
- Battery optimization silently kills the Steam runtime mid-launch, so disable it for DroidDeck
- Insufficient storage for Proton prefixes and shader caches also causes launch-time crashes
- Change one setting at a time and retest the same game to isolate the failing layer
Why DroidDeck Closes Steam During Game Launch
When DroidDeck shutting down Steam when launching a game occurs, the problem almost always sits at the intersection of Android process management and the Linux runtime that hosts Steam. DroidDeck runs a Linux environment on your Android device, and when a game launches, Steam spawns additional child processes for the Proton compatibility layer. Android interprets this burst of new processes as suspicious background activity and may terminate the entire app tree — closing Steam and the game with it.
The most common triggers fall into four categories:
| Trigger | What Happens | Frequency |
|---|---|---|
| Android 12+ process limits | System restricts or kills child processes Steam needs | Very common |
| Battery optimization | Runtime terminated when screen or app state changes | Common |
| Insufficient storage | Proton prefix or shader cache write fails during launch | Common |
| Proton / driver conflict | Game process crashes and takes Steam down with it | Occasional |
Aggressive task-killer and cleaner apps frequently terminate the DroidDeck runtime and Steam processes mid-launch. Uninstall or disable them before troubleshooting anything else, or your fixes will never hold.
According to the official DroidDeck FAQ (droiddeck.app/faq), some Android 12 and higher devices need the Restrict child processes setting adjusted in Developer Options before the Steam environment can sustain a game launch. This is the single highest-value fix, so start there.
Step-by-Step Fix for Steam Closing on Launch
Work through these fixes in order. After each step, relaunch DroidDeck, sign in to Steam, and test the same game so you know exactly which change resolved the issue.
Clean Restart
Close DroidDeck completely, remove it and any related processes from the recent-apps view, then restart the device. A stale background process from a previous failed session is the fastest problem to eliminate.
Adjust Developer Options
On Android 12 or newer, open Developer Options and review the Restrict child processes setting as described in the official FAQ. Restricting child processes prevents Steam from spawning the processes it needs to launch games through Proton.
Disable Battery Optimization
In Android settings, find DroidDeck under battery or app settings and disable battery optimization for it. Keep DroidDeck and the game in the foreground during testing — backgrounding during launch invites the system to reclaim the process.
Verify Storage and Runtime
Confirm the device has free space beyond the game's own size: Proton prefixes, runtime components, and shader caches all need room. If a previous installation was interrupted, reinstall from a clean state using the official download channel.
Test Proton and Rendering
If Steam still closes, test the game with the default Proton configuration, then try an alternative Proton version one change at a time. Also test windowed or borderless mode and a lower resolution, since fullscreen and shader compilation failures can crash the whole session.
Keep a note of the exact Proton version, launch options, and Android settings that produce a stable launch. When you reinstall or update DroidDeck, you can restore the working configuration instead of troubleshooting from scratch.
Settings That Prevent the Crash
Beyond the immediate fixes, a handful of device settings determine whether Steam survives game launches over the long term. Apply these as a stable baseline before testing demanding titles.
Process Management
- Restrict child processes: disabled or relaxed
- Task killers removed
- DroidDeck kept in foreground during launch
Power and Battery
- Battery optimization: off for DroidDeck
- Stable power delivery during long sessions
- Avoid low-battery gaming sessions
Environment Health
- Free storage: headroom for prefixes and caches
- Complete, uninterrupted runtime installation
- Current DroidDeck release from official sources
The table below maps symptoms to the settings most likely responsible:
| Symptom | Most Likely Setting | Fix |
|---|---|---|
| Steam closes the moment the game starts | Restrict child processes | Adjust in Developer Options |
| Steam closes after screen off or switching apps | Battery optimization | Disable optimization for DroidDeck |
| Crash only on heavy 3D games | Storage or thermal limits | Free space, lower resolution and frame rate |
| Crash on specific games only | Proton configuration | Test alternate Proton version per game |
Always confirm you are running the current DroidDeck release from the official download page or the GitHub Releases archive. Older builds may lack process-handling fixes present in recent updates.
Isolating Hard-to-Diagnose Cases
If the baseline settings do not stop DroidDeck shutting down Steam when launching a game, the failure is likely game-specific rather than device-wide. Isolate it methodically:
- Test a Linux-native game first. Native Linux titles skip the Proton layer entirely, so a successful launch proves the runtime, Steam session, and input stack are healthy.
- Swap one variable at a time. Changing Proton, resolution, rendering API, and launch options simultaneously makes it impossible to identify the fix.
- Check audio device changes. If a Bluetooth audio device connects or disconnects during launch, the audio subsystem can fail and take the session down. Reconnect audio before launching.
- Rule out anti-cheat. Online games with kernel-level or unsupported anti-cheat may refuse to launch at all. This is a developer decision, not a DroidDeck bug, and disabling security components to bypass it is never the answer.
| Diagnostic Test | What It Proves | If It Fails |
|---|---|---|
| Launch a Linux-native game | Runtime and Steam session are stable | Problem is environmental — revisit Steps 1–4 |
| Launch with default Proton | Baseline compatibility works | Game needs a different Proton version |
| Launch in windowed mode | Fullscreen mode is the culprit | Keep borderless or windowed for this title |
| Test with another controller | Input layer conflict | Switch between native input and Steam Input |
If Steam still closes after all fixes, report the problem on the official DroidDeck GitHub Issues page. Include the DroidDeck version, Android version and device model, the exact crash point, the active Proton version, and any startup or runtime log output.
Pre-Launch Checklist
Before Every Gaming Session:
- Restart device or clear DroidDeck from recent apps
- Confirm battery optimization is off for DroidDeck
- Verify at least a few GB of free storage
- Keep DroidDeck and the game in the foreground
- Test one title before changing advanced settings
FAQ
Q: Why does DroidDeck shut down Steam when launching a game?
In most cases, Android is terminating the child processes Steam needs during game launch. Android 12 and newer devices are especially prone to this. Adjusting the 'Restrict child processes' setting in Developer Options and disabling battery optimization for DroidDeck resolves the majority of cases.
Q: Does this problem affect all games equally?
No. Linux-native games place the lightest load on the launch path and are the best first test. Windows games running through Proton spawn additional processes and write shader caches, making them more sensitive to process restrictions and storage limits. Anti-cheat multiplayer titles may fail to launch for separate reasons controlled by the game developer.
Q: Should I reinstall DroidDeck if Steam keeps closing?
Only after applying the process and battery settings. If crashes persist, verify storage space and reinstall from a clean state using the official download channel. Never replace the official APK with an unknown modified build, and let the first-run runtime initialization finish completely before launching games.
Q: Where do I report the issue if nothing works?
File a report on the official DroidDeck GitHub Issues page or ask in the DroidDeck Discord. Include your DroidDeck version, Android version, device model, the exact symptom, the Proton version in use, and any startup or runtime log output so maintainers can reproduce the problem.