İlt: agl-4a-audio-service cannot parse the hal configurations

Gönderen: Oguzhan Mutlu
Gönderildi: 14 Mart 2019 Perşembe 11:35
Kime: Jonathan Aillet
Konu: Ynt: agl-4a-audio-service cannot parse the hal configurations

Hi again Jonathan,

Yesterday we finally found the way. Some parts of our hal configuration caused to fail the audio service. So we changed configurations with the "amixer controls" commands results. Upgrading "guppy" and these configurations solved the problem. But we still can't get sound from A2DP connection. I attached our current hal config and journalctl logs of the 4a audio service. Should we do anything else to get sound from bluetooth ?

Thank you for your interest,

Best Regards

Gönderen: Oguzhan Mutlu
Gönderildi: 13 Mart 2019 Çarşamba 14:09
Kime: Jonathan Aillet
Konu: Ynt: agl-4a-audio-service cannot parse the hal configurations

Hi Jonathan,

Thank you for the quick answer. I checked the "/usr/libexec/agl/4a-hal/etc" and yes our hal configuration was there so I don't think that service can't find the file. I also upgraded our AGL system to "guppy" release but result was the same. Also I executed the service with strace and I found that service trying to open "/etc/asound.conf"(exist but empty) and "/home/0/.asoundrc" (not exist) files, Should we configure these files also ? By the way I attached the logs which you wanted from me.

Kind Regards

Gönderen: Jonathan Aillet <jonathan.aillet@xxxxxxx>
Gönderildi: 13 Mart 2019 Çarşamba 13:23
Kime: Oguzhan Mutlu
Bilgi: automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx; Yiğit Çabaş
Konu: Re: agl-4a-audio-service cannot parse the hal configurations

Hello Oguzhan,

It seems that no hal json configuration file has been detected by
hal-manager at loading.

By default, all hal json configuration files are deployed in
'/usr/libexec/agl/4a-hal/etc.available' and needs to be moved in
'/usr/libexec/agl/4a-hal/etc' to be detected by hal-manager.
Could you check that your configuration file is deployed in
'/usr/libexec/agl/4a-hal/etc' ?

If not, can you move it into '/usr/libexec/agl/4a-hal/etc' and restart
4a audio service by using systemctl command :
- To get the exact name of the 4a audio service : systemctl | grep
service-audio-4a
- To restart the service : systemctl restart XXX (with XXX the name of
4a service)

If your configuration file is in the right directory and you still have
an error, I will need the results of these commands to help you :
- journalctl | grep afbd-agl-service-audio
- ls -lah /dev/snd/by-path
- aplay -l
- amixer -D hw:X controls (with X the id of your card result by aplay -l)

Regards,

Jonathan.

On 12/03/2019 14:38, Oguzhan Mutlu wrote:
> Hello,
>
> We are trying to adapt the AGL flounder distribution to our custom
> board and we decided to use 4a-framework for audio management. We
> built the system and there is no problem with that. Then we wrote our
> own specific hal configuration. But other agl services cannot get the
> right device uri. When we used afb-client-demo application to see what
> it returns, we are seeing the device uri section is empty. You can see
> our log and our hal config is in the attachments.
>
> Kind Regards
>
> Command:
>
> 4a-api hals
>
>
> Response:
>
> Detected systemd unit file!
> Port detected:
> ---
> 4a-hal-manager loaded {'verbose':false,'all':false}
> ---
> ON-REPLY 1:4a-hal-manager/loaded: OK
> {
> "response":[
> ],
> "jtype":"afb-reply",
> "request":{
> "status":"success",
> "info":"Requested data"
> }
> }
>
>
> Command:
>
> 4a-api roles
>
>
> Response:
>
> Detected systemd unit file!
> Port detected:
> ---
> ahl-4a get_roles
> ---
> ON-REPLY 1:ahl-4a/get_roles: OK
> {
> "response":[
> ],
> "jtype":"afb-reply",
> "request":{
> "status":"success"
> }
> }
>
> Client:
>
> afb-client-demo -H "localhost:1234/api?token=1234&uuid=magic"
>
>
> Command:
>
> ahl-4a multimedia { "action": "open" }
>
> Response:
>
> ON-REPLY 1:ahl-4a/multimedia: OK
> {
> "response":{
> "device_uri":""
> },
> "jtype":"afb-reply",
> "request":{
> "status":"success"
> }
> }
>
> Command:
> 4a-hal-manager loaded { "verbose": true }
>
> Response:
>
> ON-REPLY 1:4a-hal-manager/loaded: OK
> {
> "response":[
> ],
> "jtype":"afb-reply",
> "request":{
> "status":"success",
> "info":"Requested data"
> }
> }
>
>
>
> _______________________________________________
> automotive-discussions mailing list
> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions