7 ms·

Google did all those things. The Pixel 3 will include USB C headphones and a dongle [1]. They have worked with Bose and other manufacturers on new bluetooth he

Google did all those things. The Pixel 3 will include USB C headphones and a dongle [1]. They have worked with Bose and other manufacturers on new bluetooth headphones that have additional functionality (switching between apps, talking with the assistant app). [2] [1] https://www.cnet.com/news/pixel-3-includes-usb-c-headphones-dongle-in-the-box/ https://www.cnet.com/news/pixel-3-includes-usb-c-headphones-... [2] https://www.blog.google/products/assistant/headphones-optimized-for-the-assistant/ https://www.blog.google/products/assistant/headphones-optimi...

wlesieutre 8y ago
I’m not just talking about one manufacturer on the Android side though, I’m talking about compatibility in the whole ecosystem. Google is including headphones that work with their phone, great, it would be embarrassing it they didn’t. If the headphone cable breaks and you buy replacement USB-C earbuds from another manufacturer, will it work with Google’s phones? Or will Google’s earbuds work with your partner’s non-Pixel phone? The point I want to make is that’s not a question you need to ask with Lightning or 3.5mm headphones. With USB-C you do.
- space_fountain 8y ago
  Since the Pixel Phones implement an open standard for USB-C audio actually yes it should just work cross device. Interesting this isn't something that's actually true of lighting headphones. There's no way to use those on any other brand of phone. I think what you're really saying here is that you like the fact that the IPhone has huge market share. That's a fair position to hold, but I personally vastly prefer open standards that can be implemented by anyone to closed ones.
  - Retric 8y ago
    In cases like this "should" often translates to 'no' then 'sometimes' then 'mostly' but rarely a simple 'yes'. EX: "Why USB-C audio still doesn't work" https://www.pcworld.com/article/3284186/mobile/bring-back-the-headphone-jack-why-usb-c-audio-still-doesnt-work.html https://www.pcworld.com/article/3284186/mobile/bring-back-th...
    - wlesieutre 8y ago
      Though reading the specifics there, it looks like Google's adapters in particular should work with any other phone because they can handle analog or digital signals. So they're doing well. Other manufacturers are doing... less well.
      - nfriedly 8y ago
        Google's adapters can work on most phones, but Google's phones can't work with most adapters :-(
        PascLeRasc 8y ago
        It's unfortunate because it's the "USB-C standard" not to do analog through the pins, but I think this a case where it's ok to break the standards. I'm not sure if there are any IEEE fines for that though.
- ajross 8y ago
  > I’m talking about compatibility in the whole ecosystem Uh... Apple's solution is Lightning-only, Google's is a standard USB thing. Surely the argument goes exactly the other way. > If the headphone cable breaks and you buy replacement USB-C earbuds from another manufacturer, will it work with Google’s phones? Yes, it does, because this is a standard USB-C signal. You're asserting stuff that simply isn't true.
  - wlesieutre 8y ago
    As described in the above PCWorld link, the problem is that the standard is open ended and the ecosystem didn't all agree on how to deal with analog vs digital audio signals and devices. Some USB-C headphones or adapters will be happy with whatever. Others will not. Since some phones can output an analog audio signal over the USB-C connector (and ship dongles without a DAC), while others output digital only and rely on the dongle including its own DAC, the argument absolutely does not go the other way. Any lightning headphones or lighting to 3.5mm dongle will work on any phone with a lightning port. EDIT: Here's a separate complaint - if you want to charge an iPhone while you have headphones plugged in, there are at least splitter/dongle accessories for that. USB-C Android phone? Good luck. https://www.theverge.com/circuitbreaker/2018/5/18/17369236/android-usb-c-charge-listen-headphone-jack-adapter https://www.theverge.com/circuitbreaker/2018/5/18/17369236/a... >Android Police reported that Google quietly pulled the listing for the one adapter it had in its online store without ever selling it. The product is also unavailable on the manufacturer’s website. According to Android Police, a few units did ship from Amazon, but the reviews were so bad that the product was quickly pulled.
    - rootusrootus 8y ago
      The more I hear about issues with USB-C the sadder I get. It feels like we had an opportunity for 'one connector to rule them all' but the standards are so loose that what we got was something that looks like one connector but could be one of many, and it may or may not work for a particular use.
    - drcharris 8y ago
      See today's Android Police artice on the Moshi adapter that just got re-released today. https://www.androidpolice.com/2018/10/09/moshi-type-c-audio-charging-adapter-now-available-40/ https://www.androidpolice.com/2018/10/09/moshi-type-c-audio-... Comments on that page point to this one on Amazon, looking very similar but a lot cheaper, with positive reviews: https://www.amazon.com/dp/B07FCZY1ZB/ref=cm_sw_r_cp_apa_T2qVBb2TQWBZQ https://www.amazon.com/dp/B07FCZY1ZB/ref=cm_sw_r_cp_apa_T2qV....
