this post was submitted on 14 Dec 2024
364 points (95.3% liked)

Android

17807 readers
114 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] turtlepower@lemm.ee 1 points 3 days ago (1 children)

An aux jack can't do that.

Really? Because there are aux jacks that allow for voice and volume control. Seems to me like they could make one for "real data".

[–] southsamurai@sh.itjust.works 2 points 3 days ago (1 children)

Well, if they can, that's interesting. But the method used to control volume and a mic are a hell of a lot simpler than transferring data. You'd need an expanded jack with extra circuitry afaik.

At that point, you're over to a usb cable, which is where all this starts.

[–] turtlepower@lemm.ee 1 points 3 days ago (1 children)

I mean, it's all just electrical signals. They could simplify the data for such a transfer. The volume and mic do have an extra wire or two in them, but those are still made no bigger than those without, and the jack just has an extra ring or two on it for the connection. Most everybody is oblivious to the presence of those rings. So, I would say it's totally possible, but is it worth it money-and-effort-wise?

[–] southsamurai@sh.itjust.works 3 points 3 days ago

Well, there's a difference between analog and digital. So, no matter how you cut it, if the aux jack is there, making it do double duty is essentially turning it into a usb port.

You can't really send much data at any kind of useful speed over the size and types of wiring in even the more complicated headphone wires, which usually aren't even present in an actual aux cord that's got a plug on each end.

The level of data transfer over Bluetooth is both higher, and is already set up to move data like the cars nowadays scrape.

So, while it would conceivably be possible to make new aux cords that are beefed up to do it, and make the jacks in both phones/tablets and head units interpret the signals, it isn't so much whether or not it's worth it money wise, it's will the car owners and passengers buy it?

The connectors, as is, have a limited number of connections, poles. To change that, you have to make the plugs and jacks bigger, or radically redesign them.

From a "worth it" standpoint, they're already taking the cheaper way out of trying to force everyone to use the Bluetooth that's already built in. Get device makers to stop having jacks, stop putting them in cars, and the problem is solved on their end. It then falls to the consumer to find a way around that.