“Pixel 2 and Pixel XL 2 will both ditch the headphone jack.”

Bluetooth Headset:<p>PRO:<p>- no cable that annoys you<p>CON<p>- heavy, thus fall out your ear while running. - small battery (which evolves, but slowely) - more expensive - redundant audio processors - mostly low quality audio processors - bluetooth is unstable<p>Cable Headset<p>PRO<p>- good audio quality - low price (in comparison) - light, stays in your ear while jogging - usable on a range of devices - compact design - make use of a huge battery, namely the one in your phone<p>CON<p>- the cable breaks after some time - the cable restricts you<p>I don&#x27;t see the why I would want to change my standard headphones for a technology that is bound to fail me over time, either by running out of juice or by a bluetooth hickup. I wouldn&#x27;t buy a phone without a headphone jack. Period.

So stupid. What a blatant attempt at grabbing money.<p>Headphone ports are one of the last truly ubiquitous pieces of technology still in use today. 1&#x2F;8&quot; headphone jacks work in EVERYTHING. And we want to throw that all away, because technology.

While I do own a few pairs of Bluetooth headphones I have yet to have any, from the cheap to the expensive, not have occasional hiccups. Because of this I love using my headphone jack.<p>I&#x27;m sad that this is a trend especially without a good, alternative and standard way of using headphones over, say, USB-C. I mean I would be _completely fine_ with removing the 3.5mm if you could re-use another jack for the same purpose but being restricted to Bluetooth or USB-C dongles, at least to me, sucks.

Phone connectors are rubbish, ancient technology. The only thing they have going for them is the network buy-in from literally 140 years of legacy.[1]<p>They are fine in static audio applications, but their performance on mobile devices is abysmal. Put the device in a pocket, and every time you move or sit down, you&#x27;re putting huge lateral stress on the connector. Either the contacts get deformed and become intermittent, the plug bends and&#x2F;or shears off in the jack, or the wire on the plug side develops an open circuit from wear. I&#x27;ve personally damaged or destroyed the headphone jack on every phone I&#x27;ve owned that had one.<p>In the last couple of weeks I&#x27;ve transitioned most of my audio to Bluetooth. BT isn&#x27;t exactly a pleasant experience, but once paired, it&#x27;s relatively seamless. I even converted my ubiquitous ATH-M50x headphones to BT using a module[2].<p>[1]: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Phone_connector_(audio)#Modern_connectors" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Phone_connector_(audio)#Modern...</a> [2]: <a href="https:&#x2F;&#x2F;www.amazon.com&#x2F;Bluetooth-Adapter-Amplifier-Technica-ATH-M50x&#x2F;dp&#x2F;B01MFFH54C" rel="nofollow">https:&#x2F;&#x2F;www.amazon.com&#x2F;Bluetooth-Adapter-Amplifier-Technica-...</a>

At least in the case of the Pixel, it&#x27;ll be a USB-C port instead of an Apple-controlled Lightning port. I prefer the lightning connector but I don&#x27;t like it being only on the iPhone (you can&#x27;t even use iPhone headphones on the Mac!) and locked down to Apple&#x27;s approval for everything.

There&#x27;s a right way and a wrong way to transition to a new interface technology.<p>The right way is to offer the new interfaces as options or have them be there in addition to the legacy interfaces. That way people with peripherals that are only compatible with legacy interfaces can still use them, while allowing early adopters to use the new interface.<p>This is what happened when the USB standard was released. Computers were sold with both USB and the old serial&#x2F;parallel ports. It took many years to get to the point that serial and parallel ports were no longer standard: well, after most every consumer had already switched to using USB for just about everything.<p>The wrong way to go about this is what&#x27;s happening in this instance, where a widely-used legacy interface is being completely ignored in favor of a new interface that has relatively little adoption.<p>No wonder so many consumers are upset, and that doesn&#x27;t even touch issues like DRM and the analog hole, where non-DRM-forcing legacy interfaces are clearly better for the consumer.

I&#x27;m a new bluetooth headset adopter. I&#x27;ve been growing increasingly keen with them:<p>You can grab them on Amazon for $20 to $50.<p>- SoundPEATS Bluetooth headphones is $19.99 with Amazon Prime. Some hiccups on this one with connecting. I keep this one as a backup when battery runs out.<p>- Phaiser BHS-730 works like a charm. $39.99 with Amazon Prime. Nice magnet feature that allows you to wear the unit around your neck when not using it.<p>They work with your smartphone and your laptop.<p>So the major downside? These things run out of battery power after 4-5 hours on average. This sucks because you&#x27;re typically using them on the go.<p>Hopefully more people using bluetooth will result in future headphones with improved battery life.

