I'm using stadia since 3 days. Today i tried to use the stadia controller with headphones/headsets (3 different) for the first time. The TV shows that a headphone is connected in the upper left corner. But the sound is completly dead. Nothing to hear. The volume in the stadia settings for chromecast and headset is all the way up to the right at max. Is my controller broken or did google maybe deactivate the function today to update/fix the low sound by headphones some people complaining? Can someone test it today? Cheers from Berlin
EDIT: So the controller hardware seems to be ok. I tried to play with headset in stadia controller on my notebook on chromebrowser. Sound works perfect. So now i have to figure out why its not working when using the chromecast and stadia controller. Any ideas?
@razzzar Is your Chromecast connected by a wired ethernet connection? I just saw another thread describing that the headset audio didn't seem to work when the Chromecast connected via ethernet but did when connected to WiFi:
I wonder if the audio routing might get treated differently in that scenario for some reason.
In any case, since it does seem that your hardware is okay I'd suggest using the Send feedback option in the Stadia app to let the developers know about this.
Yes its when i'm using ethernet for the chromecast. But its not the reason. It has something to do with "same lan". When i use ethernet modem/cc the sound doesn't work. When i use ethernet router/cc it works. Wlan/cc + wlan/controller works too.
Somehow sound doesnt work when cc using ethernet directly in modem which is the fastest way speedwise at my home. After modem there is my router which i use for wifi in my appartment. When i plug ethernet there it works.
It's strange anyways because the controller steering works when i use the modem ethernet and stadia recordnize the headset top left corner but its dead. Sorry for my bad english.
I had the exact same issue. I thought the solution of using Ethernet vs wifi was bull, but gave it a try anyway and it worked! How can this be a reproducible issue for this long and Stadia not fix it?!
Ugh, complaints aside. Thanks for the thread, this helped!