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>
This commit is contained in:
221 files changed
+24369 -491

No files matched your search

+117
View File
@@ -1,5 +1,12 @@
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="steamvr_recovery_title">Grafika SteamVR przestała działać</string>
<string name="steamvr_recovery_countdown">DroidDeck uruchomi się ponownie za %1$d s, aby zresetować grafikę i ponownie otworzyć SteamVR. Uruchomiona gra zostanie zamknięta; niezapisanego postępu nie da się przywrócić.</string>
<string name="steamvr_recovery_repeated">Błąd grafiki powrócił wkrótce po ponownym uruchomieniu. Automatyczne odzyskiwanie wstrzymano, aby uniknąć pętli. Ponowne uruchomienie zamknie grę; niezapisanego postępu nie da się przywrócić.</string>
<string name="steamvr_recovery_restart">Uruchom ponownie</string>
<string name="steamvr_recovery_cancel">Nie zamykaj</string>
<string name="steamvr_recovery_restarting">Resetowanie grafiki i ponowne otwieranie SteamVR…</string>
<string name="steamvr_recovery_failed">Nie udało się automatycznie uruchomić ponownie DroidDeck. Całkowicie zamknij aplikację, a potem otwórz ją ponownie.</string>
<string name="app_name">DroidDeck</string>
<string-array name="loading_hints">
<item>Przy pierwszym uruchomieniu pobierany jest Steam. Może to potrwać kilka minut.</item>
@@ -947,6 +954,8 @@
<string name="ctrl_keyboard_button">Przycisk klawiatury</string>
<string name="ctrl_select_steam">Naciśnij Select, aby otworzyć menu Steam</string>
<string name="ctrl_select_steam_hint">Zamiast View/Select.</string>
<string name="ctrl_joycon_vr">Joy-Cony jako kontrolery VR</string>
<string name="ctrl_joycon_vr_hint">Gdy działa SteamVR, każdy Joy-Con staje się dłonią. Skieruj go przed siebie i przytrzymaj Home lub Capture, aby go wyśrodkować.</string>
<string name="setup_animations">Animacje</string>
<string name="ctrl_adaptive_hint">Gałki pojawiają się tam, gdzie dotykasz, i chowają się po puszczeniu</string>
<string name="ctrl_layout">Układ</string>
@@ -1004,6 +1013,7 @@
<string name="content_linux_desktop_hint">KDE Plasma, Firefox i Twoje emulatory</string>
<string name="games_empty">Gry, które instalujesz w Steam, pojawią się tutaj po sesji.</string>
<string name="games_play_steam">Zagraj w Steam</string>
<string name="games_play_steamvr">Zagraj w SteamVR</string>
<string name="games_launch_settings">Ustawienia uruchamiania</string>
<string name="games_launch">Uruchom</string>
<string name="games_files">Pliki gry</string>
@@ -2355,6 +2365,113 @@
<string name="stores_sync_gog_unreachable">Nie udało się połączyć z GOG</string>
<string name="stores_sync_gog_unreadable">Nie udało się wczytać Twojej biblioteki GOG</string>
<string name="stores_registering">Rejestrowanie w Steam…</string>
<string name="drawer_page_glasses">Okulary</string>
<string name="glasses_open">Okulary VITURE</string>
<string name="glasses_control">Sterowanie okularami</string>
<string name="glasses_driver_missing">Ta kompilacja nie zawiera sterownika dla tych okularów.</string>
<string name="glasses_connection_failed">Nie udało się połączyć z okularami. Podłącz ponownie kabel lub dotknij „Zezwól”, aby spróbować ponownie.</string>
<string name="glasses_allow">Zezwól</string>
<string name="glasses_allow_hint">Pozwól DroidDeck ustawiać częstotliwość odświeżania, tryb 3D, jasność, głośność i przyciemnianie okularów oraz odczytywać dane śledzenia głowy.</string>
<string name="glasses_asking">Oczekiwanie na zgodę w oknie systemu Android…</string>
<string name="glasses_denied">Nie przyznano zgody na sterowanie. Zezwól, aby zmieniać ustawienia okularów.</string>
<string name="glasses_no_control">Te okulary wyświetlają grę, ale ich ustawień nie można tu zmienić.</string>
<string name="glasses_output">Wyjście</string>
<string name="glasses_status">%1$d×%2$d · %3$d Hz · %4$s</string>
<string name="glasses_mode_2d">2D</string>
<string name="glasses_mode_3d">3D</string>
<string name="glasses_game_on">Gra w okularach</string>
<string name="glasses_game_on_hint">Pokazuje grę tylko w okularach. Wyłączone: grę pokazuje telefon, a Android powiela jego ekran.</string>
<string name="glasses_display">Wyświetlacz</string>
<string name="glasses_refresh">Częstotliwość odświeżania</string>
<string name="glasses_3d">3D (obok siebie)</string>
<string name="glasses_3d_hint">Każde oko dostaje własną połowę obrazu 3840×1080. Jeśli obraz zniknie, przytrzymaj przycisk 2D/3D na okularach.</string>
<string name="glasses_3d_failed">Nie udało się potwierdzić sygnału 3D. Spróbuj ponownie, gdy wróci obraz 2D.</string>
<string name="glasses_no_signal">Brak obrazu: okulary są w trybie, którego ten telefon nie obsługuje. Przytrzymaj ich przycisk 2D/3D albo odłącz je i podłącz ponownie.</string>
<string name="glasses_3d_refresh">Częstotliwość odświeżania w 3D</string>
<string name="glasses_auto3d">3D w grach VR</string>
<string name="glasses_auto3d_hint">Przełącza na 3D, gdy działa SteamVR, a potem wraca.</string>
<string name="glasses_picture">Obraz 3D</string>
<string name="glasses_picture_hint">Automatycznie: SteamVR wypełnia widok; inne gry wiszą jako ekran w 3D i pozostają płaskie w 2D.</string>
<string name="glasses_picture_auto">Automatycznie</string>
<string name="glasses_picture_screen">Wirtualny ekran</string>
<string name="glasses_picture_sbs">Gra 3D obok siebie</string>
<string name="glasses_screen_size">Szerokość ekranu</string>
<string name="glasses_screen_distance">Odległość ekranu</string>
<string name="glasses_screen_next_session">Szerokość i odległość działają, gdy gra jest wyświetlana w okularach jako wirtualny ekran.</string>
<string name="glasses_screen_no_output">Te ustawienia działają, gdy opcja „Gra w okularach” jest włączona, a gra jest tam wyświetlana.</string>
<string name="glasses_screen_flat_hint">Tryb „Automatycznie” pokazuje tę grę 2D na pełnym ekranie. Użyj wirtualnego ekranu, aby dostosować jej szerokość, odległość i śledzenie głowy.</string>
<string name="glasses_screen_use">Użyj wirtualnego ekranu</string>
<string name="glasses_screen_direct_hint">SteamVR wypełnia widok. Dostosuj poniżej jego pole widzenia; szerokość i odległość dotyczą tylko wirtualnego ekranu.</string>
<string name="glasses_screen_sbs_hint">Gry 3D obok siebie wypełniają obraz każdego oka. Szerokość i odległość dotyczą tylko wirtualnego ekranu.</string>
<string name="glasses_tracking_flat_hint">Tryb „Automatycznie” utrzymuje tę grę 2D nieruchomo w polu widzenia. Aby używać śledzenia głowy, wybierz „Wirtualny ekran” w sekcji „Wyświetlacz”.</string>
<string name="glasses_tracking_sbs_hint">Śledzenie głowy działa z wirtualnym ekranem lub uruchomioną grą SteamVR.</string>
<string name="glasses_hardware">Okulary</string>
<string name="glasses_brightness">Jasność</string>
<string name="glasses_volume">Głośność</string>
<string name="glasses_sunblock">Przyciemnianie</string>
<string name="glasses_sunblock_hint">Przyciemnia przednie szkła.</string>
<string name="glasses_tracking">Śledzenie głowy</string>
<string name="glasses_head_tracking">Śledzenie głowy</string>
<string name="glasses_head_tracking_hint">Własne czujniki okularów obracają wirtualny ekran i SteamVR zgodnie z ruchem głowy.</string>
<string name="glasses_recenter">Wyśrodkuj widok</string>
<string name="glasses_recenter_button">Wyśrodkuj</string>
<string name="glasses_vr_fov">Pole widzenia SteamVR</string>
<string name="glasses_vr_fov_hint">Mniejsze przybliża SteamVR i wypełnia okulary; większe pokazuje więcej dookoła.</string>
<string name="glasses_playing">Grasz na: %1$s</string>
<string name="glasses_calibration">Kalibracja śledzenia</string>
<string name="glasses_calibration_hint">Ogranicza dryf i wyrównuje poziom odniesienia.</string>
<string name="glasses_calibration_saved_hint">Dla tych okularów używana jest zapisana kalibracja.</string>
<string name="glasses_calibration_open">Kalibruj</string>
<string name="glasses_calibration_instructions">Połóż podłączone okulary do góry nogami na poziomej powierzchni, tak aby oprawka leżała równo. Dotknij „Rozpocznij” i nie ruszaj ich przez około 8 sekund. Ruch rozpoczyna pomiar od nowa. Kalibracja koryguje dryf i pochylenie, ale nie kierunek.</string>
<string name="glasses_calibration_settling">Zostaw okulary do góry nogami i ich nie dotykaj. Oczekiwanie, aż się ustabilizują…</string>
<string name="glasses_calibration_collecting">Pomiar czujników. Nie ruszaj okularów.</string>
<string name="glasses_calibration_moving">Wykryto ruch. Nie dotykaj okularów; pomiar rozpocznie się ponownie automatycznie.</string>
<string name="glasses_calibration_turn_over">Połóż okulary do góry nogami na poziomej powierzchni. Pomiar rozpocznie się, gdy będą prawidłowo ułożone.</string>
<string name="glasses_calibration_complete">Kalibracja zapisana. Załóż okulary i patrz prosto przed siebie, a potem dotknij „Gotowe”, aby wyśrodkować widok.</string>
<string name="glasses_calibration_failed">Nie udało się ukończyć kalibracji. Sprawdź połączenie i nie ruszaj okularów, a potem spróbuj ponownie. Poprzednia kalibracja pozostała bez zmian.</string>
<string name="glasses_calibration_start">Rozpocznij</string>
<string name="glasses_calibration_done">Gotowe</string>
<string name="glasses_calibration_reset">Resetuj kalibrację śledzenia</string>
<string name="glasses_calibration_reset_hint">Usunąć zapisaną kalibrację i przywrócić domyślne ustawienia modelu? Po ponownym założeniu okularów wyśrodkuj widok.</string>
<string name="glasses_calibration_reset_button">Resetuj</string>
<string name="hand_camera_group">Śledzenie dłoni</string>
<string name="hand_camera_prompt_title">Śledzić dłonie za pomocą kamery?</string>
<string name="hand_camera_prompt_body">Kamera widzi Twoje dłonie. Gdy nie jest podłączony żaden kontroler, Twoje gołe dłonie stają się dłońmi VR: złącz kciuk i palec wskazujący, aby kliknąć, zaciśnij dłoń, aby chwycić, a żeby otworzyć menu, obróć dłoń wnętrzem do siebie i złącz palce. Z Joy-Conami kamera umieszcza je tam, gdzie naprawdę są Twoje dłonie. Obrazy są przetwarzane na tym urządzeniu i nigdy nie są zapisywane ani wysyłane.</string>
<string name="hand_camera_rear">Tylna kamera</string>
<string name="hand_camera_rear_hint">Zalecane. Zwykle ostrzejsza i szersza.</string>
<string name="hand_camera_front">Przednia kamera</string>
<string name="hand_camera_front_hint">Na wypadek, gdy tył urządzenia nie może być skierowany w Twoją stronę.</string>
<string name="hand_camera_allow">Użyj kamery</string>
<string name="hand_camera_not_now">Nie teraz</string>
<string name="hand_camera_setting">Śledzenie dłoni kamerą</string>
<string name="hand_camera_setting_hint">Gdy nie jest podłączony żaden kontroler, Twoje dłonie stają się dłońmi VR: złącz palce, aby kliknąć, a z dłonią zwróconą do siebie, aby otworzyć menu. Z Joy-Conami umieszcza je tam, gdzie widzi je kamera. Obrazy pozostają na tym urządzeniu.</string>
<string name="hand_camera_choice">Kamera</string>
<string name="hand_camera_access">Dostęp do kamery</string>
<string name="hand_camera_access_hint">Zezwól na dostęp do kamery, aby rozpocząć śledzenie dłoni.</string>
<string name="hand_camera_access_denied">Dostęp do kamery jest wyłączony. Włącz go w ustawieniach Androida.</string>
<string name="hand_camera_allow_button">Zezwól</string>
<string name="hand_camera_open_settings">Otwórz ustawienia</string>
<string name="hand_camera_placement">Położenie kamery</string>
<string name="hand_camera_placement_hint">Sprawdź, czy kamera Cię widzi, zanim zaczniesz grać.</string>
<string name="hand_camera_check">Sprawdź</string>
<string name="hand_camera_check_title">Położenie kamery</string>
<string name="hand_camera_how_rear">Ustaw urządzenie pionowo w odległości od 1,5 do 2 metrów, mniej więcej na wysokości klatki piersiowej, tylną kamerą skierowaną w Twoją stronę. Następnie wejdź w kadr z wyciągniętymi rękami.</string>
<string name="hand_camera_how_front">Ustaw urządzenie pionowo w odległości od 1,5 do 2 metrów, mniej więcej na wysokości klatki piersiowej, ekranem skierowanym w Twoją stronę. Następnie wejdź w kadr z wyciągniętymi rękami.</string>
<string name="hand_camera_starting">Uruchamianie kamery…</string>
<string name="hand_camera_stand_up">Urządzenie leży płasko. Ustaw je pionowo, aby kamera była skierowana w Twoją stronę.</string>
<string name="hand_camera_upright">Ustaw urządzenie bardziej pionowo, aby kamera była skierowana w Twoją stronę.</string>
<string name="hand_camera_not_seen">Jeszcze Cię nie widać. Wejdź w kadr tak, aby widoczne były głowa i ramiona.</string>
<string name="hand_camera_move_back">Cofnij się trochę.</string>
<string name="hand_camera_move_closer">Podejdź trochę bliżej.</string>
<string name="hand_camera_show_hands">Wyciągnij obie ręce tak, aby kamera je widziała.</string>
<string name="hand_camera_good">Wygląda dobrze.</string>
<string name="hand_camera_failed">Nie udało się uruchomić kamery. Zamknij inne aplikacje, które jej używają, i spróbuj ponownie.</string>
<string name="hand_camera_switch">Zmień kamerę</string>
<string name="hand_camera_skip">Pomiń</string>
<string name="hand_camera_done">Gotowe</string>
<string name="glasses_xreal_network_missing">Oczekiwanie na połączenie USB Ethernet okularów. Ten telefon może nie udostępniać go aplikacjom.</string>
<string name="glasses_xreal_connection_failed">Połączenie z XREAL zostało przerwane lub zwróciło nieobsługiwaną odpowiedź. Ponawianie…</string>
<string name="glasses_xreal_experimental">Eksperymentalna obsługa 1S. Użyj trybu Follow i wyłącz stabilizację w menu okularów. Kierunki śledzenia i tryby wyświetlania wymagają jeszcze testów na urządzeniu.</string>
<string name="cardboard_title">Cardboard VR</string>
<string name="cardboard_mode">Tryb Cardboard</string>
<string name="cardboard_mode_hint">Obraz dla lewego i prawego oka do gogli VR na telefon.</string>