Yes, I thought it might be a code issue. It just seemed weird that with other Debian based distros (ubuntu and mint) I have never had this issue. I hope this weekend I get enough free time to investigate further. Thank you for the tip.
Maybe the necessary codecs just aren’t installed in Debian by default? Mint and Ubuntu are targeted at laptops for general use, so it makes sense they’d bundle all Bluetooth codecs in a default installation to be ready for most users. But Debian makes fewer assumptions like that, and is often used for servers, so perhaps they didn’t want to bloat it with codecs that many installations will never need.
I’m just guessing here, but that makes sense to me.
Yes, I thought it might be a code issue. It just seemed weird that with other Debian based distros (ubuntu and mint) I have never had this issue. I hope this weekend I get enough free time to investigate further. Thank you for the tip.
Maybe the necessary codecs just aren’t installed in Debian by default? Mint and Ubuntu are targeted at laptops for general use, so it makes sense they’d bundle all Bluetooth codecs in a default installation to be ready for most users. But Debian makes fewer assumptions like that, and is often used for servers, so perhaps they didn’t want to bloat it with codecs that many installations will never need.
I’m just guessing here, but that makes sense to me.