Files
DroidDeck/docs/development/rayneo-xr.md
T
+13 83eda433c8 Add VITURE XR controls, head tracking, and SteamVR (#732)
* Add VITURE glasses support: hardware control, 3D, head tracking

Glasses get their own controller over the MCU (permission, 120 Hz default, brightness, volume, sunblock, 2D/3D) and the game moves onto them when plugged in. The IMU drives Cardboard head tracking and the SteamVR driver. 3D falls back to one eye's view on phones that can't send the 3840x1080 signal. Options open from a glasses button in game and on the Steam page.

* Drop the glasses settings like Steam's: Play-style button, Settings lip, tabs

* Hang the glasses Settings lip over the top of the button

* Space glasses MCU commands so the IMU rate sticks, fit fixed resolutions to the glasses

* Keep Steam alive with SteamVR registered, run SteamVR at the glasses' rate, keep the glasses lip on top

* Fit VR games on the glasses: full view, seated origin at the head, pad hands reach with the d-pad

* Let the pad hands reach a metre out so buttons with deep colliders press

* Show every VR frame in order at 120 fps: wait for SteamVR's GPU work, present only finished copies, skip the grace on idle shared counters

* Glasses: SteamVR starts and stops with them, closer view with a field of view setting, Recenter on the pad

* Glasses: SteamVR field of view defaults to 90°

* VR pad hands: sticks move and aim the hands, left stick click switches the sticks to the game, d-pad pulls a held hand

* Glasses: Play SteamVR beside the glasses button instead of starting SteamVR with them, pad hands drawn as Index controllers and off while other VR controllers are connected, glasses sheet tabs sized like Steam's

* Track glasses mode, refresh-aware glasses window, align Play SteamVR with Play Steam

* Fix 3D on the glasses: full-res SteamVR presenter, revert VR 3D at session end, coalesce vsync ticks, no session restart after end

* Address review: glasses output after installs and session end, VR revert retry, display fallback, presenter swapchain retry, agent hex checks, drawer bumpers, glasses translations, docs

* Harden VITURE stereo negotiation and output refresh tracking

* Localize stereo recovery feedback and record Astra reconnect tests

* Improve test failure diagnostics and refresh Astra firmware findings

* Handle VITURE docks separately and reject truncated USB frames

* Glasses: remember a 3D fallback per model, docks as display only, VR timing fixes

- A 3D attempt that ends at the 640x480 fallback is remembered for that glasses
  model, so Play SteamVR no longer blacks out the glasses after every restart;
  Retry clears it and "3D for VR games" stays reachable
- A VITURE Mobile Dock on its own no longer counts as glasses; through a dock
  Play SteamVR is hidden and the sheet shows the output and why there is no control
- HDR is probed on the glasses when the session starts there
- Glasses frames with a mismatched checksum are marked in the status frame log
- SteamVR layer and driver vblank counters stay monotonic across refresh changes;
  one-eye render scale applies from activation and on mono/3D switches
- Compositor binds announce the refresh clients were last told; the presenter
  retries a failed first swapchain
- Dead strings and helpers removed; docs updated

* Glasses: drop USB frames with a bad checksum

* Glasses: count frames dropped for a bad checksum

* Feat/viture xr (#907)

* Add RayNeo Air and GT support to the XR glasses pipeline

* Add RayNeo Air and GT support to the XR glasses pipeline

* Checkpoint glasses tracking, calibration, and SteamVR launch integration

* Checkpoint glasses tracking, calibration, and SteamVR launch integration

* Add XREAL 1S support and correct GT and Pro 2 tracking

* Add XREAL 1S support and correct GT and Pro 2 tracking

* Fix mirrored glasses tracking and recover SteamVR after device loss

* Fix mirrored glasses tracking and recover SteamVR after device loss

* Document confirmed XREAL 1S brightness control

* Document confirmed XREAL 1S brightness control

* Fix SteamVR glasses defaults and rendering controls

* Fix SteamVR glasses defaults and rendering controls

* chore: keep only the 3 newest session log folders (#852)

* chore: add agent comment rules (#748)

Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>

* Fix SteamVR polling, VITURE checksums, and fence tracking

Keep manual SteamVR launches polled, discard corrupt VITURE packets, and retire Vulkan fences out of order without blocking submissions at a fixed capacity. Preserve the contiguous completion watermark used by the presenter.

Fix optional Windows launcher configuration and audited helper staging. Add Android, Windows, and native tracker regression coverage.

* Fix SteamVR polling, VITURE checksums, and fence tracking

Keep manual SteamVR launches polled, discard corrupt VITURE packets, and retire Vulkan fences out of order without blocking submissions at a fixed capacity. Preserve the contiguous completion watermark used by the presenter.

Fix optional Windows launcher configuration and audited helper staging. Add Android, Windows, and native tracker regression coverage.

* fix: wireless ADB page names the child-process switch the way Android shows it (#848)

* l10n: refresh stale and untranslated strings in es, fr, ko, ru (#850)

* l10n: refresh stale and untranslated strings in es, fr, ko, ru

- mode_added_art_hint: now mentions Steam then SteamGridDB (all four locales).
- wincomp_needs_installer / wincomp_installers_note: es and ko still described
  the old "coming soon" behaviour; align with the current English text.
- summary_remove_game: was still English in all four locales.

Machine-assisted translation; native-speaker review is welcome.

* l10n(es): say registro, not grabación, for the missing installer record

---------

Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>

* fix: a failed cloud save recovery no longer ends the app (#846)

The cloud-recovery thread started at every app start had nothing to
catch an error, so one went to CrashHandler, which halts the process
with status 2. In unit tests the thread can outlive the test that
started it, fail on the torn-down preferences, and take the whole test
run down. The error is now logged and the thread ends.

Co-authored-by: Kirk <12691869+KirkPatrickJunsay@users.noreply.github.com>

* fix: an interrupted Linux runtime download resumes instead of starting again (#847)

* fix: an interrupted Linux runtime download resumes instead of starting again

installOnce() asked the downloader to resume but always deleted the archive in its finally block, so the next attempt began at zero. The archive is now named after the release version and checksum, a failed download keeps what it fetched, and archives of other releases (and the old fixed name) are removed. A checksum or extraction failure still deletes the file.

* test: Downloader resumes a cut-off download from the bytes it kept

Starts a socket server that promises the whole file, hangs up part way and then answers a Range request, and checks that the second downloadFile call resumes with the right offset and ends with identical bytes.

* fix: a resumed download discards a 206 that does not start where the kept bytes end

Downloader appended every 206 response to the partial file without
looking at Content-Range. A server or proxy that answers a Range request
with a different offset would leave a corrupt file. Check that the range
starts at the kept length; otherwise delete the partial file and start
again without a Range header.

Adds a test with a server that answers the Range request from offset 0.

---------

Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>

* l10n: German, French, Spanish, Italian, Portuguese and Russian for the zRAM, reset-settings and store free-space strings (#849)

* l10n: German, French, Spanish, Italian, Portuguese and Russian for the zRAM, reset-settings and store free-space strings

Adds the strings values-de, values-it and values-pt were missing (14 each) and the six that values-fr, values-es and values-ru were missing. Machine-assisted drafts that follow each file's existing register and terms; native review is welcome.

* l10n: correct missing active swap translations

---------

Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>

* fix: droiddeckctl reaches variant-package builds (recover #842) (#854)

fix: droiddeckctl reaches builds shipped under a variant package

The provider authority and the start Activity's component were fixed to
com.droiddeck.launcher, so droiddeckctl could not talk to the antutu,
ludashi or pubg builds from tools/release/variants.txt. DROIDDECK_PACKAGE
now picks the package; the Activity's class name stays the same in every
variant.

Co-authored-by: angelrenefm <17342133+angelrenefm@users.noreply.github.com>

* feat: droiddeckctl reports on-screen pacing (recover #843) (#855)

feat: droiddeckctl pacing reports the frames that reached the screen

Reads SurfaceFlinger's timestats for the game's layer (or the session's
SurfaceView) over a capture: frames on screen, fps on screen, the
present-to-present histogram and how many intervals were off the usual
cadence. Records split by a refresh-rate change are summed. A game's own fps
counter counts frames handed over, so it can't show dropped or doubled frames.

Co-authored-by: angelrenefm <17342133+angelrenefm@users.noreply.github.com>

* fix: Steam can restart more than twice in a session (#754)

* fix: Steam can restart more than twice in a session

Every exit 42 counted toward the cap that stops an update which will
not install, and the count was never cleared, so the third restart of
a session ended it however far apart they were. A client that ran for
a minute before asking is not that loop: the count starts again.

* fix: measure the client's run time as it exits

The time spent collecting logs and checking FEX after the client exits
counted toward its run, so a slow cleanup could make a quick exit 42
look like a long one and clear the count.

---------

Co-authored-by: Kirk <12691869+KirkPatrickJunsay@users.noreply.github.com>
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>

* fix: the front end keeps its page when the Fold is folded or unfolded (#832)

* fix: the front end keeps its page when the Fold is folded or unfolded

MainActivity, FileManagerActivity, FilePickerActivity and StoreLoginActivity did not declare the screen-size configuration changes, so folding or unfolding a foldable recreated them and dropped their in-memory state. They now handle orientation, screenSize, screenLayout, smallestScreenSize and density themselves, like SessionActivity already does. uiMode is left out on purpose.

* fix: store login keeps rebuilding its toolbar when the display density changes

StoreLoginActivity builds its toolbar in code with dp-to-pixel values taken at creation time and has no onConfigurationChanged. It no longer declares density in configChanges, so a density change recreates it as before this PR. Size and layout changes are still handled in place.

---------

Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>

* Release pointer buttons without replaying stale motion (#803)

* Fix cursor warping on native touch down

* Preserve input cleanup without replaying stale pointer motion

---------

Co-authored-by: siyuan.qsy <siyuan.qsy@alibaba-inc.com>

* l10n: translate the strings added since #284 into zh-CN, zh-HK, zh-TW and ja (#539)

* l10n: translate the 184 strings added since #284 (zh-CN/HK/TW, ja)

The stores, cloud saves, Windows components, Steam touch, desktop
removal and background-downloads strings landed after #284's
translation snapshot, so every one of them fell back to English.
Translate all 184 into Simplified Chinese, Traditional Chinese
(Taiwan and Hong Kong) and Japanese, keeping each locale file's own
vocabulary (工作階段/會話, 解除安裝/卸載, 元件/組件, 設定).

Also fix four Hong Kong strings that kept the simplified 着色器.

* l10n(zh): fix stale and ambiguous strings found in review

Severe: summary_remove_game was untranslated English in all three
files; mode_added_art_hint, wincomp_installers_note and
wincomp_needs_installer still described the pre-#480/#492 English.

Also: distinguish the Setup wizard from Android system settings in
zh-HK/zh-TW (初始設定 / 系統設定 / Android 設定), unify library as
收藏庫, component as 組件 in zh-HK, session as 會話 in zh-HK, account
as 帳戶 in zh-HK, Trending as 趋势/趨勢, Forget as 清除, reword the
re-applied-at-launch, action-failed and already-in-Games strings, and
play as 執行/開啟遊戲 in zh-TW/zh-HK.

* l10n(ja): fix stale and ambiguous strings found in review

---------

Co-authored-by: Dantalian <Dantalian-dev@users.noreply.github.com>
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>

* Rebuild and verify Windows VR runtime components

* Rebuild and verify Windows VR runtime components

* Add top, bottom, and centered picture positions for Steam sessions (#871)

* fix: dependency scan ignores folders above the game folder (#859)

* DroidDeck-Proton: get releases from the Droid-Deck org repo

DroidDeck-Proton is now built and released on Droid-Deck/DroidDeck-Proton
(11-9.1 is Latest there), so the Components page, the update check and the
guest installer read releases from the org repo instead of The412Banner's.

* feat: low-latency controller and touch toggles in the session drawer (#808)

* fix: SteamGridDB lookups no longer stick as "no match" after a failure; add a search to the art chooser (#876)

* feat: Steam home wall fills from the signed-in library instead of store picks (#878)

* test: cover GPU family and support classification (#880)

* Fix local builds on Linux failing after the first Comet build (#866)

* feat: sort the store library and installed tabs, and switch between card and list views (#798)

* feat: three-finger tap toggles Steam's on-screen keyboard in game mode (#782)

* fix: keep Quest-patched Turnip as the auto default (#853)

* Fix deploy_local.sh and droiddeckctl not finding a phone connected over wireless debugging (#864)

* fix: keep proot sessions alive when the kernel loses fork events (#457)

* fix(quest): correct desktop and Steam display corruption across sessions (#733)

fix(quest): stabilize desktop and Steam layer presentation

Keep Quest SDR scenes and the black backdrop off the Android Vulkan swapchain regardless of session order or HDR preferences. Only report the first frame after client content is submitted.

Add backdrop lifecycle and first-frame regression coverage. Record the user's successful Quest 3 Test 2 result.

Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>

* fix: keep SteamVR syscall hooks and report Steam crashes (#905)

* fix: preserve SteamVR syscall hooks

* fix: report Steam crashes through gamescope

* fix: honor glasses pacing and resolution in SteamVR launches

---------

Co-authored-by: connor g <connorsspam1992@gmail.com>
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
Co-authored-by: Yassine Gherbi <y.gherbi.dev@gmail.com>
Co-authored-by: Resul Övür <92828257+ovurrsl@users.noreply.github.com>
Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>
Co-authored-by: Kirk <kirtoy.junsay@gmail.com>
Co-authored-by: Kirk <12691869+KirkPatrickJunsay@users.noreply.github.com>
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>
Co-authored-by: angelrenefm <17342133+angelrenefm@users.noreply.github.com>
Co-authored-by: asdf17128 <asdf17128@gmail.com>
Co-authored-by: siyuan.qsy <siyuan.qsy@alibaba-inc.com>
Co-authored-by: Dantalian <wsu091227@qq.com>
Co-authored-by: Dantalian <Dantalian-dev@users.noreply.github.com>
Co-authored-by: The412Banner <the412banner@users.noreply.github.com>
Co-authored-by: The412Banner <205237651+The412Banner@users.noreply.github.com>
Co-authored-by: FX1922 <120828496+FX192@users.noreply.github.com>
Co-authored-by: Muaz Kadan <32595066+muazkadan@users.noreply.github.com>
Co-authored-by: kingokksa <47888451+kingokksa@users.noreply.github.com>
Co-authored-by: Jamie Schenker <jam1esch3nk3r@gmail.com>
Co-authored-by: Jagger15 <jagger2333@live.com>

* Glasses: keep a pending 2D restore and the SteamVR recovery offer, show Play SteamVR only with a picture

* Translate the glasses calibration, XREAL and SteamVR recovery strings

* SteamVR recovery: give a finished teardown time to collect logs before restarting

* Credit the projects the XR glasses support builds on

* Joy-Cons: SteamVR hands from their gyro while SteamVR runs, one combined pad otherwise

* Headsets: settings badge on Play SteamVR instead of a top-right button, both shown only once connected

* Hand tracking: camera-tracked Joy-Cons and bare hands in SteamVR, drawn as white gloves

- Joy-Con movement from the accelerometer (report reordering, per-Joy-Con calibration, zero-velocity updates)
- MediaPipe pose and hand landmarks from the device camera, placement check, per-hand Kalman filter with the Joy-Con
- No controller connected: bare camera hands with Quest-style gestures, 1€ filtered, rendered as a white glove model built from a distance field
- SteamVR safe mode cleared before each start so one crash no longer blocks the driver

---------

Co-authored-by: MaxsTechReview <6025299+maxjivi05@users.noreply.github.com>
Co-authored-by: informalTechCode <informaltechyt@gmail.com>
Co-authored-by: connor g <connorsspam1992@gmail.com>
Co-authored-by: Kurt Himebauch <136133082+xXJSONDeruloXx@users.noreply.github.com>
Co-authored-by: Yassine Gherbi <y.gherbi.dev@gmail.com>
Co-authored-by: Resul Övür <92828257+ovurrsl@users.noreply.github.com>
Co-authored-by: ovurrsl <ovurrsl@users.noreply.github.com>
Co-authored-by: Kirk <kirtoy.junsay@gmail.com>
Co-authored-by: Kirk <12691869+KirkPatrickJunsay@users.noreply.github.com>
Co-authored-by: xXJsonDeruloXx <danielhimebauch@gmail.com>
Co-authored-by: angelrenefm <17342133+angelrenefm@users.noreply.github.com>
Co-authored-by: asdf17128 <asdf17128@gmail.com>
Co-authored-by: siyuan.qsy <siyuan.qsy@alibaba-inc.com>
Co-authored-by: Dantalian <wsu091227@qq.com>
Co-authored-by: Dantalian <Dantalian-dev@users.noreply.github.com>
Co-authored-by: The412Banner <the412banner@users.noreply.github.com>
Co-authored-by: The412Banner <205237651+The412Banner@users.noreply.github.com>
Co-authored-by: FX1922 <120828496+FX192@users.noreply.github.com>
Co-authored-by: Muaz Kadan <32595066+muazkadan@users.noreply.github.com>
Co-authored-by: kingokksa <47888451+kingokksa@users.noreply.github.com>
Co-authored-by: Jamie Schenker <jam1esch3nk3r@gmail.com>
Co-authored-by: Jagger15 <jagger2333@live.com>
2026-10-17 13:17:05 -04:00

12 KiB
Raw Blame History

RayNeo Air / GT XR integration

Built on the current feat/viture-xr PR #732 at bdf876d47c. The supplied historical hashes a127e66, 7f9dd75, e8e3e6b and f0b3297 were not resolvable in the fetched branch; no native projection or synchronization files are changed.

Discovery and transport

Glasses.kt owns USB permission, attachment/detachment and presentation-display selection. There is no manifest USB VID filter: discovery uses UsbManager.deviceList. VITURE discovery is retained. RayNeoModel accepts the scaffold's confirmed 1bbb:af50 and verncat's confirmed GT identity 3941:af50; other products under 1bbb or bridge vendor 22d9 must identify as RayNeo/TCL Air or GT in their USB product name. This covers named Air 2, 2s, 3, 4 Pro and GT devices without claiming arbitrary TCL phones or bridge chips. Additional unnamed VID/PID pairs require captures before being allowlisted. Other products under 3941 are rejected. Without a meaningful USB product name, 3941:af50 is labeled "RayNeo GT series"; a supplied GT MAX name is preserved. GT Max was observed on the Samsung SM-F976U with this USB identity on 2026-10-14; USB permission and the command handshake succeeded. EDID/product display names containing RayNeo, Ray Neo, or TCL Air/GT use the existing external-screen path. Android's supported modes, not a synthetic refresh value, determine whether 120 Hz can be selected. Stereo modes may have a lower maximum rate. GT Max's observed display identity is SmartGlasses, EDID manufacturer TCL, product 980 (1920x1080, 60/120 Hz in 2D). This exact metadata combination is recognized even though neither display name contains RayNeo. Other generic SmartGlasses/TCL products are not accepted by this rule.

Game output uses the same GlassesScreen presentation as VITURE, with the phone retaining the session controls; no screen-capture permission is needed. Discovery checks both Android's display name and its product name. On Android 12 and newer, a missing product-info object is treated like an unnamed panel: a recognized glasses USB device can identify a single presentation display. Unrelated named monitors and multiple unnamed displays are not automatically selected by that fallback. Game on glasses remains enabled by default. The presentation holder is selected before show(), and the phone SurfaceView is hidden only after the compositor attaches to the glasses holder. Late phone surface callbacks cannot reset the external output.

RayNeoLink claims a paired IN/OUT interface and translates the controller's internal commands to RayNeo packets. For 3941:af50, selection prefers interface number 5 (not array index 5), as tested in verncat's GT contribution. Only endpoints that can carry 64-byte packets qualify. Firmware with a different interface number can use a unique qualifying IN/OUT pair; ambiguous alternatives are rejected. It requests device info (0x66/0), enables IMU (0x66/1) and waits for acknowledgments, warms up for two seconds, and stops IMU (0x66/2) when no pose consumer remains or the link closes. SBS uses commands 6/7. Unsupported VITURE brightness, volume and electrochromic commands are never sent; the VITURE hardware-control UI is hidden for RayNeo. GT spatial-button notification 0x08 and volume/display ACKs remain non-device-info responses and cannot satisfy unrelated startup commands. The spatial button is left to the glasses' firmware; no undocumented spatial-mode command is sent.

The parser/filter are adapted from the user's scaffold at 581dbf712ed601ece4cf5e4a7c1f52e780299c88. Sensor packets are framed with 0x99/0x65, with little-endian acceleration at byte 4, gyro (degrees/sec) at 16 and a uint32 100us device tick at 40. Fragmented and coalesced reports are assembled before decoding. Board 0x3a (Air 4 Pro) receives the scaffold's -20-degree X IMU mounting correction. GT Max (3941:af50, board 0x41) uses the mapping measured on 2026-10-14: gyro and acceleration (-y, z, -x), then +35 degrees around X. At the user's level pose the raw acceleration was approximately (5.70, 0.00, 7.95) m/s². A directed left-turn-and-hold capture produced positive X/Z gyro (e.g. (20.5, 2.0, 28.2) deg/s), and upward looks produced negative Y gyro. The 35-degree mounting estimate comes from that level capture, not manufacturer calibration; frame fit and other GT variants remain unverified. Gravity initializes orientation before the first published pose. Subsequent body-to-world fusion uses measuredUp × predictedUp, correcting tilt toward gravity instead of amplifying the error. These fusion corrections also apply to Air; the GT Max sensor remapping does not apply to Air or VITURE.

The non-Max GT shares USB 3941:af50 but reports board 0x40, confirmed by switching between both physical pairs on the same phone. Its sensor axes use the ordinary XYZ basis with a measured -25-degree X mounting correction, rather than the Max permutation. Its confirmed upside-down resting acceleration was approximately (0.020, -8.819, -4.106) m/s²; the worn level capture was near (0.09, 9.26, 3.11). Left turns produced positive Y/Z gyro. The mounting estimate uses the resting surface; per-device calibration refines its tilt and gyro bias. Both the pose filter and calibration collector select the same board profile. Non-Max calibration keys have a :gt-standard-v1 suffix so they cannot replace existing Max profiles when USB identity fields coincide. Calibration loading waits for the device-info response; detached-device callbacks cannot change the replacement device's calibration key. Existing Max keys remain compatible. After installing this correction, the non-Max completed the upside-down calibration on the phone with saved=true, phase SAVED, progress 100. All 186 glasses/shared-pose/SteamVR-launch/UI regression checks passed and the installed APK's packaged runtime inputs verified. After calibration and the recenter check, the wearer confirmed on 2026-10-14 that the non-Max GT view looks and feels good.

Existing pose and SteamVR pipeline

The scaffold fuses gyro/accel into wxyz. The Android adapter converts its Y-up coordinate basis and component order into VITURE's Z-up xyzw convention before calling the same Glasses.PoseSink used by VITURE. HeadTracker and HeadPose retain their existing recenter/seated-reference behavior. The path continues through WaylandCompositor.nativeSetCardboardPose, the compositor's headpose_shm.h shared-memory record and tools/vr/src/driver_droiddeck.cpp's pose-file reader. The OpenVR projection, presenter, Vulkan wait logic and vblank counters are untouched. An explicit Play SteamVR request polls the guest runtime independently of display attachment and USB-control readiness. Both RayNeo and VITURE call the same droiddeck-steamvr start helper. Stopping cancels the pending launch request; automatic hardware 3D switching still respects the shared Auto 3D setting.

Optional stationary calibration

Glasses → Tracking → Tracking calibration guides the user to rest the connected RayNeo upside down on a level surface. It allows three seconds to settle, then requires five continuous seconds of stationary samples (at least 200 reports). Invalid gravity, the wrong orientation, motion/variance, or gaps longer than 250 ms restart the window. A 30-second deadline fails without replacing a saved profile; USB stream loss also terminates the operation. Cancellation and link replacement invalidate queued callbacks by operation revision and connection generation.

The profile contains a raw gyro bias and a small mounting tilt correction, applied to both sensor vectors before fusion. It does not estimate heading, full accelerometer scale/bias, or translation. Profiles persist by vendor/product/serial; when a serial is unavailable the product and model name share a fallback profile. Reset deletes only the current profile and restores the model mapping. VITURE's fused SDK poses do not expose the raw inputs this measurement needs, so this control is RayNeo-only.

While measuring, live pose publication pauses. On completion the user wears the glasses, looks ahead and taps Done to recenter the active session. Dismissing the dialog or leaving the tracking panel cancels an in-progress measurement. Agent diagnostics expose the calibration state through glasses; operations are calibrate, cancel-calibration, and reset-calibration. The calibration build passed 157 targeted sensor, lifecycle, pose, launch and Compose UI tests. Installing this feature and validating a real upside-down capture on the phone remain pending a debugging connection.

Regression and hardware validation

SteamVR library launch routing (2026-10-14)

DroidDeck's SteamVR library entry (appid 250820), including its game shortcut, now sets the same EXTRA_STEAMVR request as Play SteamVR instead of sending a normal Steam game URL. Existing sessions resume with that request as well. Other games retain their normal launch path and arguments.

Inside Steam's library, the existing SharedJSContext bridge wraps SteamClient.Apps.RunGame for exactly 250820 and dispatches it to droiddeck-steamvr launch. This calls the same install/start helper used by the button, including OpenVR registration, the ARM64 runtime and Vulkan layer setup. It does not change Steam's saved launch options. The library bridge is installed for both desktop and Big Picture. It relies on the live Steam UI API and needs verification against the actual phone's Steam version after installation.

The helper serializes installation/startup and avoids restarting an active DroidDeck SteamVR session. Library launch diagnostics are in ${XDG_RUNTIME_DIR:-/tmp}/droiddeck-steamvr/library-launch.log; normal runtime logs remain in vrstartup.log and Steam's logs directory. It does not intercept arbitrary external steam:// URLs or change VR game launch arguments.

Validation: seven bridge/dispatch tests passed under Node/Python, five Android SteamVR launch tests passed, shell syntax passed and the debug APK built with runtime input verification. The broader Linux compatibility suite cannot run unmodified on Windows because it requires fcntl; no Linux runtime was available for the helper's lock/process integration tests. Installation and live library Play verification are pending while the phone charges.

Run ./gradlew -PskipRust=true :app:testDebugUnitTest --tests 'com.droiddeck.launcher.glasses.*'. Protocol tests cover malformed/fragmented packets, unsigned timestamps, model gating, quaternion normalization, yaw basis and tick rollover. USB integration tests cover permissions, GT interface preference/fallback, interleaved GT notifications and ACKs during startup, 2D/3D writes, and stale pose callbacks. Hardware validation is still required per model: USB enumeration, acknowledgment/stream startup, axes and recenter, hot unplug/replug, SBS negotiation, Android's actual 120Hz mode, and SteamVR pose/frame pacing. GT Max was verified on SM-F976U with USB 3941:af50 and the TCL/980 display: the compositor attached to its separate 1920x1080 display, the Play SteamVR request started native vrserver/vrcompositor through the shared helper, and the presenter logged roughly 60 frames/s while the IMU packet count increased. The test retained the user's disabled Auto 3D setting. After installing the corrected GT sensor mapping, the user confirmed an upright starting view and correct movement in all directions. SteamVR and the glasses IMU remained running. Stereo negotiation, long-term drift, and alternate bridge firmware variants still need their own hardware validation. The targeted glasses, Cardboard pose, and SteamVR launch suite passed 134 tests after the tracking correction. Tracking regression coverage checks initial gravity alignment, tilt convergence, the recorded GT Max level pose, and yaw/pitch/roll through the shared VITURE basis conversion and recenter path.

Attribution and the scaffold's Apache-2.0 license are in docs/third-party/rayneo/.