DroidDeck/docs/quest.md

Experimental Quest 2/3/3S support

Quest 3/3S runs DroidDeck as a 2D panel. This does not add immersive VR or OpenXR support. Quest 2 has a separate experimental Adreno 6xx driver path.

Quest 2 selects turnip26.3.0-quest2, a pinned Banners-Turnip A6xx/A7xx build with the same GPUOBJ adapter. It does not select the Quest 3 A7xx binary. The first Quest 2 launch applies manual driver selection and the SurfaceControl workaround, even if questDefaultsV1 exists from an earlier install. Later user choices are retained. The separate turnip26.3.0-a6xx bundle provides a plain Adreno 6xx offline fallback for other devices; their driver Auto behavior remains. Neither family-wide hardware coverage nor Quest 2 operation has been verified.

The A6xx input URL and SHA-256 are pinned in tools/quest/build-driver.py. Both A6xx bundles are prepared by the existing local/CI wrapper build step and covered by runtime-input attestation. Quest 3/3S retains its original driver. Early installation and compositor breadcrumbs are written to driver-setup.txt in private files and, when available, the app's external files directory. They do not require a Steam session. The existing Quest Java crash file now also applies to Quest 2; native crashes still require Android logcat.

Install the standard DroidDeck APK on Quest 3/3S. Device detection on the first launch selects manual drivers, the bundled turnip25.1.0-quest1 Android driver and the default Linux driver. It enables hdr.steam to use the existing SurfaceControl presentation workaround from the Quest report. These defaults apply once; subsequent user changes are retained. Colour accuracy and headset performance still need testing.

Both the Android driver wrapper and the Linux session preload use tools/quest/kgsl_compat.c. Successful legacy allocation/free calls are unchanged. Only EACCES/EPERM failures retry through GPUOBJ_ALLOC, GPUOBJ_INFO and GPUOBJ_FREE. The Android wrapper depends on the original bundled Turnip binary. Unhandled controller ioctls forward to the next preload hook rather than skipping it with a raw syscall.

tools/build_local.sh and CI build the wrapper from source using the pinned Android NDK; the normal preload builds include the shared Linux adapter. Runtime input verification checks the resulting driver archive and invalidates stale prepared assets after compatibility sources change. To rebuild only the Android driver archive:

python3 tools/quest/build-driver.py "$ANDROID_HOME/ndk/27.3.13750724"

Quest compatibility is included in the standard APK; no separate Quest package is needed. Other devices retain their existing defaults. The remaining performance-name APK variants continue to use separate app data and bwrap sockets.

Quest 3 testers have successfully launched games.

On a headset, check the Steam login panel, sign-in, game installation and then an owned game's rendering/input. Capture the device/OS, session logs, files/quest-startup.txt and any files/quest-last-crash.txt failure. Host allocation and preload-chain tests do not establish headset operation.