Unofficial guide. This site is not run by the DroidDeck team and hosts no APK files. Every download link goes to the official GitHub releases page.

DroidDeck Play Protect, Stuck on Waiting for Steam’s First Frame, and Black Screen Fixes

Checked against DroidDeck 0.7.1 · Last reviewed November 15, 2026 · Verified against Droid-Deck/DroidDeck, 0.7.1 release notes and upstream issue reports

Three startup blockers stop most Android handheld and phone setups before a single PC game opens: Google Play Protect blocking the sideloaded APK, the launcher stalling on “Waiting for Steam’s first frame”, and a DroidDeck (or “Droid Deck”) black screen after Big Picture starts. Every fix below comes directly from contributor notes and source code in the Droid-Deck/DroidDeck repository.

Advertisement

Safety rule before bypassing any Android warning: verify your APK against SHA256SUMS.txt from github.com/Droid-Deck/DroidDeck/releases. Never pause Play Protect for an APK downloaded from a third-party mirror, video link or chat attachment.

Match your exact DroidDeck error message

What appears on screenVerified root causeFix section
“Harmful app blocked” with More details > Install anywayPlay Protect unknown-app check on an APK outside Google Play (issue #351, issue #1270)Standard Play Protect prompt
“App blocked to protect your device. This app can request access to sensitive data” (no Install anyway link)Google Enhanced Fraud Protection blocking sideloaded APKs that declare BIND_ACCESSIBILITY_SERVICE (issue #2388, issue #2517)Sensitive-data block fix
“App not installed as package conflicts with an existing package”Test-key vs release-key mismatch (issue #436), or Samsung Galaxy Store / Device Care conflict on -pubg / -antutu APKs (issue #806)Signing key & Samsung fix
Stuck on “Opening Steam / Waiting for Steam’s first frame” on first launch ~650 MB Steam client archive unpacking silently inside PRoot with no progress bar (issue #75, issue #180, issue #780)First-launch unpack check
Stuck on “Waiting for Steam’s first frame” on every startAndroid Wayland Display driver vs container Runtime driver mismatch (issue #1881, issue #1995)Dual-driver manual fix
Droid Deck black screen in Big Picture while touch or FPS counter worksTurnip GMEM tile rendering or wrong Adreno family driver on steamwebhelper (issue #75)Black screen diagnostics
Black screen with “Abort game” after quitting, or stuck on Steam launch screenRegression in 0.7.0 fixed in DroidDeck 0.7.1Update & per-game fixes

DroidDeck Play Protect warning and SHA-256 verification

DroidDeck is open-source GPL-3.0 software published on GitHub Releases rather than the Google Play Store. As contributors note in issue #351 and issue #1270, Google Play Protect warns on newly published or sideloaded APKs that have not gone through Play Store distribution, and on some Android 16 and Android 17 builds the package installer aborts silently with INSTALL_FAILED_VERIFICATION_FAILURE (issue #1607).

Step 1: Verify the APK checksum before installing

Copy sites appeared within days of DroidDeck’s initial release (issue #297). Before tapping through any security dialog, download both DroidDeck-0.7.1.apk and SHA256SUMS.txt from Droid-Deck/DroidDeck/releases and confirm the SHA-256 hash matches:

  • Linux or Termux on Android: run sha256sum -c SHA256SUMS.txt --ignore-missing in your Downloads folder and confirm DroidDeck-0.7.1.apk: OK.
  • macOS Terminal: run shasum -a 256 DroidDeck-0.7.1.apk and compare the 64-character hex digest with SHA256SUMS.txt.
  • Windows PowerShell: run Get-FileHash DroidDeck-0.7.1.apk -Algorithm SHA256 and compare the Hash output against SHA256SUMS.txt.

Step 2: Pass the standard Play Protect sideload prompt

When Android shows the Play Protect sheet with a More details chevron, tap More details and then tap Install anyway. Android may ask for your PIN or fingerprint to confirm.

Fix “App blocked to protect your device” (sensitive data)

In regions where Google Play Protect enforces Enhanced Fraud Protection (reported across India and Southeast Asia in issue #1928, issue #2388 and issue #2517), Android blocks browser-downloaded APKs that request BIND_ACCESSIBILITY_SERVICE or BIND_NOTIFICATION_LISTENER_SERVICE and removes the “Install anyway” option altogether.

Why DroidDeck triggers that rule: earlier builds included both BottomNotificationListener and HomeButtonService. Pull request #2342 (shipped in 0.7.1) removed BottomNotificationListener specifically because Google’s fraud protection blocks sideloaded apps declaring a notification listener. HomeButtonService (BIND_ACCESSIBILITY_SERVICE) remains in AndroidManifest.xml so optional controller Home shortcuts, Alt+Tab / Win key capture, and dual-screen window detection can work when enabled (and since 0.6.9 the service stays disabled in Android until you turn it on, so banking apps no longer flag it while off).

  1. Update to DroidDeck 0.7.1 or newer first so you have the PR #2342 manifest cleanup, and verify its hash against SHA256SUMS.txt.
  2. Open the Google Play Store app and tap your profile icon in the top-right corner.
  3. Tap Play Protect, then tap the Settings gear icon in the top-right corner.
  4. Turn off Scan apps with Play Protect and confirm with your device PIN or biometric prompt.
  5. Install the verified DroidDeck-0.7.1.apk from your file manager.
  6. Return immediately to Play Store > Play Protect > Settings and turn Scan apps with Play Protect back on (issue #1607, issue #2517).

Fix signing key conflicts and Samsung APK errors

  • Release key vs CI test key (issue #436): APKs on GitHub Releases and pr-* / main-* prereleases on DroidDeck-CI use the project’s release signing key, whereas GitHub Actions workflow artifacts and self-compiled APKs use a public test key. Android blocks in-place updates across keys; uninstall the test build before installing a release APK (note that uninstalling deletes internal container data).
  • Samsung Galaxy Store and Device Care conflict (issue #806): each release ships four APKs with identical code under different package names. On Samsung One UI phones and tablets, -pubg (com.tencent.ig) and -antutu (com.antutu.benchmark.full) collide with Samsung’s built-in packages. Install the standard DroidDeck-0.7.1.apk (com.droiddeck.launcher).
Advertisement

Stuck on “Waiting for Steam’s first frame”: how startup works

Inside DroidDeck’s Android source (app/src/main/res/values/strings.xml), load_opening_steam_detail displays the exact message “Waiting for Steam’s first frame” while the Ubuntu 26.04 LTS PRoot container launches Valve’s native ARM64 Steam client, starts gamescope and Xwayland, and waits for the first Vulkan-composited frame to cross the shared-memory / DMA-BUF bridge into Android’s DroidDeckWayland surface.

Cause 1: Silent ~650 MB Steam unpack on first launch

Contributors explain in issue #75, issue #180 and issue #780 that DroidDeck’s progress percentage covers downloading the ~650 MB Steam bootstrap update, not verifying and extracting its archives inside user-space PRoot. During extraction, the status line sits on “Waiting for Steam’s first frame” with zero percentage movement for 10 to 15 minutes depending on UFS storage speed. Once unpacked, warm starts finish in roughly 10 to 25 seconds (issue #180). On a fresh install, plug into power, keep DroidDeck in the foreground, and give the first launch a full 15 minutes before force-stopping.

Cause 2: Child process restrictions or split-tunnel VPN

  • Android child process killer: on Android 14 and newer, open Settings > Developer options and turn Disable child process restrictions on (and keep Developer options enabled afterwards). On Android 12 and 13 where that toggle is hidden, tap Fix it for me on DroidDeck’s setup banner to pair Wireless debugging. Details are in the DroidDeck install guide.
  • Interrupted Steam client bootstrap (issue #225, issue #987): split-tunnel VPNs often block Valve’s CDN inside the PRoot container (issue #987). Switch your VPN to Global mode (or configure Setup > Download > HTTP proxy). If two launches exit without drawing a frame, DroidDeck automatically re-downloads the Steam client while preserving installed games, or you can trigger Steam settings > Client > Repair Steam client > Repair (issue #225).

Fix Wayland Display Driver vs Runtime Driver mismatch

If “Waiting for Steam’s first frame” hangs on every launch even after the ~650 MB unpack completed, check DroidDeck’s dual-driver architecture. DroidDeck loads two independent Vulkan drivers:

  • Runtime driver: runs inside the Linux container for gamescope, Steam Big Picture and Proton games (takes effect on the next session).
  • Display driver: runs on the Android host side for DroidDeckWayland to present frames onto your screen (takes effect after restarting the DroidDeck app).

In issue #1881 and issue #1995 (on Snapdragon 8 Gen 5 / Adreno 829 devices) and issue #75 (on Adreno 810), logs showed gamescope rendering Steam Big Picture at 90 fps inside the container while the auto-selected Android display driver (turnip-sdk36) logged present: no physical devices or dmabuf import failed in wayland.log. Because no frame ever reached Android’s surface, the UI remained stuck on “Waiting for Steam’s first frame”.

  1. Open Setup > GPU drivers (or Components > GPU drivers).
  2. Change the mode from Auto to Manual.
  3. On Adreno 8xx (Snapdragon 8 Elite, 8 Gen 5, 8s Gen 4; Adreno 825, 829, 830, 840): choose DD-Turnip, WinNative · Balanced, or Banners-Turnip · Adreno 8xx so both the Runtime driver and Display driver match, and wait for both downloads to complete (issue #66, issue #1881, issue #1995).
  4. On Adreno 810 (Snapdragon 7s Gen 3, issue #75): enable Show drivers for other GPUs and pick the Banners-Turnip (7xx) pair instead of an 8xx build.
  5. On Mali / Immortalis GPUs (MediaTek Dimensity, Google Tensor G1 to G4, issue #218, issue #2383): keep the Android Display driver on Auto so MaliBridge handles Android gralloc presentation. Manually forcing a PanVK Android display half stalls Mali at “Waiting for Steam’s first frame” (issue #2383).
  6. Force-close and reopen the DroidDeck app before pressing Play so the new Android Display driver loads cleanly.

Droid Deck black screen diagnostics and GPU fixes

Whether you search for a DroidDeck black screen or a Droid Deck black screen, separate a whole-client black window from a single-game black window before changing settings:

1. Pitch-black Steam Big Picture while touch sounds or FPS overlay work

Steam’s Big Picture interface renders through Chromium (steamwebhelper) > ANGLE > Zink > Turnip. In issue #75, contributors traced solid-black Big Picture frames on certain Adreno firmware to Turnip tile-memory (GMEM) rendering failing without system-memory fallback, or Auto picking the wrong Adreno generation. Update to DroidDeck 0.7.1 (which enables TU_DEBUG=sysmem for Steam’s Chromium client and is required on Adreno 720/722) and apply the matched manual Turnip pair in the GPU driver steps above.

2. Black screen with “Abort game” after quitting, or stuck at Steam launch screen

Version 0.7.0 introduced two session-lifecycle bugs: games stalling at Steam’s launch card when started from DroidDeck’s library, and a black screen showing “Abort game” or an endless spinner after exiting a game back to Steam. Both were fixed in DroidDeck 0.7.1. Open Updates inside DroidDeck or install the latest APK from DroidDeck APK download.

3. Scaling, resolution or external USB-C display black screen

If Big Picture goes black only after raising resolution, turning on upscaling, or plugging into a USB-C monitor / Samsung DeX dock, open Steam session > Display, cap Resolution at Up to 720p or Up to 900p, disable FSR / Snapdragon GSR scaling for one test session, and confirm output on the phone’s built-in screen first.

4. Only one Windows game opens to a black screen

When Steam Big Picture renders normally but one title opens black (issue #160, issue #660):

  • In Steam, open the game’s Properties > Compatibility and switch between Proton Experimental ARM64 and Proton 11.0 ARM64 (keep builds marked compatible with DroidDeck’s prefix fixes).
  • Add -dx11 in Steam Launch Options, especially on experimental Adreno 6xx chips (such as Snapdragon 865 / Retroid Pocket 5) where DirectX 12 VKD3D-Proton often crashes or draws black.
  • For older Direct3D 9 to 11 titles, open DroidDeck’s per-game Game environment settings and test PROTON_USE_WINED3D=1 (OpenGL over Zink / Vulkan instead of DXVK).

Supported Android & Snapdragon GPU quick check

Many “session ended” or black-screen reports come from unsupported graphics hardware. Check your GPU against DroidDeck’s documented tiers (full model table on DroidDeck supported devices):

GPU tierExample chipsets & devicesStatus
Adreno 730+ and Adreno 8xxSnapdragon 8 Gen 1, 8+ Gen 1, 8 Gen 2, 8 Gen 3, 8 Elite, 8 Elite Gen 5 (Galaxy S22 Snapdragon/S23/S24 Ultra/S25/S26, OnePlus 12/13, Odin 2, AYN Thor)Supported range
Adreno 722 (Retroid Pocket Duo)Retroid Pocket Duo dual-screen handheldShown as Supported since 0.6.7
Adreno 6xxSnapdragon 865 / 870 / 888 (Retroid Pocket 5, Logitech G Cloud)Experimental (prefer DirectX 11)
Mali, Xclipse, PowerVRMediaTek Dimensity, Samsung Exynos (Xclipse 940/950/960), Google Tensor G1 to G5Initial experimental support since 0.7.0 (issue #218 open; PowerVR grayscale fixed in 0.7.1)
Adreno 710Snapdragon 7s Gen 2 and mid-range variantsNot supported

Collect Share logs properly before reporting

If none of the fixes above resolves your black screen or first-frame hang, use Share logs inside DroidDeck’s Setup screen or session drawer. Never manually zip Download/DroidDeck/ in an Android file manager: contributors warn in issue #180 that Android scoped storage hides the live container logs and produces an empty zip. Inside the generated Share logs archive, check three files first:

  • device.txt: confirms the detected SoC, Vulkan driver version, Runtime driver and Display driver pair.
  • wayland.log: reveals present: no physical devices or dmabuf import failed when the Display driver cannot present frames.
  • session.log: records VK_ERROR_INCOMPATIBLE_DRIVER, network resets during Steam bootstrap, or Android phantom-process kills.

Attach that zip in the #bug-reports forum of the DroidDeck Discord or on GitHub Issues. For “Loading user data” stalls, SD card mounts and Epic Games sign-in errors, continue to the DroidDeck troubleshooting guide.

Controllers for Steam games on a phone

Most PC games expect a gamepad. Pair the controller with Android over Bluetooth, or plug it into USB-C, before you start a session; in Steam sessions the pad is presented as a Steam Deck controller with a Quick Access button, version 0.4.0 added up to four controllers for local co-op, and 0.6.9 added button shortcuts per controller in Setup > Controller > Button mapping. Handhelds such as the AYN Odin 2 or Retroid Pocket already have controls built in.

ControllerTypeGood for
GameSir G8 PlusStretch grip that holds the phone, BluetoothPhones and small tablets; the Bluetooth model leaves the USB-C port free for charging
Backbone One (USB-C, 2nd Gen)Stretch grip that plugs into the phone’s USB-C portLow latency and no pairing; check that your phone and case fit the grip
Xbox Wireless ControllerStandalone pad, Bluetooth or USB-C cablePlaying on a TV or monitor through a USB-C display output, or with a phone stand

As an Amazon Associate, this site earns from qualifying purchases. Controller links go to amazon.com; this site is not connected with the DroidDeck project or the controller makers.

Advertisement

Play Protect, first frame & black screen FAQ

Why does Google Play Protect block the DroidDeck APK?

DroidDeck is distributed on GitHub Releases rather than Google Play, so Play Protect flags it as an unrecognised sideloaded app (issue #351). In regions with Google Enhanced Fraud Protection enabled, Android also blocks internet-sideloaded APKs that declare an Accessibility Service such as DroidDeck’s optional HomeButtonService (issues #2388 and #2517). Verify the file against SHA256SUMS.txt before bypassing or pausing Play Protect for the install.

How do I install DroidDeck when Play Protect shows no “Install anyway” button?

First confirm your APK matches SHA256SUMS.txt from the Droid-Deck/DroidDeck GitHub release. Then open Google Play Store, tap your profile icon, open Play Protect, tap Settings (gear icon), turn off “Scan apps with Play Protect”, install the verified DroidDeck APK, and turn “Scan apps with Play Protect” right back on (issues #1607 and #2517).

Why is DroidDeck stuck on “Waiting for Steam’s first frame”?

On the very first launch, Steam downloads and unpacks roughly 650 MB inside DroidDeck’s Ubuntu PRoot container, and the unpack phase has no percentage bar, so the screen can stay on “Waiting for Steam’s first frame” for 10 to 15 minutes (issues #75 and #180). If it happens on every start, the Android Wayland display driver and the container Linux Turnip driver do not match on your GPU (issues #1881 and #1995); switch GPU drivers from Auto to Manual, pick a matched Turnip pair, and restart DroidDeck.

How do I fix a Droid Deck black screen when Big Picture has audio or touch response?

Steam Big Picture renders through Chromium, ANGLE, Zink and Turnip. When Turnip tile rendering fails or Auto loads the wrong Adreno family driver (issue #75), the frame stays black even while input and the FPS overlay work. Update to the latest DroidDeck release (which sets TU_DEBUG=sysmem for Steam) and select a matched manual Turnip driver pair under GPU drivers.

Why does DroidDeck fail to install on a Samsung Galaxy phone with a package conflict?

Two causes appear in the issue tracker: switching between a test-key CI artifact and a release-key GitHub APK without uninstalling first (#436), or installing the -pubg or -antutu package-name variants on Samsung One UI where Galaxy Store and Device Care conflict with those package IDs (#806). Use the standard DroidDeck APK (com.droiddeck.launcher) on Samsung devices.

Should I manually select a PanVK display driver on a Mali phone?

No. Issue #2383 and DroidDeck’s driver menu notes show that forcing a manual PanVK Android display half stalls Mali gralloc at “Waiting for Steam’s first frame”. Leave the Android display driver on Auto so MaliBridge handles presentation.

How do I export DroidDeck logs when troubleshooting a black screen?

Use Share logs in Setup or in the session drawer. Do not manually zip Download/DroidDeck/ in an Android file manager, because Android scoped storage omits the internal container logs and produces an empty archive (issue #180).

Back to the DroidDeck guide, DroidDeck APK download or install guide.