Android
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
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
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.
-
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.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
view the rest of the comments
But this is almost all false or just speculation.
Instead of having audio and usb-c, now you have usb-c port, usb-c headphone dongle, the finally audio port and usb-c port again. Unless you want to intentionally buy a usb-c exclusive set of headphones that won't work with whatever next "revolutionary port technology" comes out.
As long as they still work, good headphones from 40 years ago are still good. Headphone tech has not significantly changed. Amps, DACs, etc have, but not the actual drivers.
As far as space goes, reasonable DAC components are getting smaller and smaller while phones tend to be getting larger as people want more screen space. The space savings on hardware here is not significant. Seriously go and look up sizes of the components needed for audio out.
As far as thinner goes, the width needed for a headphone jack is like 2mm more than what's needed for a usb-c port, and there's width needed for internal speakers either way. I'm also not sure how much thinner people want cell phones to be at this point. We're pretty close to the point of sacrificing device drop resistance for size anyway (arguably we've passed that point with most people doubling the size of their phone with a protective case). Not to mention that the real thing preventing more thinness is the camera lenses now, as easily evidenced by the camera island bumps all phones have now.
Lastly, you can't seriously be arguing that analog audio out represents any significant amount of attack surface kernel wise. Like holy shit man. Wow. Yes, technically every line of code is increased attack surface, but it's a huge assumption that USB-C audio is in any way more secure or less surface.
Standards change as they get developed and better, sorry. I don't see the "new revolutionary port technology" coming out in the next couple of decades, especially with the EU forcing USB-C on all (which is a good thing). USB-C is still fairly new and not adopted everywhere. And I'd bet money that most people don't keep 40 year old headphones. Like, I said, sure it sucks now because we're in the middle of it.
Except the USB-C is here to stay for a good bit...unless you're proposing making it a power only connectors? Some secure devices do that, but why handicap the new port on mobile device that has limited space? So yes, removing the audio port code portion on a device with no audio port makes sense, when we get there.
Space is at a premium in phones as they are already fairly small and cramped. And why duplicate the ports (have two audio ports) simply because you don't want to buy a dongle or a new headset to replace 40 year old devices that have drastically been improved?