One check at a time
Fix a DroidDeck setup one check at a time
Choose the stage that stopped, then the Android band and the DroidDeck version. Each card says why it matters and what success looks like. You can step backward.
Step 1
Where did it stop?
Stages
- APK installThe package never finishes installing, or the file came from somewhere other than GitHub Releases.
- Runtime downloadThe app is installed, and the Linux runtime has not finished.
- Steam launchPlay does nothing useful, Steam closes, or the first launch never reaches login.
- Steam loginSteam is on screen and the account sign-in is the part that stops.
- A game launchSteam itself is open. One Windows game is the part that fails or looks wrong.
- Controller or audioPicture is up, and input or sound is the broken piece.
Troubleshooting questions
Steam closes on Android 12 or 13. What does the README say?
Turn off Restrict child processes in Developer options. If that option is missing on Android 12 or 13, the first Steam launch offers Fix it for me. Those are the 0.4.0 README words.
The screen stays black. Is that always a GPU fault?
No. A runtime that never finished, a child-process kill, and a game still sitting on a loading screen are different stops. The wizard asks which stage you are in before it talks about DirectX.
The controller does nothing.
On 0.4.0 the release notes describe up to four controllers and several emulation modes switched from the session menu. Confirm the mode under test before changing the game profile. This site has not measured those modes.
Should I upload a log to this website?
No. Share logs inside DroidDeck builds a scrubbed zip for the project Discord. This site does not accept logs, account details, or debug access.
Do these steps apply to every DroidDeck version?
They are written for 0.4.0. If you select 0.3.x or an unknown build, the wizard says so. Menu names move between releases.