Mobile OS as assistant using native Broadcast scanning with nrf5340

We tested a few of the newest Auracast capable phones and headphones. For example using the S24 and Galaxy Buds 2 Pro allows the user to search for broadcasts from the Bluetooth settings within the os. That works fine. We can see other broadcasts and tell the headphones to connect to those. Even if they require a password.

Our question is now: is there an example that allows the nrf5340 to act the same as the buds in the above mentioned example? 

We were unable to replicate the behavior using the broadcast sink sample. It seems like most of the features are there though? Using the sink sample Android detects the Auracast characteristics and displays all the options as with other headphones but nothing happens when clicking scan. So no scanning results. The example code itself can scan and find broadcasts just fine when no assistant is connected but does not publish those findings in any way that we were able to observe when connected to the Assistent.

Did we make a mistake? Is there a different example that is applicable for this use case? Or are the small missing parts coming later this year?

Parents
  • Hi Laurin, 

    LE Audio development is a bit cutting edge, so it varies a bit what is supported on different platforms in the market, which can make this interoperability a bit difficult. Though I would think this should work. I can ask the relevant R&D team.

    The example code itself can scan and find broadcasts just fine when no assistant is connected but does not publish those findings in any way that we were able to observe when connected to the Assistent.

    This is for instance something that I could assume is just issues with interoperability.

    Are you using the newest NCS version? And I see you mention both Mobile OS and Android here, making me a bit confused.

    Regards,

    Elfving

  • Thank you for the quick response!

    We tested on Android and iOS. But with iOS the app needs to take care of calling the correct endpoints and handling things. On Android they blocked third party apps from accessing the auracast characteristics. So we can only use Android OS to directly handle auracast scanning right now. But our product should be useable by both mobile OS in the future. 

    We are currently using 2.7.0 and have tested 2.9.0 but noticed no functional differences for this use case.

  • Laur1n M. said:
    So we can only use Android OS to directly handle auracast scanning right now. But our product should be useable by both mobile OS in the future. 

    Ah I see. I assumed you were referring to some obscure OS called "mobileOS".

    I'll ask the relevant R&D team and see. It might be that some Android/iOS interoperability thing is missing.

    Regards,

    Elfving

Reply
  • Laur1n M. said:
    So we can only use Android OS to directly handle auracast scanning right now. But our product should be useable by both mobile OS in the future. 

    Ah I see. I assumed you were referring to some obscure OS called "mobileOS".

    I'll ask the relevant R&D team and see. It might be that some Android/iOS interoperability thing is missing.

    Regards,

    Elfving

Children
No Data
Related