News for hackers. Stuff that matters.
Re:New Google Pixel 3, Pixel Slate, and Home Hub by jszymborski on Tuesday October 09, 2018 @07:31PM (#18180698)
I'm not a fan by any means of axing the 9mm jack, but to get around jackless electronics, I've been using a tiny (and cheap) bluetooth receiver so I can keep using my old headphones... it's been great, and no more annoying that charging wireless headphones.

This is not the model I have, but I've something very similar by Anker https://www.amazon.com/Roav-Bluetooth-Noise-Cancellation-Int...

EDIT: Sidenote, I don't know how much I'd trust cheap bluetooth adapters re: security... there is a non-zero chance it's spewing my conversations out, ripe for anyone w/ the proper equipment to listen in. <Tin Hat />

Re:New Google Pixel 3, Pixel Slate, and Home Hub by voltagex_ on Tuesday October 09, 2018 @11:45PM (#18181797)
Funny - at least that one doesn't lie about apt-x support. Bluetooth audio sounds like crap to me, I'll be using wired headphones until the patents on non-crap Bluetooth audio expire, I guess.

Supply chain issues notwithstanding, I think you're pretty safe with a CSR bluetooth chip - they're in everything. Whether it's a clone or an original though, no idea.

Re:New Google Pixel 3, Pixel Slate, and Home Hub by clhodapp on Wednesday October 10, 2018 @03:20AM (#18182698)
What confuses me about Bluetooth audio is that I did the math a while ago and unless I got it wrong, reasonably modern Bluetooth should have the bandwidth to stream uncompressed digital audio... So why are we still stuck with this awful lossy compression?