this post was submitted on 01 Aug 2025
13 points (72.4% liked)

Android

22005 readers
4 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 3 years ago
MODERATORS
top 6 comments
sorted by: hot top controversial new old
[–] mrfriki@lemmy.world 13 points 1 year ago

Still waiting for Bluetooth LE audio and the LC3 codec from back BT 5.2 to see a widespread use. Maybe in the next decade or so.

[–] nesc@lemmy.cafe 12 points 1 year ago

They won't. πŸ˜„

[–] Onomatopoeia@lemmy.cafe 8 points 1 year ago (1 children)

Another video to communicate what could be explained in a paragraph.

[–] rustyredox@lemmy.world 6 points 1 year ago

I'd like to discover alternative sources if you know any. Most written literature I come across in searches are either technical specifications biased from the Bluetooth consortium, or watered down blog spam of the same consortium's news releases. Very little in terms of critical analysis or observations of user adoption and real trends in the original equipment manufacturers.

For example, all throughout the news releases of 5.X, no one would discuss if any improvements to bidirectional audio sinks for microphoned headsets were implemented or planned. It's like the consortium is content keeping us all on phone calls with HFP from the 1990s at bitrates of 64kbps, leaving Discord audio sessions sounding like on-hold music at the DMV.

[–] CrayonDevourer@lemmy.world 2 points 11 months ago (1 children)

They won't because it's nearly 2026 and they STILL DON'T HAVE STEREO AUDIO + MIC CHANNEL as a STANDARD FEATURE

[–] rustyredox@lemmy.world 1 points 11 months ago

It's so frustrating that mono audio+mic has been the norm for so long. The awfully small bit rate for both sink and source channels is just the cherry on top. I have to break out a USB-C DAC with a TRRS connector for discord calls on my tablet, as every manufacturer has done away with internal headphone jacks, just maintain the same audio quality I would have on speakerphone mode.

Android is also pretty frustrating and that you can't bifurcate your audio syncs and sources. For example on any modern Linux distribution, you can at least direct apps to use your internal laptop microphone by default, and your headphones for full bit rate stereo audio only - to work around and avoid Bluetooth's ancient HFP protocol. Why Android developers can't replicate this basic audio muxing is beyond me, but resorting to a device's internal microphone comes with its own setbacks.

Perhaps that muxing on Android is only possible for Bluetooth headphones without a microphone, but I can't find any earphone devices that are not also headsets anymore. Just doesn't seem to be a thing any longer.