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">Os gráficos do SteamVR pararam</string>
<string name="steamvr_recovery_countdown">O DroidDeck vai reiniciar em %1$d segundos para redefinir os gráficos e reabrir o SteamVR. O jogo em execução será fechado; o progresso não salvo não poderá ser recuperado.</string>
<string name="steamvr_recovery_repeated">A falha gráfica voltou logo após uma reinicialização recente. A recuperação automática foi pausada para evitar um loop. Reiniciar vai fechar o jogo; o progresso não salvo não poderá ser recuperado.</string>
<string name="steamvr_recovery_restart">Reiniciar agora</string>
<string name="steamvr_recovery_cancel">Manter aberto</string>
<string name="steamvr_recovery_restarting">Redefinindo os gráficos e reabrindo o SteamVR…</string>
<string name="steamvr_recovery_failed">O DroidDeck não conseguiu reiniciar automaticamente. Feche o app completamente e abra-o de novo.</string>
<string name="app_name">DroidDeck</string>
<string-array name="loading_hints">
<item>Na primeira execução, a Steam é baixada. Isso pode levar alguns minutos.</item>
@@ -930,6 +937,8 @@
<string name="ctrl_keyboard_button">Botão do teclado</string>
<string name="ctrl_select_steam">Pressione Select para abrir o menu Steam</string>
<string name="ctrl_select_steam_hint">Em vez de View/Select.</string>
<string name="ctrl_joycon_vr">Joy-Cons como controles de RV</string>
<string name="ctrl_joycon_vr_hint">Enquanto o SteamVR está rodando, cada Joy-Con vira uma mão. Aponte-o para a frente e segure Home ou Capture para recentralizá-lo.</string>
<string name="setup_animations">Animações</string>
<string name="ctrl_adaptive_hint">Os analógicos aparecem onde você toca e somem ao soltar</string>
<string name="ctrl_layout">Layout</string>
@@ -987,6 +996,7 @@
<string name="content_linux_desktop_hint">KDE Plasma, Firefox e seus emuladores</string>
<string name="games_empty">Os jogos que você instala na Steam aparecem aqui após a sessão.</string>
<string name="games_play_steam">Jogar na Steam</string>
<string name="games_play_steamvr">Jogar no SteamVR</string>
<string name="games_launch_settings">Configurações de inicialização</string>
<string name="games_launch">Iniciar</string>
<string name="games_files">Arquivos do jogo</string>
@@ -2316,6 +2326,113 @@
<string name="stores_sync_gog_unreachable">Não foi possível conectar à GOG</string>
<string name="stores_sync_gog_unreadable">Não foi possível ler sua biblioteca da GOG</string>
<string name="stores_registering">Registrando na Steam…</string>
<string name="drawer_page_glasses">Óculos</string>
<string name="glasses_open">Óculos VITURE</string>
<string name="glasses_control">Controle dos óculos</string>
<string name="glasses_driver_missing">Esta versão não inclui o driver para estes óculos.</string>
<string name="glasses_connection_failed">Não foi possível conectar aos óculos. Reconecte o cabo ou toque em Permitir para tentar de novo.</string>
<string name="glasses_allow">Permitir</string>
<string name="glasses_allow_hint">Permite que o DroidDeck ajuste a taxa de atualização, o modo 3D, o brilho, o volume e o escurecimento dos óculos, e leia o rastreamento da cabeça deles.</string>
<string name="glasses_asking">Aguardando você permitir na solicitação do Android…</string>
<string name="glasses_denied">O controle foi recusado. Permita para alterar as configurações dos óculos.</string>
<string name="glasses_no_control">Estes óculos mostram o jogo, mas as configurações deles não podem ser alteradas por aqui.</string>
<string name="glasses_output">Saída</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">Jogo nos óculos</string>
<string name="glasses_game_on_hint">Mostra o jogo só nos óculos. Desativado: o celular mostra o jogo e o Android espelha a tela do celular.</string>
<string name="glasses_display">Tela</string>
<string name="glasses_refresh">Taxa de atualização</string>
<string name="glasses_3d">3D (lado a lado)</string>
<string name="glasses_3d_hint">Cada olho recebe a própria metade de uma imagem de 3840×1080. Se a imagem sumir, mantenha pressionado o botão 2D/3D dos óculos.</string>
<string name="glasses_3d_failed">O sinal 3D não foi confirmado. Tente novamente quando a imagem 2D voltar.</string>
<string name="glasses_no_signal">Sem imagem: os óculos estão em um modo que este celular não consegue enviar. Mantenha pressionado o botão 2D/3D deles ou desconecte e reconecte os óculos.</string>
<string name="glasses_3d_refresh">Taxa de atualização em 3D</string>
<string name="glasses_auto3d">3D para jogos de RV</string>
<string name="glasses_auto3d_hint">Muda para 3D enquanto o SteamVR está em execução e volta depois.</string>
<string name="glasses_picture">Imagem 3D</string>
<string name="glasses_picture_hint">Automático: o SteamVR preenche a visão; outros jogos flutuam como uma tela em 3D e ficam planos em 2D.</string>
<string name="glasses_picture_auto">Automático</string>
<string name="glasses_picture_screen">Tela virtual</string>
<string name="glasses_picture_sbs">Jogo lado a lado</string>
<string name="glasses_screen_size">Largura da tela</string>
<string name="glasses_screen_distance">Distância da tela</string>
<string name="glasses_screen_next_session">A largura e a distância valem quando um jogo roda nos óculos como tela virtual.</string>
<string name="glasses_screen_no_output">Estas configurações valem enquanto Jogo nos óculos estiver ativado e o jogo for exibido neles.</string>
<string name="glasses_screen_flat_hint">O modo Automático mantém este jogo 2D em tela cheia. Use uma tela virtual para ajustar a largura, a distância e o rastreamento da cabeça.</string>
<string name="glasses_screen_use">Usar tela virtual</string>
<string name="glasses_screen_direct_hint">O SteamVR preenche a visão. Ajuste o campo de visão abaixo; a largura e a distância valem só para uma tela virtual.</string>
<string name="glasses_screen_sbs_hint">Jogos lado a lado preenchem a visão de cada olho. A largura e a distância valem só para uma tela virtual.</string>
<string name="glasses_tracking_flat_hint">O modo Automático mantém este jogo 2D fixo na visão. Escolha Tela virtual na seção Tela para usar o rastreamento da cabeça.</string>
<string name="glasses_tracking_sbs_hint">O rastreamento da cabeça vale para uma tela virtual ou um jogo do SteamVR em execução.</string>
<string name="glasses_hardware">Óculos</string>
<string name="glasses_brightness">Brilho</string>
<string name="glasses_volume">Volume</string>
<string name="glasses_sunblock">Escurecimento</string>
<string name="glasses_sunblock_hint">Escurece as lentes frontais.</string>
<string name="glasses_tracking">Rastreamento da cabeça</string>
<string name="glasses_head_tracking">Rastreamento da cabeça</string>
<string name="glasses_head_tracking_hint">Os sensores dos próprios óculos giram a tela virtual e o SteamVR com a sua cabeça.</string>
<string name="glasses_recenter">Recentralizar visão</string>
<string name="glasses_recenter_button">Recentralizar</string>
<string name="glasses_vr_fov">Campo de visão do SteamVR</string>
<string name="glasses_vr_fov_hint">Menor aproxima o SteamVR e preenche os óculos; maior mostra mais ao seu redor.</string>
<string name="glasses_playing">Jogando em %1$s</string>
<string name="glasses_calibration">Calibração do rastreamento</string>
<string name="glasses_calibration_hint">Reduz a deriva e alinha a referência de nível.</string>
<string name="glasses_calibration_saved_hint">A calibração salva é aplicada a estes óculos.</string>
<string name="glasses_calibration_open">Calibrar</string>
<string name="glasses_calibration_instructions">Coloque os óculos conectados de cabeça para baixo em uma superfície nivelada, com a armação apoiada por igual. Toque em Iniciar e não mexa neles por cerca de 8 segundos. Qualquer movimento reinicia a medição. Isso ajusta a deriva e a inclinação, não a direção.</string>
<string name="glasses_calibration_settling">Deixe os óculos de cabeça para baixo, sem tocar neles. Aguardando que fiquem estáveis…</string>
<string name="glasses_calibration_collecting">Medindo os sensores. Mantenha os óculos parados.</string>
<string name="glasses_calibration_moving">Movimento detectado. Não toque nos óculos; a medição vai reiniciar automaticamente.</string>
<string name="glasses_calibration_turn_over">Apoie os óculos de cabeça para baixo em uma superfície nivelada. A medição começa quando eles estiverem na posição correta.</string>
<string name="glasses_calibration_complete">Calibração salva. Coloque os óculos e olhe para a frente; depois toque em Concluído para recentralizar.</string>
<string name="glasses_calibration_failed">Não foi possível concluir a calibração. Verifique a conexão, mantenha os óculos parados e tente novamente. Sua calibração anterior não foi alterada.</string>
<string name="glasses_calibration_start">Iniciar</string>
<string name="glasses_calibration_done">Concluído</string>
<string name="glasses_calibration_reset">Redefinir calibração do rastreamento</string>
<string name="glasses_calibration_reset_hint">Remover a calibração salva e restaurar o padrão do modelo? Recentralize depois de colocar os óculos de novo.</string>
<string name="glasses_calibration_reset_button">Redefinir</string>
<string name="hand_camera_group">Rastreamento das mãos</string>
<string name="hand_camera_prompt_title">Rastrear suas mãos com a câmera?</string>
<string name="hand_camera_prompt_body">A câmera consegue ver suas mãos. Sem nenhum controle conectado, suas mãos livres viram as mãos de RV: junte o polegar e o indicador para clicar, feche a mão para pegar e, para abrir o menu, vire a palma para você e junte os dedos. Com Joy-Cons, ela os coloca onde suas mãos realmente estão. As imagens são processadas neste dispositivo e nunca são salvas ou enviadas.</string>
<string name="hand_camera_rear">Câmera traseira</string>
<string name="hand_camera_rear_hint">Recomendada. Costuma ser mais nítida e ampla.</string>
<string name="hand_camera_front">Câmera frontal</string>
<string name="hand_camera_front_hint">Para quando a parte de trás do dispositivo não puder ficar voltada para você.</string>
<string name="hand_camera_allow">Usar câmera</string>
<string name="hand_camera_not_now">Agora não</string>
<string name="hand_camera_setting">Rastreamento das mãos pela câmera</string>
<string name="hand_camera_setting_hint">Sem nenhum controle conectado, suas mãos viram as mãos de RV: junte os dedos para clicar e, com a palma virada para você, junte-os para abrir o menu. Com Joy-Cons, ela os coloca onde a câmera os vê. As imagens ficam neste dispositivo.</string>
<string name="hand_camera_choice">Câmera</string>
<string name="hand_camera_access">Acesso à câmera</string>
<string name="hand_camera_access_hint">Permita o acesso à câmera para que o rastreamento das mãos possa começar.</string>
<string name="hand_camera_access_denied">O acesso à câmera está desativado. Ative-o nas configurações do Android.</string>
<string name="hand_camera_allow_button">Permitir</string>
<string name="hand_camera_open_settings">Abrir configurações</string>
<string name="hand_camera_placement">Posição da câmera</string>
<string name="hand_camera_placement_hint">Verifique se a câmera consegue ver você antes de jogar.</string>
<string name="hand_camera_check">Verificar</string>
<string name="hand_camera_check_title">Posição da câmera</string>
<string name="hand_camera_how_rear">Deixe o dispositivo em pé a 1,5-2 metros de distância, na altura do peito, com a câmera traseira voltada para você. Depois entre no campo de visão com as mãos estendidas.</string>
<string name="hand_camera_how_front">Deixe o dispositivo em pé a 1,5-2 metros de distância, na altura do peito, com a tela voltada para você. Depois entre no campo de visão com as mãos estendidas.</string>
<string name="hand_camera_starting">Iniciando a câmera…</string>
<string name="hand_camera_stand_up">O dispositivo está deitado. Deixe-o em pé para a câmera ficar voltada para você.</string>
<string name="hand_camera_upright">Deixe o dispositivo mais em pé para a câmera ficar voltada para você.</string>
<string name="hand_camera_not_seen">Ainda não consegue ver você. Entre no campo de visão para mostrar a cabeça e os ombros.</string>
<string name="hand_camera_move_back">Afaste-se um pouco.</string>
<string name="hand_camera_move_closer">Chegue um pouco mais perto.</string>
<string name="hand_camera_show_hands">Mostre as duas mãos onde a câmera possa vê-las.</string>
<string name="hand_camera_good">Tudo certo.</string>
<string name="hand_camera_failed">Não foi possível iniciar a câmera. Feche outros apps que estejam usando a câmera e tente de novo.</string>
<string name="hand_camera_switch">Trocar de câmera</string>
<string name="hand_camera_skip">Pular</string>
<string name="hand_camera_done">Concluído</string>
<string name="glasses_xreal_network_missing">Aguardando a conexão Ethernet por USB dos óculos. Este celular pode não disponibilizá-la para os apps.</string>
<string name="glasses_xreal_connection_failed">A conexão com os óculos XREAL foi interrompida ou retornou uma resposta incompatível. Tentando novamente…</string>
<string name="glasses_xreal_experimental">Suporte experimental ao 1S. Use o modo Follow e desative a estabilização no menu dos óculos. As direções do rastreamento e os modos de exibição ainda precisam de testes no dispositivo.</string>
<string name="cardboard_title">Cardboard VR</string>
<string name="cardboard_mode">Modo Cardboard</string>
<string name="cardboard_mode_hint">Imagens para o olho esquerdo e o direito, para um óculos de RV de celular.</string>