huehehue 8y ago
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.
- jszymborski 8y ago
  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-Integrated-Hands-Free/dp/B07CXVZCYL 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 />
  - voltagex_ 8y ago
    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.
    - clhodapp 8y ago
      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?
- 8y ago

wlesieutre 8y ago

I’m not just talking about one manufacturer on the Android side though, I’m talking about compatibility in the whole ecosystem. Google is including headphones that work with their phone, great, it would be embarrassing it they didn’t. If the headphone cable breaks and you buy replacement USB-C earbuds from another manufacturer, will it work with Google’s phones? Or will Google’s earbuds work with your partner’s non-Pixel phone? The point I want to make is that’s not a question you need to ask with Lightning or 3.5mm headphones. With USB-C you do.

space_fountain 8y ago
Since the Pixel Phones implement an open standard for USB-C audio actually yes it should just work cross device. Interesting this isn't something that's actually true of lighting headphones. There's no way to use those on any other brand of phone. I think what you're really saying here is that you like the fact that the IPhone has huge market share. That's a fair position to hold, but I personally vastly prefer open standards that can be implemented by anyone to closed ones.
- Retric 8y ago
  In cases like this "should" often translates to 'no' then 'sometimes' then 'mostly' but rarely a simple 'yes'. EX: "Why USB-C audio still doesn't work" https://www.pcworld.com/article/3284186/mobile/bring-back-the-headphone-jack-why-usb-c-audio-still-doesnt-work.html https://www.pcworld.com/article/3284186/mobile/bring-back-th...
  - wlesieutre 8y ago
    Though reading the specifics there, it looks like Google's adapters in particular should work with any other phone because they can handle analog or digital signals. So they're doing well. Other manufacturers are doing... less well.
    - nfriedly 8y ago
      Google's adapters can work on most phones, but Google's phones can't work with most adapters :-(
      - PascLeRasc 8y ago
        It's unfortunate because it's the "USB-C standard" not to do analog through the pins, but I think this a case where it's ok to break the standards. I'm not sure if there are any IEEE fines for that though.
ajross 8y ago
> I’m talking about compatibility in the whole ecosystem Uh... Apple's solution is Lightning-only, Google's is a standard USB thing. Surely the argument goes exactly the other way. > If the headphone cable breaks and you buy replacement USB-C earbuds from another manufacturer, will it work with Google’s phones? Yes, it does, because this is a standard USB-C signal. You're asserting stuff that simply isn't true.
- wlesieutre 8y ago
  As described in the above PCWorld link, the problem is that the standard is open ended and the ecosystem didn't all agree on how to deal with analog vs digital audio signals and devices. Some USB-C headphones or adapters will be happy with whatever. Others will not. Since some phones can output an analog audio signal over the USB-C connector (and ship dongles without a DAC), while others output digital only and rely on the dongle including its own DAC, the argument absolutely does not go the other way. Any lightning headphones or lighting to 3.5mm dongle will work on any phone with a lightning port. EDIT: Here's a separate complaint - if you want to charge an iPhone while you have headphones plugged in, there are at least splitter/dongle accessories for that. USB-C Android phone? Good luck. https://www.theverge.com/circuitbreaker/2018/5/18/17369236/android-usb-c-charge-listen-headphone-jack-adapter https://www.theverge.com/circuitbreaker/2018/5/18/17369236/a... >Android Police reported that Google quietly pulled the listing for the one adapter it had in its online store without ever selling it. The product is also unavailable on the manufacturer’s website. According to Android Police, a few units did ship from Amazon, but the reviews were so bad that the product was quickly pulled.
  - rootusrootus 8y ago
    The more I hear about issues with USB-C the sadder I get. It feels like we had an opportunity for 'one connector to rule them all' but the standards are so loose that what we got was something that looks like one connector but could be one of many, and it may or may not work for a particular use.
  - drcharris 8y ago
    See today's Android Police artice on the Moshi adapter that just got re-released today. https://www.androidpolice.com/2018/10/09/moshi-type-c-audio-charging-adapter-now-available-40/ https://www.androidpolice.com/2018/10/09/moshi-type-c-audio-... Comments on that page point to this one on Amazon, looking very similar but a lot cheaper, with positive reviews: https://www.amazon.com/dp/B07FCZY1ZB/ref=cm_sw_r_cp_apa_T2qVBb2TQWBZQ https://www.amazon.com/dp/B07FCZY1ZB/ref=cm_sw_r_cp_apa_T2qV....

huehehue 8y ago

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.

jszymborski 8y ago
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-Integrated-Hands-Free/dp/B07CXVZCYL 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 />
- voltagex_ 8y ago
  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.
  - clhodapp 8y ago
    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?
8y ago