[Steam Frame] Often fails to connect to the PC for streaming while charging from the official Steam charger
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 42/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- linux
調査の方向性
Start by reproducing the failure with the official Steam charger and capture the headset logs using the in-headset bug reporter. Compare them with remote_connections.txt, vrserver.txt, and driver_vrlink.txt from failed and successful attempts, focusing on why the Wireless Adapter link is not announced. Done means PC VR streaming connects reliably while the headset is charging from the official charger.
索引モデルが issue の本文から書いたものです。
説明
System Info
- Steam client version: 1790545198 (host PC)
- SteamOS version: Steam Frame 0.4.1 (20260925.6191901)
- Opted into Steam client beta?: Yes
- Opted into SteamOS beta?: Default channel (not changed)
- Have you checked for updates in Settings > System?: Headset is on the build listed above (updated 2026-09-25)
Issue
While the Steam Frame is charging from the official Steam charger, it intermittently fails to connect to the PC over the Steam Frame Wireless Adapter, so PC VR streaming can't start. The headset shows no message when this happens. On battery, or on a third-party charger in the same wall outlet, it connected every time.
Test results (full SteamVR restart before every attempt)
| Power | Attempts | Failed to connect |
|---|---|---|
| Official Steam charger and cable, wall outlet | 4 | 2 (1st and 3rd) |
| Third-party charging base (Insignia) with a Samsung USB-C cable, same wall outlet | multiple (not counted) | 0 |
| Unplugged, on battery | multiple (not counted) | 0 |
Expected: the headset connects over the Wireless Adapter and the game streams, the same as on battery.
Actual (intermittently, only on the Steam charger): the headset doesn't connect. The game launches on the PC, SteamVR reports no headset, and Steam gives up waiting for the VR connection.
What the host-side logs show (Steam's remote_connections.txt, SteamVR's vrserver.txt and driver_vrlink.txt)
- Failed attempts: the headset only announced itself on the home Wi-Fi network, never on the Wireless Adapter's network, and Steam never logged a client connection. vrlink never attached a headset (no
Found primary link), and the game was refused withVRInitError_Driver_WirelessHmdNotConnected. - Successful attempts: the headset announced itself on both networks, Steam logged
connected via direct connectionplus an adapterConnect event, and vrlink attached over the adapter link. - The PC side was identical in both cases (adapter plugged in, SteamVR freshly restarted), so the failure is on the headset side.
The host never receives the headset's charging state, so these logs show the effect, not the cause. The headset's own logs from a failed attempt should show why it didn't bring up the adapter link. I can capture them with the in-headset bug reporter on the next failure if that's useful.
Host: Linux desktop (Arch Linux, KDE Plasma Wayland), AMD RX 9070 XT, SteamVR 2.17.10, Wireless Adapter on a USB 3 port.
Steps To Reproduce
- Plug the Frame into the official Steam charger and cable at a wall outlet.
- On the PC, restart SteamVR. The Wireless Adapter is connected.
- From the headset, connect to the PC and launch a PC VR game.
- Repeat. In my testing, 2 of 4 attempts failed to connect, with no message on the headset.
- Repeat on battery, or on a different charger and cable: every attempt connects.
- 主要言語
- 言語のデータがありません
- スター
- 2.6k
- フォーク
- 86
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ValveSoftware/SteamOS のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ValveSoftware/SteamOS#2927 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ValveSoftware/SteamOS#2875 · コメント 1 件 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
ValveSoftware/SteamOS#2856 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repairオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
ValveSoftware/SteamOS#2829 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 68/100
ValveSoftware/SteamOS#1743 · コメント 1 件 · リアクション 2 件 ·
ValveSoftware/SteamOS の issue をすべて見る
似ている issue
-
Proxy ignores l5d-retry-http and l5d-retry-grpc conditions that follow a comma and space対応中かも @RaphaelFakhri が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 3 日以内に返信
-
kind/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
kubernetes-sigs/cluster-api-provider-ibmcloud#3023 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
tunneld on Windows: Wi-Fi devices are not discovered because uvicorn runs on a ProactorEventLoopオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
doronz88/pymobiledevice3#2051 ·
メンテナーはふだん 1 日以内に返信
-
Realtime reconnect retries exceed the documented 60-second backoff cap対応中かも @hsusul が今日担当しました。 オープンbug python realtime
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
supabase/supabase-py#1765 ·
メンテナーはふだん 4 日以内に返信
-
mega65_ftp gtest hanging because of etherload_common.c missing index対応中かも @nobruinfo が今日担当しました。 オープンnew
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
MEGA65/mega65-tools#244 ·