this post was submitted on 06 Jul 2024
12 points (100.0% liked)

Microblog Memes

9988 readers
2172 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Walking_coffin@lemmy.dbzer0.com 1 points 2 years ago* (last edited 6 months ago) (1 children)
[–] scrion@lemmy.world 0 points 2 years ago (1 children)

How do you mention you can play multiple audio streams at the same time and then claim the OS is designed to let only one app access an audio channel / device? Which one is it now? Let's dig a bit deeper into this:

Also, let's not blame everything on the OS vendor being malicious. In most cases, playing multiple audio streams simultaneously would be annoying. In android, you can absolutely play multiple sources simultaneously, and Android will mix everything together and play it.

That being said, starting with API level 31, Android actually started to enforce a concept called audio focus at the system level. That would be around Android version 12. Audio focus is basically a token that can be requested and handed from app to app, and only the app holding the token gets to talk, everything else is faded out.

I'll agree that enforcing this and not making it configurable for the end user was a pretty dumb move, but that was simply a UX decision, not certainly malicious.

If your phone is rooted, you can work around it, e. g. via an xposed module.

[–] Walking_coffin@lemmy.dbzer0.com 1 points 2 years ago* (last edited 6 months ago)