[Bluez-users] Bluez build problem

[Bluez-users] Bluez build problem

[Voni Hakau]

Hi all,

I'm cross compiling bluez-util to my platform, so I use something like
--prefix=/path/to/my/platform/root/filesystem/usr. Everything builds
and installs perfectly.

But, in my platform, bluez now thinks that all the files are located
in the path /path/to/my/platform/root/filesystem/usr (it is hard coded
in the binaries), which doesn't really exists on the platform - it was
just on my host, where I built my root fs for the platform. I need to
install everything on my host to that path, but on the platform I need
bluez to ignore it...

Any suggestions ? I can always use --prefix=/usr and then manually
copy all the files to /path/to/my/platform/root/filesystem/usr but
that is too hard... there must be a better way..

Thank you!
Voni

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Mumia W..]

On 06/13/2008 07:07 AM, Voni Hakau wrote:
> Hi all,
> 
> I'm cross compiling bluez-util to my platform, so I use something like
> --prefix=/path/to/my/platform/root/filesystem/usr. Everything builds
> and installs perfectly.
> 
> But, in my platform, bluez now thinks that all the files are located
> in the path /path/to/my/platform/root/filesystem/usr (it is hard coded
> in the binaries), which doesn't really exists on the platform - it was
> just on my host, where I built my root fs for the platform. I need to
> install everything on my host to that path, but on the platform I need
> bluez to ignore it...
> 
> Any suggestions ? I can always use --prefix=/usr and then manually
> copy all the files to /path/to/my/platform/root/filesystem/usr but
> that is too hard... there must be a better way..
> 
> Thank you!
> Voni
> 

Hi Voni.

Try to create a package instead. Use --prefix=/usr when you configure, 
but use DESTDIR=/tmp/buildplace when you install.

That should install the files to /tmp/buildplace. Use tar(1) to create a 
tarball of the files in /tmp/buildplace, or even better, use a packager 
for your preferred platform.

During configuration, your command line might look like this:

make --prefix=/usr

When you "install" the package, you'll use this command:

make install DESTDIR=/tmp/buildplace

Obviously, the files won't be installed to the right place. No problem, 
use tar(1).

cd /tmp/buildplace
tar czf /tmp/bluez-x.xx-i386.tar.gz *

Now you have a tarball that you can install wherever you wish, including 
the correct place for your platform, 
/path/to/my/platform/root/filesystem/usr.

Good luck.



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Voni Hakau]

On Fri, Jun 13, 2008 at 6:25 PM, Mumia W..
<paduille.4061.mumia.w+nospam@earthlink.net> wrote:
> On 06/13/2008 07:07 AM, Voni Hakau wrote:
>> I'm cross compiling bluez-util to my platform, so I use something like
>> --prefix=/path/to/my/platform/root/filesystem/usr.

> Try to create a package instead. Use --prefix=/usr when you configure,
> but use DESTDIR=/tmp/buildplace when you install.
>
> That should install the files to /tmp/buildplace. Use tar(1) to create a
> tarball of the files in /tmp/buildplace, or even better, use a packager
> for your preferred platform.
>
> During configuration, your command line might look like this:
>
> make --prefix=/usr
>
> When you "install" the package, you'll use this command:
>
> make install DESTDIR=/tmp/buildplace
>
> Obviously, the files won't be installed to the right place. No problem,
> use tar(1).
>
> cd /tmp/buildplace
> tar czf /tmp/bluez-x.xx-i386.tar.gz *
>
> Now you have a tarball that you can install wherever you wish, including
> the correct place for your platform,
> /path/to/my/platform/root/filesystem/usr.

Wow this is an amazing idea !! Thank you so much !!

I didn't know I can give --prefix to make. Or did you mean to ./configure ?

and I didn't know there is DESTDIR for make install. great great tip !!!

So I can just do make install DESTDIR with the prefix of my platform
root filesystem,
right ? I don't have to do the package, right ?

Thank you so much for this!! it's a really great idea..

Voni


>
> Good luck.
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Mumia W..]

