Use bluetooth device as an input in 4a (4a-hal & 4a-softmixer)

Description

The use of a bluetooth device as an audio input in 4a must be implemented ASAP.

What is needed :

  • Development of a '4a-hal' controller plugin that will get the connected bluetooth device. It must register itself to AGL bluetooth network service (provide by connectivity) to stay informed of the connected bluetooth devices.

  • Provide the bluetooth hardware address to 4a-softmixer.

  • Creation of an input PCM using the received bluetooth hardware address in '4a-softmixer' (an example is available in 'bluealsa-aplay').

  • Use the previously created PCM to stream audio from the bluetooth device to speaker output.

Environment

None

Activity

Show:

Walt Miner 
September 28, 2018 at 3:51 PM

Agreed. Please resolve this issue.

Stephane Desneux 
September 28, 2018 at 12:17 AM

Yes it can be resolved (from a development POV) but now have issue https://lf-automotivelinux.atlassian.net/browse/SPEC-1763#icft=SPEC-1763 to solve.

Walt Miner 
September 27, 2018 at 8:06 PM

Can this be resolved now that https://gerrit.automotivelinux.org/gerrit/#/c/16769/ (master) and https://gerrit.automotivelinux.org/gerrit/#/c/16771/ (flounder) have been merged? 

Matt Porter 
August 21, 2018 at 5:30 PM

Hi

https://git.automotivelinux.org/apps/agl-service-bluetooth-pbap/tree/binding/bluetooth-pbap-binding.c is an example of the PBAP service monitoring bluetooth devices via the Bluetooth service. There's also an example in the telephony binding which is part of the phone app.

-Matt

Jonathan Aillet 
August 21, 2018 at 5:03 PM

Hi ,

As describe in the above JIRA ticket, we need to get (and to stayed informed of) the currently connected bluetooth device(s) to implement use of bluetooth in 4a.

Do you know if there is a way to register an application framework binder (4a in our case) to bluetooth service to stayed informed of the currently connected bluetooth devices ?

Thanks in advance for your response.

Regards.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority

Created August 21, 2018 at 4:47 PM
Updated October 9, 2018 at 2:53 PM
Resolved September 28, 2018 at 3:59 PM

Flag notifications