Step by step
Check the required Android setting
Open Developer options and turn OFF Restrict child processes.
Complete the fallback when needed
If the toggle is unavailable, select Fix it for me in DroidDeck and finish the wireless ADB setup.
Retry Steam
Return to the app and press Play. On the first launch, ensure the connection permits the Steam client download.
Share the newest session
Use Share logs from Setup or the session drawer after reproducing the exit. Tell project support whether Steam ever appeared and provide your exact device and app version.
Symptom: Steam disappears or returns to the launcher
A short-lived session can feel like nothing happened. Check the child-process setting before repeatedly reinstalling DroidDeck or clearing its storage.
First check: Android child-process restrictions
The official install instructions require Restrict child processes to be turned off before Steam launches. When the toggle is missing, use DroidDeck's Fix it for me flow and finish its wireless ADB pairing step.
This is the first setup check, not a diagnosis of every silent exit. A blocked first Steam download is another community-reported cause of a session returning to the launcher.
Find the logs that are available
No visible error does not necessarily mean there is no log. The official README says DroidDeck keeps recent session logs in app-private storage and provides Share logs in Setup or the session drawer.
Try to reproduce the problem once, then share the newest session with the project. Include whether the failure happens before sign-in, after sign-in, or only when a game starts.