4 ms·
Whenever I've done it I've always gone with #2, wireless non buds. I've gotten multiple pairs. While they don't get lost, I have always ended up with two fundam
by joecot 5y ago
Whenever I've done it I've always gone with #2, wireless non buds. I've gotten multiple pairs. While they don't get lost, I have always ended up with two fundamental problems with them
#1 Bluebooth connectivity to computers. If I was just using my phone they were mostly fine, but at a computer it was a constant fight to get them to connect, to work with whatever app I'm using, and especially when I'm switching back and forth between using them for listening to music or using them to video conference. This might also be partly because Linux is my main driver, but having to switch back and forth between high quality audio output for music and two way cell phone quality audio sucks.
#2 Having owned multiple pairs over the years, none of them would connect over Bluetooth while charging. Let me make my wireless headphones temporarily wired.
At this point I use an over the ear headphone with a mic and a USB DAC. I specifically only get phones with a minijack so I could use them with that too.
- thrashh 5y ago#1 is because your BT drivers suck. The Mac’s BT driver seamlessly switches fine and I don’t have connection issues. I actually don’t have connection issues on Windows either, but it does have the switching problem.
- kelnos 5y agoNot everyone uses a Mac, and I expect that most people aren't going to change OSes (and app ecosystems) just to get wireless headphones to work well. Less disruptive to just use wires.
- mrighele 5y agoFor #1 I would blame linux. It's bluetooth stack is... let's say less than stellar, expecially for headsets. I always have to fiddle to get my headset to work, while it works perfectly with any other OS I tried (MacOS, iOS, Android, Windows). #2: True, but usually the battery of a pair of headphones last much longer than earbuds, in my case at least 4 days, so I just put them in charge at night