On 06/16/2008 07:05 AM, Voni Hakau wrote:
> On Fri, Jun 13, 2008 at 6:25 PM, Mumia W..
> <paduille.4061.mumia.w+nospam@earthlink.net> wrote:
>> [...]
>> make --prefix=/usr
>>
>> When you "install" the package, you'll use this command:
>>
>> make install DESTDIR=/tmp/buildplace
>> [...]
> 
> Wow this is an amazing idea !! Thank you so much !!
> 
> I didn't know I can give --prefix to make. Or did you mean to ./configure ?
> 
> and I didn't know there is DESTDIR for make install. great great tip !!!
> 
> So I can just do make install DESTDIR with the prefix of my platform 
> root filesystem, 
> right ? I don't have to do the package, right ?
> 
> Thank you so much for this!! it's a really great idea..
> 
> Voni
> 

You're welcome Voni.

Yes, I meant "./configure --prefix=/usr"

But DESTDIR is used during "make install," and as you figured, you can 
use the platform's prefix.

Note that some programs don't use the DESTDIR variable, but almost all do.



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Voni Hakau]

Hi !

On Tue, Jun 17, 2008 at 1:41 AM, Mumia W..
<paduille.4061.mumia.w+nospam@earthlink.net> wrote:
> But DESTDIR is used during "make install," and as you figured, you can use
> the platform's prefix.
>
> Note that some programs don't use the DESTDIR variable, but almost all do.
>

I have successfully built expat,dbus and bluez-libs with this idea, but it seems
that bluez-utils doesn't like it..

Here is my configure command:
BLUEZ_CFLAGS=-I/path/to/my/platform/root/usr/include
BLUEZ_LIBS="-L/path/to/my/platform/root/usr/lib -lbluetooth"
DBUS_LIBS="-L/path/to/my/platform/root/usr/lib -ldbus-1"
DBUS_CFLAGS="-I/path/to/my/platform/root/usr/include/dbus-1.0
-I/path/to/my/platform/root/usr/include/dbus-1.0/include"
CPPFLAGS=-I/path/to/my/platform/root/usr/include
LDFLAGS=-L/path/to/my/platform/root/usr/lib ./configure --prefix=/usr
--host=arm-linux --mandir=/usr/share/man --sysconfdir=/etc
--localstatedir=/var --libexecdir=/lib

configure runs ok, and then make runs a little until it is doing this:
arm-linux-gcc -I/path/to/my/platform/root/usr/include
-I/path/to/my/platform/root/usr/include/dbus-1.0
-I/path/to/my/platform/root/usr/include/dbus-1.0/include -I../eglib
-I../gdbus -DPLUGINDIR=\"/usr/lib/bluetooth/plugins\" -Wall -O2
-D_FORTIFY_SOURCE=2 -o hcid main.o -rdynamic
-L/path/to/my/platform/root/usr/lib libhciserver.a
../sdpd/libsdpserver.a ../common/libhelper.a ../gdbus/.libs/libgdbus.a
../eglib/.libs/libeglib.a -ldl /usr/lib/libdbus-1.so
/path/to/my/platform/root/usr/lib/libbluetooth.so   -Wl,--rpath
-Wl,/path/to/my/platform/root/usr/lib -Wl,--rpath
-Wl,/path/to/my/platform/root/usr/lib
/usr/lib/libdbus-1.so: file not recognized: File format not recognized
collect2: ld returned 1 exit status

we can see that it tried to use my host libdbus-1.so, and it ignores
the DBUS_LIBS variable..

did i do something wrong ?
maybe it is a bug in bluez ? do you know how to fix it or bypass it ?
I tried to look in the Makefiles themselves to change this behavior
but didn't find it..

Thank you again for this wonderful assistance !
Voni

(btw, I even tried to set up
PKG_CONFIG_PATH=/path/to/my/platform/root/usr/lib/pkgconfig
but it didn't help...)

>
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Voni Hakau]