Horrible idea. I&#x27;m on holiday at the moment, didn&#x27;t bring my headphones - don&#x27;t often use them, but on flight and occasionally lazing by the pool would have liked to listen to my audiobook.<p>I decided to get a new cheap pair when I was shopping, remembering just in time that my phone model doesn&#x27;t have standard audio equipment. So from what was available instead of a simple €5 purchase, I would be on the hook for another little adapter cable priced at €10 or €39 for another set of Apple&#x27;s headphones with their bespoke charging port.<p>It&#x27;s not &quot;brave&quot; it&#x27;s shit and annoying. Also travelling with Bluetooth speakers, which use standard cables, means I need to carry multiple cables around because of proprietary charging port that they continue to be able to get away with.<p>I like my phone, does what I need, but not being able to pick up a cheap pair of headphones on holiday, yeah thanks Apple. Shit decision. Google... please read this real world experience, don&#x27;t make your equipment annoying too.

While I am sad about this, at least it is likely to be USB C, which means my dongle and&#x2F;or head phones will work with more than just my phone.<p>That is the only silver lining here that I can see.

That&#x27;s terrible. I wouldn&#x27;t buy a phone without a way to plug in. I would lose headphones that are not attached with a wire.

There&#x27;s plenty of other phones. Bluetooth is absolute utter shit. No, it&#x27;s worse than shit. It&#x27;s an atrocity. Half the time it doesn&#x27;t connect. Another third it says it&#x27;s connecting but it&#x27;s playing from your phone&#x27;s speakers still. And when you finally get it working--if you do before smashing the damn phone into the ground--it has shitty sound quality. The engineers who work on this should be ashamed of what they&#x27;ve put out into the world: an ugly monstrosity that seems to be a terrible solution looking for a problem. Reliable wireless connections would be nice, but I&#x27;m done hoping it will ever happen as long as Bluetooth is a standard. Not a single Bluetooth product I&#x27;ve ever operated has operated with any reliability whatsoever. It&#x27;s just absolute garbage.

I haven&#x27;t used or tried AirPods, but every Bluetooth device i have tried has a noticible to awkward lag when watching video on a phone.<p>This ranges from earphones to my sound system in the house. So unless wireless can solve that problem, it seems like we are giving up something by making the switch.

I&#x27;m going to take the contrary view here.<p>I hate hate headphone cords. OTOH I&#x27;ve use 3 different cordless headphones regularly (ironically not AirPods) and I don&#x27;t have any particular problems.<p>Positives: The cord doesn&#x27;t get tangled, the remote works properly on all phones and laptops (unlike the multiple standards for wired remotes).<p>Negatives: The battery life. They cost more for similar quality (although this isn&#x27;t as clear cut anymore: eg less than $100 gets quite competent JBL BT headphones).<p>Neutral: I don&#x27;t find the audio any worse. Some wired headsets are better, but many aren&#x27;t.

I have one of the iPhones without the headphone jack and it&#x27;s a constant pain. I tend to agree with Apple&#x27;s moves of this sort, but this particular one was a bad idea. It just plain sucks.

Good lord people, if you don&#x27;t like it then don&#x27;t buy it. I swear to god this exact same reaction occurs every time something old starts getting replaced by something new.<p>Same thing happened with the iPhone 7, even though it came with a very neat little adapter so you can plug whatever headphones you want into it.<p>Even in some dystopian future where phones are completely wireless, I&#x27;m sure you can still buy a little Bluetooth adapter to put on the end of your electrostatic headphones that you wear whilst jogging each day.

I believe this is an objectively stupid idea.<p>I want to be openminded and understand why I would buy a phone that doesn&#x27;t have a headphone jack, when there are phones that exist that do have a headphone jack (AND bluetooth!).<p>I don&#x27;t think I can understand these companies&#x27; motives unless I can be convinced there&#x27;s some benefit here. Can someone who likes phones without headphone jacks tell me why they are a better product that phones that do have headphone jacks?

Not even a year since they mocked the iPhone for the lack of headphone jack and they themselves removed it. It’s a matter of time before the rest of the phones ditch it too. Or may be it becomes a “feature” for the high end phones. Got to say Apple saw it first.

This phone better be waterproof...

I do not understand how this benefits anyone except the &quot;must be thinner&quot; fetishists. With Apple it was their usual form-over-function problem, which is at least what we expect from Apple, but why would Google follow suit?

It may be useful if they trade the space saved by removing the headphone components to accomodate more battery capacity. This assumes that you&#x27;re already using BT for your phone audio needs.

Hey, remember when they specifically called out Apple for not having a headphone jack at the first Pixel reveal? I wonder how they’re going to spin it now.

I just don&#x27;t understand why we can&#x27;t have the best of both worlds. I mean, having the headphone jack doesn&#x27;t mean not having bluetooth.

The current Pixel bluetooth support is horrendous. I hope this is not true.

Do not believe it.