Update 05/01/20 - tried different scenarios in a frieds environment - same here, althought hi didn't even realized it. Unfortunately controller resetting worked reproducable for one day only. Yester...
See more...
Update 05/01/20 - tried different scenarios in a frieds environment - same here, althought hi didn't even realized it. Unfortunately controller resetting worked reproducable for one day only. Yesterday - sound was brilliant w/o any changes on my side. Today - just tried for this post, crackling is back. So meanwhile I think, that it is rather a server-session then a client- or hardware-configuration issue. As I urged support to get their job done, they told me, quote: "officially known issue as of 26th April 2020 to be solved by future update". At least something after all... By the way - controller has usb-c connector an build in bluetooth "to be activated later on" according to google store. May be that will allow wireless headsets faster then they get this 3,5mm-jack issue solved. Time will tell... @Endgegner too many parameters in my opinion - FttH 200 MBit Fritzbox 7490, dual band mesh-wlan with band steering activ, Chromecast 1 GHz LAN-wired playing on TV,