On Mon, Jun 30, 2008 at 3:06 PM, Voni Hakau <hakauvoni@gmail.com> wrote:
> Hi !
>
> On Tue, Jun 17, 2008 at 1:41 AM, Mumia W..
> <paduille.4061.mumia.w+nospam@earthlink.net> wrote:
>> But DESTDIR is used during "make install," and as you figured, you can use
>> the platform's prefix.
>>
>> Note that some programs don't use the DESTDIR variable, but almost all do.
>>
>
> I have successfully built expat,dbus and bluez-libs with this idea, but it seems
> that bluez-utils doesn't like it..
>
> Here is my configure command:
> BLUEZ_CFLAGS=-I/path/to/my/platform/root/usr/include
> BLUEZ_LIBS="-L/path/to/my/platform/root/usr/lib -lbluetooth"
> DBUS_LIBS="-L/path/to/my/platform/root/usr/lib -ldbus-1"
> DBUS_CFLAGS="-I/path/to/my/platform/root/usr/include/dbus-1.0
> -I/path/to/my/platform/root/usr/include/dbus-1.0/include"
> CPPFLAGS=-I/path/to/my/platform/root/usr/include
> LDFLAGS=-L/path/to/my/platform/root/usr/lib ./configure --prefix=/usr
> --host=arm-linux --mandir=/usr/share/man --sysconfdir=/etc
> --localstatedir=/var --libexecdir=/lib
>
> configure runs ok, and then make runs a little until it is doing this:
> arm-linux-gcc -I/path/to/my/platform/root/usr/include
> -I/path/to/my/platform/root/usr/include/dbus-1.0
> -I/path/to/my/platform/root/usr/include/dbus-1.0/include -I../eglib
> -I../gdbus -DPLUGINDIR=\"/usr/lib/bluetooth/plugins\" -Wall -O2
> -D_FORTIFY_SOURCE=2 -o hcid main.o -rdynamic
> -L/path/to/my/platform/root/usr/lib libhciserver.a
> ../sdpd/libsdpserver.a ../common/libhelper.a ../gdbus/.libs/libgdbus.a
> ../eglib/.libs/libeglib.a -ldl /usr/lib/libdbus-1.so
> /path/to/my/platform/root/usr/lib/libbluetooth.so   -Wl,--rpath
> -Wl,/path/to/my/platform/root/usr/lib -Wl,--rpath
> -Wl,/path/to/my/platform/root/usr/lib
> /usr/lib/libdbus-1.so: file not recognized: File format not recognized
> collect2: ld returned 1 exit status
>
> we can see that it tried to use my host libdbus-1.so, and it ignores
> the DBUS_LIBS variable..
>
> did i do something wrong ?
> maybe it is a bug in bluez ? do you know how to fix it or bypass it ?
> I tried to look in the Makefiles themselves to change this behavior
> but didn't find it..
>
> Thank you again for this wonderful assistance !
> Voni
>
> (btw, I even tried to set up
> PKG_CONFIG_PATH=/path/to/my/platform/root/usr/lib/pkgconfig
> but it didn't help...)

btw, I can also see another problem:

-DPLUGINDIR=\"/usr/lib/bluetooth/plugins\"

i don't know if it is severe..
>
>>
>>
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[jayjwa]

On Mon, 30 Jun 2008, Voni Hakau wrote:

-> > I have successfully built expat,dbus and bluez-libs with this idea, but it seems
-> > that bluez-utils doesn't like it..
-> >
-> > Here is my configure command:
-> > BLUEZ_CFLAGS=-I/path/to/my/platform/root/usr/include
-> > BLUEZ_LIBS="-L/path/to/my/platform/root/usr/lib -lbluetooth"
-> > DBUS_LIBS="-L/path/to/my/platform/root/usr/lib -ldbus-1"
-> > DBUS_CFLAGS="-I/path/to/my/platform/root/usr/include/dbus-1.0
-> > -I/path/to/my/platform/root/usr/include/dbus-1.0/include"
-> > CPPFLAGS=-I/path/to/my/platform/root/usr/include
-> > LDFLAGS=-L/path/to/my/platform/root/usr/lib ./configure --prefix=/usr
-> > --host=arm-linux --mandir=/usr/share/man --sysconfdir=/etc
-> > --localstatedir=/var --libexecdir=/lib
-> >
-> > configure runs ok, and then make runs a little until it is doing this:
-> > arm-linux-gcc -I/path/to/my/platform/root/usr/include
-> > -I/path/to/my/platform/root/usr/include/dbus-1.0
-> > -I/path/to/my/platform/root/usr/include/dbus-1.0/include -I../eglib
-> > -I../gdbus -DPLUGINDIR=\"/usr/lib/bluetooth/plugins\" -Wall -O2
-> > -D_FORTIFY_SOURCE=2 -o hcid main.o -rdynamic
-> > -L/path/to/my/platform/root/usr/lib libhciserver.a
-> > ../sdpd/libsdpserver.a ../common/libhelper.a ../gdbus/.libs/libgdbus.a
-> > ../eglib/.libs/libeglib.a -ldl /usr/lib/libdbus-1.so
-> > /path/to/my/platform/root/usr/lib/libbluetooth.so   -Wl,--rpath
-> > -Wl,/path/to/my/platform/root/usr/lib -Wl,--rpath
-> > -Wl,/path/to/my/platform/root/usr/lib
-> > /usr/lib/libdbus-1.so: file not recognized: File format not recognized
-> > collect2: ld returned 1 exit status
-> >
-> > we can see that it tried to use my host libdbus-1.so, and it ignores
-> > the DBUS_LIBS variable..
-> >
-> > did i do something wrong ?
-> > maybe it is a bug in bluez ? do you know how to fix it or bypass it ?
-> > I tried to look in the Makefiles themselves to change this behavior
-> > but didn't find it..

Perhaps the library is mentioned in a libtool (.la) file? You should be able 
to change the Makefiles if needed. Looking in 3.34 utils, I see your libdbus-1 
is mentioned in lots of places (found with `rgrep -r 'dbus-1' . | most ` while 
cwd was /tmp/bluez-utils-3.34):

./sdpd/Makefile:DBUS_CFLAGS = -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
./sdpd/Makefile:DBUS_LIBS = -ldbus-1
./hcid/Makefile:DBUS_CFLAGS = -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
./hcid/Makefile:DBUS_LIBS = -ldbus-1
./hcid/Makefile:#dbusdir = $(sysconfdir)/dbus-1/system.d
./hcid/Makefile:        $(top_builddir)/gdbus/libgdbus.la -Wl,--export-dynamic 
-lgmodule-2.0 -ldl -lglib-2.0   -lglib-2.0   -ldbus-1

You could try giving the full path names.

/path/to/my/platform/root/usr/lib/libdbus-1.so

DBUS_LIBS="/path/to/my/platform/root/usr/lib/libdbus-1.so "

If it still gives errors, start grepping through .la files to see if one is 
listing a -ldbus-1.


-> btw, I can also see another problem:
-> 
-> -DPLUGINDIR=\"/usr/lib/bluetooth/plugins\"
-> 
-> i don't know if it is severe..

I think yes, if that path doesn't exist on the target you are compiling for, 
because the daemons will need to load their plugins while they run on the 
target machine. If the target actually has a /usr/lib/bluetooth/plugins dir, 
then it should be OK.



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[Voni Hakau]

On Tue, Jul 1, 2008 at 6:09 PM, jayjwa <jayjwa@atr2.ath.cx> wrote:

> -> > we can see that it tried to use my host's libdbus-1.so, and it ignores
> -> > the DBUS_LIBS variable..

> Perhaps the library is mentioned in a libtool (.la) file? You should be able
> to change the Makefiles if needed. Looking in 3.34 utils, I see your libdbus-1
> is mentioned in lots of places (found with `rgrep -r 'dbus-1' . | most ` while
> cwd was /tmp/bluez-utils-3.34):

So you think too that there is a bug in bluez-utils ? That it ignores
the DBUS_LIBS environment variable ?

Thank you
Voni

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Bluez build problem

[jayjwa]

On Wed, 2 Jul 2008, Voni Hakau wrote:

-> > Perhaps the library is mentioned in a libtool (.la) file? You should be able
-> > to change the Makefiles if needed. Looking in 3.34 utils, I see your libdbus-1
-> > is mentioned in lots of places (found with `rgrep -r 'dbus-1' . | most ` while
-> > cwd was /tmp/bluez-utils-3.34):
-> 
-> So you think too that there is a bug in bluez-utils ? That it ignores
-> the DBUS_LIBS environment variable ?

Honestly, I'm not sure. Note that vars like DBUS_LIBS can be set in many 
places, and there is an order in which they take preference. You might be 
setting it, only to have to cancelled by a higher-preference assignment some 
place else. If that is how it is designed to be, it's not a bug; it's hard to 
tell without the actual problem in front of me. It built OK here, but then I'm 
not cross compiling, which is a bit trickier.


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] Error encounter when connecting A2DP following wiki instruction ! How to connect A2DP ?

