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: [email protected]
💡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: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
📰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 [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
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
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
There's just exactly no upsides.
Among other things, a USB-C connector is less stable than a 3.5mm jack, and can twist the cable since the connector cannot spin.
Sure, it can do a lot of things, but there's no reason to break an existing standard if the proposed successor is inherently worse.
I was looking for someone to mention the connection itself. To add to that the connector is a lot more delicate since it's some ~~40~~24 pins vs 3 or 4.
AND if my one USB-C port wears out from use, now I need a whole ass new phone now as opposed to "oh damn, well the phone still works without headphones, I'll suffer for a bit until I can comfortably replace it."
This is actually something I had once considered too. It's not that they want to downgrade the port itself, it's also that they want to downgrade the AMOUNT of it. I went looking for phones with two ports (I was also curious about using a phone as a data bus) and I could literally find none.
This is why when it comes time to decide on a compromise, Bluetooth (and its audio issues) wins out versus anything with ports. Because it's a solution that doesn't throw away options with it.
"maybe i should get a DAC for the time beeing"
At least this would ONLY break my shitty DAC with flimsy cable and not the headphones.
I guess you could try something like this