Slashdot Mirror
Google Is Latest Company To Ditch Headphone Jack In Its Newest Smartphones (cultofmac.com)
When launching its original Pixel smartphone, Google mocked the iPhone 7's missing headphone jack in its marketing material. According to Cult of Mac, Google won't be doing the same for the Pixel 2. "The company has decided to remove the aging port from its latest handsets," reports Cult of Mac. "A new leak reveals that the lineup will rely solely on USB-C for wired connectivity." From the report: Incredibly reliable leaker Evan Blass has published pictures and details of Google's upcoming Pixel 2 smartphones on VentureBeat. He has also confirmed that neither device will feature a headphone jack, which means users will have to rely on a USB-C adapter or Bluetooth. It also means Google will no longer be able to put out Pixel ads that take sly swipes at the iPhone's missing port. Blass says both Pixel handsets will be powered by a Snapdragon 835 chipset -- the same one found in the Galaxy S8, the LG V30, and other 2017 flagships -- not a faster Snapdragon 836 processor as originally planned. Other features are said to include 12-megapixel cameras, 4GB of RAM, and 64GB or 128GB storage options. The smaller Pixel will pack a 5-inch 1080p display with a 16:9, while its larger sibling will pack a 6-inch Quad HD display with an 18:9 aspect ratio. Is the lack of a headphone jack a deal-breaker, or do you think the Pixel's other features, like stock Android and front-facing stereo speakers, will make up for it?
Android, leader in Chinese knock offs.
Samsung, the biggest cellphone maker of them all, still supports the 3.5mm jack. My new Note 8 has one, and with the 256 GB MicroSD card installed I have a ton of downloaded Tidal albums...
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
Sony and Nokia have phones with the same processor but with the 3.5mm jack, expandable storage and water/dust resistance. Their software is close to Google's and Sony contributes to AOSP. Google loses. Oh, and if you want to make good photos, buy a goddamn dedicated camera. No phone comes close and none will due to the laws of optics.
Waka Waka!
I, like many /. readers I want a phone with a MicroSD slot and regular security updates for at least 2 years.
>"Is the lack of a headphone jack a deal-breaker"
100% yes. Although I am not happy with lack of SD cards, I can handle that if a reasonable storage size is available, 64+GB. I am never happy with a non-swappable battery, but it seems that is beating a dead horse. Certainly also unhappy that wireless charging is so rare. Other unhappiness- lack of NFC, thinness instead of battery size, pixel density instead of brightness and efficiency, huge screen instead of portability.
But I have to draw the line somewhere, and it is at losing a simple, compact, compatible, easy, reliable headphone jack. There is simply no really good reason to remove it. I don't know when I will or won't need it, and I don't want to carry a stupid adapter that also is expensive, easy to lose, sucks more power, is likely to break, makes the phone weak and awkward while using it, and prevents charging while using it.
No SD slot, and likely no Miracast.
This is shaping up to be a very courageous phone design team indeed.
Please note I'm using the modern definition of "courageous", ie pants-on-head loony.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
Sucks to get stuck with Bluetooth if you want to travel, though... Many overseas airlines will not allow use of Bluetooth headphones, and technically the FAA did not allow them either (just BLE-based devices). And that's not even talking about the audio quality hit you'd get with Bluetooth unless you're running something decent like AptX or AptX HD (neither of which is available on iOS).
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
This shouldn't come as any surprise considering how it was discussed in the context of DRM a decade ago. People choose the cloud, people loose choice.
My car has aux in. They talk about how 3.5mm Jack's are crap and wear out. Well now I'm going to wear out my charging port and turn my phone into a paper weight. I think about it every time I plug my phone in to it.
I use it in my car to connect to my oem head unit. I use to connect to some old powered PC speakers in the bathroom. I use it to connect to aux in on a few other devices. In other words, DEAL BREAKER.
I know this is blatantly off topic and I'm just feeding a troll but I've been hooked and can't let go.
USB is a serial bus (2 pins for supply + 2 pins for serial signal), but USB-C isn't because is a parallel bus.
The Universal Serial Bus is a parallel bus?
USB-C is a new plug which can implement the USB3 protocol.
The USB3 protocol uses two sets of differential pairs for high speed communication. This is a serial bus and the same setup as many other systems including Serial ATA.
For backwards compatibility USB3 plugs contain wiring for both the serial USB2 signal and the serial USB3 signal, typically referred to as a dual signal. A typical device enumerates on one of the two busses, hubs enumerate on both to form two hubs one of which handles downstream USB3, the other downstream USB1/2.
However multiple serial busses does not make it a parallel bus, especially because the two signal sets run independently are clocked at different rates.
Oblig.
His is a perfectly valid response. Just because something's from the 1980's doesn't mean we need to ditch it. Hell, I'm from the 1980's and I find new uses for myself all the time.
Incidentally, the 3.5 mm jack is actually 19th c. tech, just slightly scaled down for some applications in the 20th c..
We're talking about a plug which is on possibly billions of devices.
This isn't just headphones and headsets, this is being able to plug into the analog port on amplifier, this standard is used on boom boxes 20 years ago, on audio 'in' ports for the past 20 or 30 years on a plethora of devices.
It's all fine and dandy for smarmy tools to say "oh shut up, get USB-C headphones!" but USB-C headphones won't work on my OTHER devices easily and I sure as shit don't see them changing any time soon, literally billions of devices over the world.
If you're not carrying some chip on your shoulder over Sony, unlike many people here, you might check out their phones.
The Xperias are still getting OS upgrades a few years later, not just security patches. My own handset is only about a year old from its own introduction, but it's been upgraded from 6.0.1 -> 7.0 -> 7.1, and is supposed to be getting an upgrade to Oreo in the future. It has a microSD card slot, a headphone jack, supports 192 khz/24 bit audio, Apt-X lossless bluetooth audio, and mine at least (Xperia Compact X) isn't stupidly slim, so it gets good battery life. I'm probably a bad example of phone usage, but I only charge it once every four days.
Hearing the difference now isn’t the reason to encode to FLAC. FLAC uses lossless compression, while MP3 is ‘lossy’. What this means is that for each year the MP3 sits on your hard drive, it will lose roughly 12kbps, assuming you have SATA – it’s about 15kbps on IDE, but only 7kbps on SCSI, due to rotational velocidensity. You don’t want to know how much worse it is on CD-ROM or other optical media. I started collecting MP3s in about 2001, and if I try to play any of the tracks I downloaded back then, even the stuff I grabbed at 320kbps, they just sound like crap. The bass is terrible, the midrangewell don’t get me started. Some of those albums have degraded down to 32 or even 16kbps. FLAC rips from the same period still sound great, even if they weren’t stored correctly, in a cool, dry place. Seriously, stick to FLAC, you may not be able to hear the difference now, but in a year or two, you’ll be glad you did. /pasta
Do you hear the crack of the sound barrier as the whoosh flies overhead?
No he didn't hear it : the sound of the whoosh was encoded with MP3 at a too low quality setting, he should have used FLAC instead.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]