Hi Pali, > This utility is very useful for determining which A2DP codecs are supported > by remote side. So install it to system as part of bluez package. > --- > Makefile.tools | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Makefile.tools b/Makefile.tools > index 9b9236609..d52721612 100644 > --- a/Makefile.tools > +++ b/Makefile.tools > @@ -176,9 +176,9 @@ endif > if TOOLS > bin_PROGRAMS += tools/rctest tools/l2test tools/l2ping tools/bccmd \ > tools/bluemoon tools/hex2hcd tools/mpris-proxy \ > - tools/btattach > + tools/btattach tools/avinfo > > -noinst_PROGRAMS += tools/bdaddr tools/avinfo tools/avtest \ > +noinst_PROGRAMS += tools/bdaddr tools/avtest \ > tools/scotest tools/amptest tools/hwdb \ > tools/hcieventmask tools/hcisecfilter \ > tools/btinfo tools/btconfig \ I had no intention to install that tool since it is too limited and makes too many assumption. In addition it has a bad name with no Bluetooth prefix. If we think it is useful to have such a test utility, then we need to clean this up first and put this into a larger btinfo work to gather appropriate information from a remote device for debug purposes. Regards Marcel
