-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poor WiFi Signal on Steam Deck OLED (likely driver issue) #1736
Comments
I have also followed the troubleshooting provided by Valve support, including a reimage. |
What's the make and model of them? What WiFi standard did you have them setup as? What encryption settings?
It's possible that SteamOS is polling the status of it more often and the others are rounding it up or polling less often.
What's better is to determine what this "wifi signal issue" manifests as. For example if you have a computer with files stored on an SSD serving its files over SFTP/FTP and it's wired via ethernet to your access point / router, and then you transfer those files via filezilla to/from your steam deck, try it in windows, try it in SteamOS, and transfer to the SSD of your Steam Deck, what transfer speeds are you seeing? This type of consistent testing will give a better idea of "what's the signal like?" rather than an arbitrary polling of "is the signal strength weak/strong" because some value in the task bar says so. |
The first two routers I no longer have, but the first was my ISP router. Evolution digital was the brand. The second was a Wyze mesh router. My current one is a Google Nest WiFi Pro. It is a WiFi 6e router. I’ve used it on the steam deck with wpa2 and wpa3. I tried game streaming via gamepass on windows and steam os on the steam deck. It was noticeably better on Windows (clearer picture, less input lag). I’ll try those tests you mentioned if I get the time. |
Every few boots, I get similar WiFi connectivity issues on the new OLED LE. When it happens it will boot but struggle to connect, when it does the speeds (1-10Mbps instead of the usual 300+) and signal strength are low. A reboot immediately after seems to resolve it in my case. |
I'm noticing that these are all 'mesh' routers. On my WiFi 6 access point / router I have mesh configurations disabled. |
It's more helpful to also provide information such as your WiFI access point, configuration (wifi standards, frequencies, etc), security settings, etc. If we're reporting problems then it helps to provide full detailed information to narrow down commonalities. Not all Wireless LANs are the same. |
Not mesh routers, two diff. routers (one Virgin WiFi 6 80MHz width, one TalkTalk WiFi 5, can't remember exact models currently), 5GHz connection, WPA2, network not congested. Can't get the exact standards conns to show on the Deck, but they connect on ax/ac on my PCs iirc. The TT router is running in bridge mode atm. Both work fine with my LCD Deck and other devices, something specific to the OLED. Persisted after a factory reset, so I suspect drivers or something power related like OP. |
I have also seen poor WiFi performance on my steam deck specifically. I don't think I have ever seen it have a full signal. It's always one bar short. Doesn't matter how close to the router I am. Using eero WiFi mesh network |
Full list of troubleshooting steps I tried is below. The issue remains.
|
Your system information
Please describe your issue in as much detail as possible:
My steam deck oled has poor WiFi signal. I’ve tried 3 routers. It’s consistent across all of them.
My current router is the Google Nest WiFi Pro.
I’ve tried disabling WiFi power saving. I’ve tried 2.4ghz,5ghz and 6ghz.
I isolated the issue to Steam OS, likely a driver issue.
On Steam OS, my signal strength is sporadic. It bounces around from 50-70%. On my other devices I have 100%.
I installed Windows on an external SSD. The WiFi strength was at a steady 100%.
This is being in the same place, on the same network. I even tried it while being on the same WiFi channel.
I tried the beta and preview channels about a month ago and the issue was the same. I am currently on the stable update channel.
Full list of troubleshooting steps I tried:
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: