Yeah, they'll include a dongle that will break in less than a year with very casual use. Ask me how I know.
And there are _very_ few third-party options that work with the Pixel lineup -- not necessarily Google's fault, but early adopters of the no-3.5mm trend are being punished while the market catches up.
Also, I already have headphones. I don't want Google's USB C headphones. They wouldn't need to include any of this junk with the phone if they didn't remove the jack in the first place.
Yeah, they'll include a dongle that will break in less than a year with very casual use. Ask me how I know.
FWIW, this isn't true in my experience. I've kept mine in my pocket jangling around with my keys and use it frequently, and never had any issues.
Also, I already have headphones. I don't want Google's USB C headphones. They wouldn't need to include any of this junk with the phone if they didn't remove the jack in the first place.
If you already have headphones you like, it seems like this is no different between Pixel/iPhones.
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.
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 />
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.
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?
I don't think you read the comment you responded to. Wlesieutre correctly points out that the Android marketplace has multiple incompatible standards of USB-C headphone dongle and USB-C earbuds, so they won't necessarily work with another USB-C Android device in your household.
You can say that's not Google's fault, and that it doesn't apply to Pixel devices specifically. But like it or not, Google chose to vomit their platform across dozens of manufacturers and thousands of devices. If they didn't want the kind of chaotic inconsistency exampled above, they should have gone with the iPhone/Pixel approach from the beginning.
And there are _very_ few third-party options that work with the Pixel lineup -- not necessarily Google's fault, but early adopters of the no-3.5mm trend are being punished while the market catches up.
Also, I already have headphones. I don't want Google's USB C headphones. They wouldn't need to include any of this junk with the phone if they didn't remove the jack in the first place.