The "Child Processes" Fix, Explained (and the "Fix it for me" Button)

2026-10-14 · sourced from the official README (linked below)

The single most common DroidDeck setup problem is games getting terminated partway through a session. The cause isn't DroidDeck itself — it's a standard Android battery/process management behavior: the system restricts background child processes, and DroidDeck's Linux runtime depends on exactly that kind of process tree.

What the official documentation says

The project README's install steps are explicit about this: before launching Steam, disable "Restrict child processes" in Developer options. On Android 12 and 13, where that toggle is missing from some firmware builds, the app shows a "Fix it for me" button on first launch that applies the change automatically. (README — Install section)

The ADB fallback

Community guides (ours included) have also described the adb command that raises the process limit:

adb shell device_config put activity_manager max_phantom_processes 2147483647

This is the same category of fix — stopping Android from capping DroidDeck's process tree. Users on some devices (for example Odin 2 Portal Pro units, per community reports) report the developer option not existing where guides say it should; on those devices the in-app button or the ADB route is the way through.

Which fix should you use?

First choice: the in-app "Fix it for me" button (newest builds, Android 12/13).
Second: toggle "Restrict child processes" off manually in Developer options, if your firmware has it.
Fallback: the ADB command above from a PC.

Primary source: Droid-Deck/DroidDeck README. Community context: r/OdinHandheld.