Droid-Deck/DroidDeck

This issue is mixing a few different cases, so it may be easier to split it so each one gets its own logs and fix:

- @brunocalmon, Pixel 5 (Adreno 620): this looks like #261, same GPU family (Adreno 6xx, below the tested hardware) and Unity games failing (Cuphead is Unity). Please follow #261 and try the steps there on the latest version and report there with logs.

- @Furina-imw, Redmi K60 (Adreno 730): that's supported hardware, so if nothing launches it's a different problem. Could you open a new issue with the game you tried and the newest session folder from Download/DroidDeck (zipped; it's written when the session ends)? But FIRST, could please try default settings of the latest release?

- @bradsour, Adreno 825: since one game works and others don't, it's probably game-specific. A separate issue per game, with its session folder, makes each one easier to fix. But FIRST, could please try default settings of the latest release?

Please use the latest version first; a lot of launc...

A correction to my earlier request: please don't zip the folder in Download/DroidDeck by hand. Android doesn't let file managers read DroidDeck's log files there, so that zip comes out empty. Use the app's own button instead:
- **During the session:** open the drawer → Support → Session logs → **Share logs**
- **From the launcher:** settings → Latest session logs → **Share logs**

It would also be worth trying #225. If the Steam client's own download or update was interrupted (a full storage, for example), the client can be left unable to start. #225 downloads it again, and keeps your games, sign-in and settings.

1. Make sure you have a few GB free.
2. Install the test build: https://github.com/Droid-Deck/DroidDeck-CI/releases/tag/pr-225 (or the Updates screen's test builds section).
3. On the home screen, open **Steam's settings** → **Client** → **Repair Steam client** → **Repair**, then start Steam.

If it still crashes, please attach the zip from **Share logs**.

Thanks for the report. The Google Drive link asks for a sign-in, so we can't open the log.

Could you attach the session log directly to this issue instead?

1. On the device, open **Download/DroidDeck/** and find the folder for the session that crashed (named by date, e.g. `2026-10-03-02-steam`).
2. Zip that folder and drag the zip into a comment here. GitHub accepts .zip attachments.

The logs are scrubbed of personal info (no serial, account names or network names), so they're safe to post.

Also, please check how much free storage the device has. Another user with the same symptom found their storage was full, and Steam needs several GB free for its first-run update.

I have aonly been able to get one game to launch thus far (Absolute Drift)
Device: Lenovo Idea Pad 2
Processor: Snapdragon® 8s Gen 4 (SM8735P) Mobile Platform
Graphics: Qualcomm® Adreno™ 825

> Hmm perhaps because of this "Use Android 9 or newer on a supported Adreno device (730 or newer, or 8xx)."

My phone runs Android 15 and meets the requirements, but it still won't launch; it seems there are still some unknown issues. In Bannerlator, I can still run the Steam client, but I can't seem to find a place to add non-Steam games. This is a great project that makes it easy for me to do that, and I hope to experience it soon.

Had same issue.
In the pre-Steam menus, I changed Controller Type from Deck Controller to Xbox Controller, and that fixed it.

When you have Halo MCC, then install it with one game Halo install all components and the game that I want to start running now.
for me it fix it but its not rly a good Solution

According to logs, steam is just installing an update, droid deck just don't show it, idk

Same with retroid pocket 6

happens to me too but I have the retroid pocket G2

Running into a similar issue with CrossCode.
We basically need a way to install ms components like vcrun. Technically Steam's first setup should install these too but this is still early days.
I was hoping that maybe ProtonPlus from flatpak would detect the steam install but also no dice.

Turns out my storage was entirely full which caused the problem

Same problem here

i hope it gets fixed because im hopeful for this emulator

I'm on the same boat, it seems to detect the controller (because it shows up the touch controlls if I disconnect it in the quick settings menu), but it doesn't respond to any kind of input