Files
DroidDeck/docs/quest.md

1.9 KiB

Experimental Quest 3/3S support

Quest 3/3S runs DroidDeck as a 2D panel. This does not add immersive VR or OpenXR support. Quest 2 is outside the bundled Adreno 7xx driver path.

The first launch on Quest 3/3S 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"

The release variant quest produces a separate com.droiddeck.quest APK with its own app data. All installed packages use their own bwrap socket. The standard APK also applies Quest defaults when running on Quest 3/3S.

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.