[colorant]

Hi

    I try to connect earphone with A2DP on arm board .
    I follow the instruction from 
http://wiki.bluez.org/wiki/HOWTO/AudioDevices

    I encounter error while doing connect saying connect method does not 
exist !

    This is what I did :


~ # ps
  PID  Uid        VSZ Stat Command
  .....
  271 root       1576 SW< /sbin/udevd --daemon
  445 root       1884 SW  /bin/sh /etc/init.d/rc 2
  454 root       1964 SW  /bin/sh
  554 root            SW< [krfcommd]
  563 messagebus   1944 SW  /usr/bin/dbus-daemon --system --fork
  566 root       1416 SW  hciattach -s 921600 /dev/ttyS1 bcsp 921600
  573 root       1564 SW  ./sdpd
  575 root       2520 SW  hcid -d
  578 root       2444 SW  /usr/lib/bluetooth/bluetoothd-service-audio
  579 root       2412 SW  /usr/lib/bluetooth/bluetoothd-service-input
  619 root       1960 RW  ps

 ~ # dbus-send --system --print-reply --dest=org.bluez /org/bluez 
org.bluez.Manager.ActivateService string:audio
method return sender=:1.0 -> dest=:1.8
   string ":1.1"

~ # dbus-send --system --type=method_call --print-reply --dest=org.bluez 
/org/bluez org.bluez.Manager.ActivateService string:audio
method return sender=:1.0 -> dest=:1.9

