GrapheneOS only publishes updates for devices with active security updates. Your device is EOL and therefore won’t receive any further mainline updates. It still will receive extended support from the Android 14 legacy branch with whatever security patches arrive in upstream AOSP, but unlikely to see device-specific patches nor firmware patches. Your device isn’t getting the same care and attention that active devices are receiving nor will it receive any future versions of Android through GrapheneOS.
The best three brands with natively-supported hardware:
- HTC’s Vive series headsets
- Bigscreen’s Beyond
- Valve’s Index
Pretty much everything else requires a lot more tinkering than just launching SteamVR/OpenVR applications.
Some helpful links for diagnosing compatibility:
The easiest ways to run custom executables for Proton titles is either going to be SteamTinkerLaunch or my shim script.
Tiny 11 comes in two variants:
Tiny11 Core is not suitable for use on physical hardware as it outright disables updates. It’s best used for short-term VM instances.
Tiny11 also has problems with updates. The advantages gained through Tiny11 will erode with applying Windows updates. The installer is more tolerable than Windows 11 by not forcing an online account (but still needing to touch telemetry settings). Components like Edge and One drive will inevitably rebuild themselves back in with cumulative updates. If this is something that coerces you to not update your system, don’t subject yourself to using Tiny11. Additionally Tiny11 fails to apply some cumulative updates out of the box, which could be a further security risk.
I recently tested the main Tiny11 in a VM based on a different user recommending it in a now deleted thread. I was skeptical knowing the history of Tiny10 onward that 11 would actually be able to update properly, and NY findings backed up my initial skepticism of functional updates.
Check for and kill all wine-related processes and then swap Proton versions for the game again.
Seeing prefix breakage messages with a wine version mismatch is often because of remnants of WINE processes that didn’t stop correctly. Steam prevents game launches for games that still have child processes present from previous launches.