tl;dr from the article:

  • Auracast is a feature of the Bluetooth LE Audio standard that enables broadcasting audio to nearby devices.
  • Android added basic support for Bluetooth LE Audio in Android 13, including support for starting and connecting to audio streams.
  • Android 15 could get a dedicated page for audio sharing, signaling that Auracast could be a key feature of the new OS.

Screenshots from the article of how the feature would look like:

  • solrize@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    3
    ·
    10 months ago

    I keep seeing “share nearby” in Android 13 share screens and it creeps me out. I’ve been wondering if there is a way to disable it. I still use wired earbuds and made sure to buy a phone that supports them.

    • JackGreenEarth@lemm.ee
      link
      fedilink
      English
      arrow-up
      11
      ·
      10 months ago

      It needs consent from both parties and just uses stuff like Bluetooth or WiFi, what’s the problem with it? You can pin other stuff to the top to force it down the list.

      • solrize@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        5
        ·
        10 months ago

        The main thing is that it’s obtrusive and it feels like Google is shoving it at me, which has to be nefarious. It hadn’t occurred to me to pin other stuff. I’d rather just get rid of the nearby feature since I’m never going to use it.

    • Squizzy@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      10 months ago

      The number one feature I want disabled elis that fuckin log in with Google on every page that loads these days

    • Pantherina@feddit.de
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 months ago

      You should probably switch to another manifacturer for a future phone if updates take so long. Android 14 was released for Google Phones on 4.10.2023 an “Google verified” Android versions get early access to the code too.

      GrapheneOS is on Android 14 roughly since that time

      • NeroC_Bass@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 months ago

        I have a galaxy s21 ultra, they’re still releasing updates and phone works flawlessly though, so you can understand my want to not switch yet.

        • Pantherina@feddit.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          9 months ago

          Jor, Samsung hat von allen die schlimmste Bloat/Spyware und die Geräte sind absichtlich nicht reparierbar und erlauben custom androids die Sicherheitsfeatures nicht…

          • NeroC_Bass@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            9 months ago

            I bought my Samsung carrierless, there has been ZERO bloat ware on it. I’ve also had this phone fixed THREE TIMES from stuff I BROKE on it. The screen, the microphone, and the camera. Hands down the best, and longest phone I’ve ever owned.

            • Pantherina@feddit.de
              link
              fedilink
              English
              arrow-up
              2
              ·
              9 months ago

              I dont think security fixes are unstable. Google pushes those updates to Pixels and they never break.

              Sorry but this is just a case of too slow security patches. It may not be very problematic for your threat model, and GrapheneOS is very secure here, but better safe than sorry

              • Hiro8811@lemmy.world
                link
                fedilink
                English
                arrow-up
                2
                ·
                9 months ago

                What I meant is that Android upgrades are slow 13->14 for example. Patches and fixes roll out every week, for my phone at least