cancel
Showing results for 
Search instead for 
Did you mean: 

sipos's Posts

@Starbuck Support told me that it is firmware, so should be fixable with a firmware update for the controllers, but it is not software, so changing your setup likely won't help. No ETA as far as I kn... See more...
@Starbuck Support told me that it is firmware, so should be fixable with a firmware update for the controllers, but it is not software, so changing your setup likely won't help. No ETA as far as I know on the firmware fix.
So, I spoke to support again. They had said that I would get a reply from someone higher up in the support team, and I got an email, referencing my case, asking me to submit feedback (it wasn't even ... See more...
So, I spoke to support again. They had said that I would get a reply from someone higher up in the support team, and I got an email, referencing my case, asking me to submit feedback (it wasn't even clear if it was feedback about the handling of the case, or feedback about the Stadia experience in the app, or what, the email didn't even make sense), so I wanted to make sure that wasn't them closing the case. The agent this time said that this is a know firmware issue, and that I would have to wait for a firmware update to fix it, but that there is no time frame for that yet. Edit: I was annoyed whne I wrote the next bit. I'm still experiencing unbelievably bad customer service from Google, but I don't really think any differently about the concept/theoretical potential of Stadia. I do however worry that it may never succeed because of the terrible customer service Google has meaning that they can never get enough people on board. I've been waiting weeks for a related issue to be solved by Google customer supoort. To be absolutely honest, I am losing faith in the whole idea of Stadia, or Google's ability to deliver it anyway, and am not planning to buy any more games right now. I might see if I can get a refund for the ones I have purchased if this doesn't get sorted soon, since I haven't been able to meaningfully play anything on Stadia - all of my play time has been trying combinations of things to see whether it works OK. I can't currently play in an even vaguely acceptable way on any platform except for my desktop computer, but I can play all of the games on Stadia on that anyway, and buy them for less off of Steam, so I have no interest in doing that and there is no point to Stadia right now for me. This audio issue isn't the only issue I have - I have terrible input lag on my Chromebook, even when connected to a ridiculously high bandwidth, low latency, highly reliable internet connection at work (but same at home too). If this can't work for someone like me with multiple bits of Google hardware the best internet connection you could really wish for for this (well, many people have more bandwidth, but there is plenty of bandwidth and the more important properties are the ridiculously low latency and basically non-existent packet loss, and the amazing WiFi connection, all carefully monitored to check for issues, and basically unused by anything else when I am trying Stadia), I don't have faith Google will ever get it to work satisfactorily. Maybe someone else will get game streaming working better, but Google just doesn't have the culture required to release reliable stuff and make it work properly, or the will to apply it to this anyway, I don't think. It is a shame, because I think they probably have the best network of anyone to deliver this kind of thing.
@Figs After trying it on my phone a bit more, I can tell I do get glitchy crackly sound sometimes, but it is occasional, and short lived, rather than constant.
@Figs I have not played much on anything other than the Chromecast (well, not played much at all, but I have at least spent quite a while on Stadia on the Chromecast trying to debug this). It is const... See more...
@Figs I have not played much on anything other than the Chromecast (well, not played much at all, but I have at least spent quite a while on Stadia on the Chromecast trying to debug this). It is constant and pretty bad on the Chromecast for me. It is at least not there the very limited amount I have tried it on my phone.
@FigsI get it constantly. I doubt it is a codec issue for me, as I get it even when playing at 1080p on an internet link and WiFi that can sustain >100Mbps bi-directional with <1ms latency and no pac... See more...
@FigsI get it constantly. I doubt it is a codec issue for me, as I get it even when playing at 1080p on an internet link and WiFi that can sustain >100Mbps bi-directional with <1ms latency and no packet loss (almost literally, there will be entire days between when a test packet is lost with our monitoring, ~0.00000001% packet loss).
Yep. Same problem with brand new hardware. It isn't a headphones issue or connection issue either, based on the fact that it both works and doesn't work in different circumstances with them the same,... See more...
Yep. Same problem with brand new hardware. It isn't a headphones issue or connection issue either, based on the fact that it both works and doesn't work in different circumstances with them the same, and continues to not work in the same circumstances except either of them changed. TBH, I suspect that it is a hardware issue, but it just affects lots of controllers, and both the old and new one are affected.
Well, @Tokra2003, my experience is that a replacement set of hardware hasn't made any difference, so no point in shipping it back (unless they actually fix the problem).
So, I received a complete replacement Founder's Edition box. I am still having the same problem. I tried a completely different type of headphones (over ear headphones with mic vs earbuds without mic)... See more...
So, I received a complete replacement Founder's Edition box. I am still having the same problem. I tried a completely different type of headphones (over ear headphones with mic vs earbuds without mic), I tried it on both 2.4GHz and 5GHz WiFi. I tried using USB type C for the headphones (they aren't detected, as before). No change at all. I tried playing on a brand new Chromebook I've just got, in the Chrome browser, and, while there was no audio issue, as with when the controller was connected to my phone, there was significant input lag. As before, sound is perfectly fine from HDMI too. Not sure what the issue is, since it seems not to be hardware (unless both sets I got are faulty). I can only really play with headphones, and it is pretty unsatisfying playing on my phone, so I don't have an acceptable way to play right now, which is really annoying because I'd like to be playing Tomb Raider.
@Tokra2003 I guess there is some concern it could be to do with the Chromecast Ultra. It only happens when using the controller with the Chromecast Ultra for me, with the sound coming from the headph... See more...
@Tokra2003 I guess there is some concern it could be to do with the Chromecast Ultra. It only happens when using the controller with the Chromecast Ultra for me, with the sound coming from the headphones from the controller. When using the controller plugged in to my phone, and the headphones plugged in to the controller, it doesn't happen. It is almost certainly to do with the controller and WiFi, but I guess this way makes sure. They are sending the new stuff before I have to send the old stuff back (with an auth hold on my card for the price of it in case I don't send it back), so there isn't any time without the stuff. I may try the new controller with the old Chromecast Ultra to be sure it is the controller before sending off the old stuff.   To me, the more ridiculous but is that they needed the serial number for the whole package from the box. I assume they would have managed somehow if I had already thrown away the box, but, mostly by chance, I hadn't yet. It would be unreasonable to expect someone to still have it I think, since they may not notice this immediately.
@jahilton2002 I don't know. That is what support advised after doing some tests with mine. I should get the new one tomorrow, so will update whether that has fixed the issue for me. It is perfectly p... See more...
@jahilton2002 I don't know. That is what support advised after doing some tests with mine. I should get the new one tomorrow, so will update whether that has fixed the issue for me. It is perfectly possible that there is more than one cause, or that a firmware fix is possible, but either the support people dealing with my case didn't know that, or they will conclude that there is after examining mine. You'd have to talk to support to get them to authorise an RMA anyway I think. I am having  a n auth hold on my card for the price of the controller and Chromecast Ultra, having the new ones shipped out and returning mine (has to arrive within 21 days, will send it when the replacement arrives), so won't be without one, but I don't think that was the only option. The crackling makes me not want to play with it, so it is a big issue for me, so I wanted a replacement ASAP.
I have ordered my replacement controller (and Chromecast), with delivery date 6-9th. I have an RMA for the existing one.  I assume this will fix the issue for me when it arrives, but I will post her... See more...
I have ordered my replacement controller (and Chromecast), with delivery date 6-9th. I have an RMA for the existing one.  I assume this will fix the issue for me when it arrives, but I will post here to confirm when it has.
So, for me, it doesn't seem to be fixed at all by disconnecting and reconnecting the jack. I will try it again to try and work out if it could be being helped by that, but it just gets bad again so f... See more...
So, for me, it doesn't seem to be fixed at all by disconnecting and reconnecting the jack. I will try it again to try and work out if it could be being helped by that, but it just gets bad again so fast that it isn't obvious that it helps, or whether it definitely doesn't help at all, assuming I have time before returning it. I guess this info could be useful to other people. I guess Google can test things with my controller themselves when they get it back, including opening it up, so it probably isn't useful to them. Ultimately they need to fix these issues I guess, so not sure how helpful it is really for other people - I guess people don't really care why the problem happens, they just want it fixed.
Unfortunately disconnecting and reconnecting doesn't fix it at all for me. It is still terribly bad immediately after reconnecting.
I hadn't realised that customer support could actually be contacted, other than through this forum until today. I have contacted customer support (requested a call), who have tried debugging with me ... See more...
I hadn't realised that customer support could actually be contacted, other than through this forum until today. I have contacted customer support (requested a call), who have tried debugging with me (factory resetting the Chromecast Ultra and Stadia Controller, trying a 2.4 GHz network) and not managed to eliminate the problem. I need the serial number for my whole Stadia package (the box both devices came in) which is at home, but they have said that, once they have that, they are going to do a replacement of my hardware (as I understand it, both the Founder's Edition controller and the Chromecast Ultra, but I would guess that it is the controller than is the issue, and I think they originally were going to replace just that). I'll update this thread once the hardware is replaced and let you all know if that has fixed it for me. Given that I have tried more than one set of headphones, on a super low latency, relatively high bandwidth, internet connection, which we (me and my colleagues, I am the IT manager for the company in question) were monitoring for packet loss (no packets dropped) and bandwidth usage (almost zero other than this), and on another connection, and factory reset the hardware, it is hard to see how it could not be a hardware issue for me at least. Edit: Also, on a WiFi network with no other devices other than my phone, from an AP with no other devices connected.
So, the three of us in this thread definitely aren't the only ones experiencing this. Below is a list of Reddit /r/stadia threads about it: https://www.reddit.com/r/Stadia/comments/e1v1uj/crackling... See more...
So, the three of us in this thread definitely aren't the only ones experiencing this. Below is a list of Reddit /r/stadia threads about it: https://www.reddit.com/r/Stadia/comments/e1v1uj/crackling_on_stadia_controller_via_headset/ https://www.reddit.com/r/Stadia/comments/e03w1a/crackling_headphones/ https://www.reddit.com/r/Stadia/comments/e0ghby/stadia_controller_has_crackling_static_noises/ https://www.reddit.com/r/Stadia/comments/e0xow2/headset_audio_quality_through_stadia_controller/ https://www.reddit.com/r/Stadia/comments/e0296f/soundproblems_with_my_headset_stadia_controller/ https://www.reddit.com/r/Stadia/comments/e29fk6/stuttering_audio/ https://www.reddit.com/r/Stadia/comments/e25630/multiple_sound_problems_no_sound_at_all_or_bad/ https://www.reddit.com/r/Stadia/comments/dzt442/static_when_using_audio_jack/ https://www.reddit.com/r/Stadia/comments/e20oyu/hardware_troubleshooting_pin/ Possibly related: https://www.reddit.com/r/Stadia/comments/e224z6/stadia_controller_headphone_jack_not_working/ https://www.reddit.com/r/Stadia/comments/e0fxdt/no_sound_via_headsetheadphone/ @GraceFromGoogleany word on what the problem might be or what we might be able to do?
I'm experiencing very crackly audio (hard to hear what is happening) when using headphones and only when the controller is on WiFi (sound from the Chromecast is fine and sound from the 3.5mm jack on ... See more...
I'm experiencing very crackly audio (hard to hear what is happening) when using headphones and only when the controller is on WiFi (sound from the Chromecast is fine and sound from the 3.5mm jack on the headphones is fine when the controller is connected to my phone by USB C). I have tried on two different internet connections, one of them with ridiculously good WiFi that nobody else was using and insanely low latency (with plenty of bandwidth) and another less good, and with two sets of headphones. I have reported it via feedback, but not got any sort of reply or acknowledgement.