Send automotive-discussions mailing
list submissions to
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
or, via email, send a message with subject or body 'help'
to
automotive-discussions-request@xxxxxxxxxxxxxxxxxxxxxxxxx
You can reach the person managing the list at
automotive-discussions-owner@xxxxxxxxxxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of automotive-discussions digest..."
Today's Topics:
1. Re: Ynt: agl-4a-audio-service cannot parse the hal
configurations (Thierry Bultel)
2. Re: Ynt: agl-4a-audio-service cannot parse the hal
configurations (Thierry Bultel)
----------------------------------------------------------------------
Message: 1
Date: Thu, 14 Mar 2019 11:51:58 +0100
From: Thierry Bultel
<thierry.bultel@xxxxxxx>
To:
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Ynt: agl-4a-audio-service
cannot parse
the hal configurations
Message-ID:
<467e8246-5c97-7fc6-b794-676af7eb6c43@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-3";
Format="flowed"
Hi Oguszan,
Unfortunately, the log does not have enough verbosity to
find out the
reason why the A2DP does not work
Would you mind changing this on your board, restart the
service, and
send the bigger log ?
In
/var/local/lib/systemd/system/afm-service-agl-service-audio-4a--1.0-xxx--main@.service
(the xxx depends on the version you are using),
please add a third
"--verbose \" line in the ExecStart
eg:
ExecStart=/usr/bin/4a_wait_bt.sh /usr/bin/afb-daemon
--ldpath=/usr/libexec/agl/4a-alsa-core/lib:/usr/libexec/agl/4a-hal/lib:/usr/libexec/agl/smixer/lib
\
??? --name
afbd-4a-service-audio-4a@1.0-b2503b9-dirty \
--rootdir=/var/local/lib/afm/applications/agl-service-audio-4a/1.0-b2503b9-dirty
\
??? --workdir=/home/%i/app-data/agl-service-audio-4a \
??? --verbose \
??? --verbose \
*??? --verbose \*
??? --monitoring \
Thanks, looking forward to reading the verbose output
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20190314/0f734091/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 14 Mar 2019 12:01:06 +0100
From: Thierry Bultel
<thierry.bultel@xxxxxxx>
To:
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Ynt: agl-4a-audio-service
cannot parse
the hal configurations
Message-ID:
<7b3aedad-0b0a-fd3e-86dd-79e30909bc03@xxxxxxx>
Content-Type: text/plain; charset="iso-8859-3";
Format="flowed"
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/automotive-discussions/attachments/20190314/6efb8d39/attachment.html>
------------------------------
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
End of automotive-discussions Digest, Vol 74, Issue 12
******************************************************