~ # dbus-send --system --type=method_call --print-reply --dest=":1.1" 
/org/bluez/audio org.bluez.audio.Manager.CreateDevice 
string:00:02:5B:00:C1:A0
method return sender=:1.1 -> dest=:1.10
   string "/org/bluez/audio/device3"
~ #
~ # dbus-send --system --type=method_call --print-reply --dest=":1.1" 
"/org/bluez/audio/device3" org.bluez.audio.Sink.Connect
Error org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with 
signature "" on interface "org.bluez.audio.Sink" doesn't exist


So I have following questions :

1 . Anyone can help to point out what might be wrong in the above operation 
?

2. Actually I also try the method of modify the /etc/asound.conf to add the 
bluetooth and use aplay directly to play the music, that way also not 
working!

~ # cat /etc/asound.conf
pcm.bluetooth{
        type bluetooth
        device "00:02:5b:00:c1:a0"
        profile "auto"
}
~ # aplay -D bluetooth sample.wav
Segmentation fault
~ #

What might be the reason ? I can do aplay sample.wav to speaker. So alsa 
utils should be ok.

3. I notice that , on this howto, it do not mentioned the process of 
pairing, Shouldn't that be done in some other place ? How can I done that ? 
actually I have put in hcid.conf something like :

# HCId options
options {
    ....
        security auto;
        pairing multi;
        passkey "1234";
    ....
}

But this one do not work for dbus-send method , right ?

Thanks.

Raymond






-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

[Bluez-users] When Connect A2DP : Error 22 while configuring device

[colorant]

Hi

    I am try to connect A2DP with Bluez

    When useing Aplay to try it , I have following problems :

~ # aplay -D bluetooth demo.wav
ALSA lib pcm_bluetooth.c:1158:(bluetooth_cfg) Error 22 while configuring 
device
aplay: main:510: audio open error: Invalid argument

Can Someone point out what might be the reason ?

My config file is :

~ # cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#

# HCId options
options {
        # Automatically initialize new devices
        autoinit yes;

        security auto;

        pairing multi;

        offmode devdown;

        passkey "1234"; // I use my pc with usb dongle to provide the a2dp 
service, so this is set to1234 not 0000 or 8888 etc.
}

# Default settings for HCI devices
device {
        name "%h-%d";

        class 0xff0100;
        # Default packet type
        #pkt_type DH1,DM1,HV1;

        iscan disable; pscan enable;

        # Page timeout (10s)
        pageto 16384;

        # Discoverable timeout (0 == disabled)
        discovto 0;

        lm accept;

        lp rswitch,hold,sniff,park;
}


~ # cat /etc/bluetooth/audio.conf
# Configuration file for the audio service

# This section contains options which are not specific to any
# particular interface
[General]

# If we want to disable support for specific services
# Defaults to supporting all implemented services
# disable=Sink

# SCO routing. Either PCM or HCI (in which case audio is routed to/from 
ALSA)
# Defaults to HCI
SCORouting=PCM

# Headset interface specific options (i.e. options which affect how the 
audio
# service interacts with remote headset devices)
[Headset]

# Set to true to only support HSP
# Defaults to false
DisableHFP=true

# Just an example of potential config options for the other interfaces
#[A2DP]
SourceCount=2






-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users