[Steam Frame] Often fails to connect to the PC for streaming while charging from the official Steam charger
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- linux
- Área
- networking, operating-systems
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.6k
- Forks
- 83
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ValveSoftware/SteamOS
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ValveSoftware/SteamOS#2860 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ValveSoftware/SteamOS#2856 ·
-
steam-short-session-tracker: incorrect registry backup path resets settings during automatic repairAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
ValveSoftware/SteamOS#2829 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
ValveSoftware/SteamOS#1743 · 1 comentario · 2 reacciones ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 28/100
ValveSoftware/SteamOS#2863 ·
Todos los issues de ValveSoftware/SteamOS
Issues similares
-
flaky-test
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
vacp2p/nim-libp2p#3194 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
permissionlesstech/bitchat#1743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Sendspin/aiosendspin#447 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100