I used some old USB-C headphones from an old google pixel phone for a long time, no issues at all good quality.

Define “give a good connection”. If it’s activating the microphone too, the connection quality will drop because of the bandwidth requirements.

Possibly a stupid question, but are you using the wireless dongle that came with the headphones? I have the same headphones and run arch as well, and my pc recognizes the dongle as “Audeze Maxwell usb” or something like that.

I’m running pipewire for my audio system and iirc it worked out of the gate with these headphones, though I did some modifications to get digital surround sound working too.

This should just be working if it’s standard USB audio; I’d recommend just researching issues with USB headphones in general. Maybe also try another cable.

If nothing works, it looks like you can use a double 3.5mm cable on this model, which pretty much every large retailer with an electronics section should have.

Bluetooth protocol support for audio is a bit of a mess, and many Bluetooth devices (especially knock off or no-name budget brand headphones/headsets) skimp on applying the standard properly.

Absent the absolute latest Bluetooth standard support (5.3 or better), you’re usually limited by the protocol to very poor quality audio. It gets even worse of your device shows up as a headset inst4ad of heaphones/speaker since it has a mic return channel crammed into the very restricted bandwidth too. The way (mostly quality) vendors have worked around this prior to the latest Bluetooth protocol versions was to use raw data channels with negotiated compression formats and a special “escape hatch” protocol supported by Bluetooth (A2DP). Both sides had to negotiate a shared compression algorithm and implement it for sending the compressed audio so it could be decided at the destination. Poorer quality or older headphones, and older Bluetooth Linix stacks didn’t do this very well.

Not sure if any of that is applicable, but in general Bluetooth is always worse quality than wired because of bandwidth restrictions. And until Bluetooth 5.3 that added LE Audio and a related very efficient audio compression algorithm, it was a compatibility crap shoot.

It will depend on the drivers that Audeze Maxwell supply? I can’t see any USB drivers for Linux beyond the dongle but they may exist.

However if they have a 3.5mm port then I’d use that. I have a Sony headset and while I don’t have any issues with Bluetooth, I do like to use 3.5mm analogue conenctions to save battery (even with noise cancelling on the battery lasts way longer off Bluetooth). I bought a long 3.5mm cable online and plug it into the front of my PC. No USB or Bluetooth faff, it just works, and at high quality.

However note that if you want the mic to work too it will depend on whether the headset’s 3.5mm jack is set up for both audio and mic (if it’s good quality it should be), plus you will need a 4pin 3.5mm plug and cable to pick up the mic from the headset and cable instead of the common 3pin audio only plug. At the other end if your pc has separate 3.5mm audio and mic jacks you will need an adaptor that splits the audio/mic into two cables to plug in to both jacks. If it’s a desktop there will be separate jacks around the back although sometimes the front jack may be a combined mic/audio jack, or you may also have one joint jack if it’s a laptop. If you do need to split the audio and mic then you can find these adaptors and also 4pin 3.5mm cables on ebay or amazon.

Edit: Just in case you’re not aware - an audio only 3.5mm cable has 2 coloured bands on the plug (splitting it into 3 metal rings or pins). An audio + mic 3.5mm cable has 3 coloured bands on the plug (splitting it into 4 metal rings or pins).

Edit 2: sorry look for 4 pole 3.5mm rather than 4 pin; you’ll see the better quality stuff when searching as pole is the correct term!

How ancient is your arch install? Are you even on pipewire? That’s what you need for stable good quality bluetooth audio, pulse is awful by comparison.