YayoProtocal

I am with you on this 100000%...I am in the same boat with a ticket opened and them asking me to return my headset first before they'll replace. This is after someone on their support team ACKNOWLEDGED VIA EMAIL that they sold me a defected item. They will not make an exception to refund me my money because unfortunately I bought them through Best Buy. Here in Canada gaming headsets are usually final sale due to sanitary reasons. If some sort of legal action comes of this I am entirely ready to jump behind it. Corsair, I want my money back.

THERE'S MIC MONITORING? LOL. SMH. AAAAAAAnd now my headset is also stuck in on with the low buzzing tone as reported here on the forums. Can not turn it off, plugging it into the charger does nothing, taking out the mic = nothing, hard restart to console does nothing. I've already found the thread of this problem reported here where the Corsair rep forwarded those people here . . . . . . I hope Best Buy will refund me after the 30 day warranty. This is absurd. I'm getting a Steel Series. Otherwise Corsair, I hope the "warranty exchange" ticket I have opened with you guys is subject to a refund instead.

SO. I've had the headset since the end of Nov and the issues had gotten better, but now they are noticeably worse and I've pin pointed something serious occuring . . . I am: -Xbox Series x -Samsung TV UHD 7 series nu7100 -No surround sound or anything else -No other electronics around or on the tv stand (such as bluetooth or other internet connected devices except for the TV) -My headset since day 1 crackled.... Then the audio would crackle and then just cut out all the time when I was inactive on the controller for about 10 seconds. If I touched my controller or began moving then the audio would cut back in. This was annoying during cinematic scenes or dialogue in video games . . . -The other main issue was that when I would turn on my headset to begin playing it would beep on (screen would show "headset assigned", and then it would immediately beep off) -Sometimes I had to repeat this process a few times until it finally remained on, because it just kept turning off when I would turn it on. -Oh, did I mention that I only get an amber light during the charge process and no white light like it's suppose to show when it's complete? Lol. (least of my worries, but really . . .) And on the first day after charging it for the recommended 2 hours or so (I forgot how long it actually was) it died after less than an hour of use. The next day was better, but it lasts nowhere near as long as advertised... -NOW, THE REAL SERIOUS ISSUE here I've recently encountered about 4 times in the last two weeks is this: at times when my headset loses connection cause I'm a tad too far, I just have to turn it off & back on for it to be reassigned and reconnect. However, these times when I turn it off and then back on to reconnect the headset won't connect, AND my controller loses it's paired connection with the console and begins flashing.... 1 of these times was when I did not lose connection with the headset, but instead was on my phone and let my xbox go idle and the controller turned off. When I turned the controller back on it had lost connection and began flashing, and then my headset was no longer producing any audio. So this problem of the connectivity and pairing issue with the console and headset seems to be a real thing. To be quite frank I'm HELLA disappointed about this because the headset was marketed as the first officially licensed headset for the Xbox . . . Like for reals? And it runs like this?