Re: Ynt: agl-4a-audio-service cannot parse the hal configurations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I also realized that in your "resource" section,
you specify a microphone named "DAIICHI-CONFIG"
but I cannot see any declared microphone in the file, you do not have any "capture"' section
This might be the cause in your case, because the audio streams (a2p & sco) will not be created

Notice that on master branch, this is something that has been set as optional,
so that the absence of a microphone will let the sco listen, and a2dp playback work.
But unfortunately this is not available on guppy

So basically, you would have 2 choices
1) going to master
2) plug a USB mic and declare it in the capture section

Best regards
Thierry


On 03/14/2019 11:39 AM, Oguzhan Mutlu wrote:
Hi Jonathan,

Sorry I forgot to add to receivers the maillist so I am resending this mail.

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: 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



_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions

_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux