Re: Bluez-users Digest, Vol 23, Issue 16

PIN introduction.
I would like to know HOW TO make a PIN handle for a Headset. I want this
handle not to need the X system (init 3 ) 
I have tryed the examples in the wiki (with python and so) but I don't
know hos to use them well, p.e., when do I have to execute the script?
It seems to do nothing.
I have change /etc/bluetooth/hcid.conf file in the Default PIN code, but
it also has no effect.
passkey "0000"

Any help, please?
Thanks in advance,
J



El jue, 27-03-2008 a las 22:54 -0700,
[email protected] escribió:
> Send Bluez-users mailing list submissions to
> 	[email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/bluez-users
> or, via email, send a message with subject or body 'help' to
> 	[email protected]
> 
> You can reach the person managing the list at
> 	[email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bluez-users digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: ACL connection handle (Brad Midgley)
>    2. Re: sdptool add service (Marcel Holtmann)
>    3. Re: ACL connection handle (Marcel Holtmann)
>    4. Could not find org.bluez interface (Peter Wurmsdobler)
>    5. Re: Could not find org.bluez interface (Marcel Holtmann)
>    6. Re: Could not find org.bluez interface (Peter Wurmsdobler)
>    7. Re: Recent bluez-gnome problems (Patryk Zawadzki)
>    8. Re: Recent bluez-gnome problems (Marcel Holtmann)
>    9. Re: ACL connection handle (Brad Midgley)
>   10. How to test sco over pcm in bluez? (dong yan)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 26 Mar 2008 21:43:30 -0600
> From: "Brad Midgley" <[email protected]>
> Subject: Re: [Bluez-users] ACL connection handle
> To: "BlueZ users" <[email protected]>
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Marcel
> 
> >  shouldn't be a big problem, but in general this belongs into the
> >  kernel since userspace is not dealing with ACL and SCO/eSCO connection
> >  handling.
> 
> I'll agree it would be cleaner in kernel. If it's to be handled in the
> kernel then I think we need some way like an ioctl so the userspace
> app can tell the kernel, before opening the sco connection, whether it
> should happen on pcm or hci. It would be handy to have a way for the
> app to ask the kernel where sco is going, in case the preferred
> transport wasn't available.
> 
> -- 
> Brad
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 27 Mar 2008 15:58:35 +0100
> From: Marcel Holtmann <[email protected]>
> Subject: Re: [Bluez-users] sdptool add service
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
> 
> Hi Chane,
> 
> > Do I need to add service manually using sdptool add? I got different
> > results using pand and rfcomm listen as servers.
> >
> > 1. >pand -s -M --role=NAP
> > After run the command above, no need to run "sdptool add NAP". The
> > service is already registered to sdpd.
> 
> the pand will register service records for you. Why are you not using  
> the network service?
> 
> > 2.>rfcomm listen 1 1
> > Need to run sdptool add SP to register SPP service to sdpd.
> 
> Yes, you need to register your own service record. However using the  
> serial service might be a better idea here.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 27 Mar 2008 16:10:32 +0100
> From: Marcel Holtmann <[email protected]>
> Subject: Re: [Bluez-users] ACL connection handle
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
> 
> Hi Brad,
> 
> >> shouldn't be a big problem, but in general this belongs into the
> >> kernel since userspace is not dealing with ACL and SCO/eSCO  
> >> connection
> >> handling.
> >
> > I'll agree it would be cleaner in kernel. If it's to be handled in the
> > kernel then I think we need some way like an ioctl so the userspace
> > app can tell the kernel, before opening the sco connection, whether it
> > should happen on pcm or hci. It would be handy to have a way for the
> > app to ask the kernel where sco is going, in case the preferred
> > transport wasn't available.
> 
> we would need to push the actual code into the drivers since the core  
> has to stay vendor free. For selecting the routing we could use a  
> socket option.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Thu, 27 Mar 2008 16:18:53 +0000
> From: Peter Wurmsdobler <[email protected]>
> Subject: [Bluez-users] Could not find org.bluez interface
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hello,
> 
> I am running a Qtopia 4.3 simulation on my Linux host. In addition, I 
> have a USB Bluetooth dongle plugged in and hciconfig tells me that 
> "hci0" is up and running. On the shell I can scan for devices, find some 
> and query the respective device info. All well so far.
> 
> Now, during the Qtopia startup, a bluetooth local device manager gets in 
> touch with the hci0 adatpter by creating an instance of a dbus interface 
> with "org.bluez", "/org/bluez", and "org.bluez.Manager" as parameters 
> (the redundancy in these values still astonishes me). Unfortunately, the 
> return is "Could not find org.bluez interface".
> 
> Could this be due to a security setting, or some other access problems?
> 
> Any hints are very much appreciated,
> peter
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Thu, 27 Mar 2008 17:24:48 +0100
> From: Marcel Holtmann <[email protected]>
> Subject: Re: [Bluez-users] Could not find org.bluez interface
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
> 
> Hi Peter,
> 
> > I am running a Qtopia 4.3 simulation on my Linux host. In addition, I
> > have a USB Bluetooth dongle plugged in and hciconfig tells me that
> > "hci0" is up and running. On the shell I can scan for devices, find  
> > some
> > and query the respective device info. All well so far.
> >
> > Now, during the Qtopia startup, a bluetooth local device manager  
> > gets in
> > touch with the hci0 adatpter by creating an instance of a dbus  
> > interface
> > with "org.bluez", "/org/bluez", and "org.bluez.Manager" as parameters
> > (the redundancy in these values still astonishes me). Unfortunately,  
> > the
> > return is "Could not find org.bluez interface".
> >
> > Could this be due to a security setting, or some other access  
> > problems?
> 
> might be, but I don't have enough information to tell you. Can you get  
> the full error message. Or test it with a simple Python script.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Thu, 27 Mar 2008 18:46:26 +0000
> From: Peter Wurmsdobler <[email protected]>
> Subject: Re: [Bluez-users] Could not find org.bluez interface
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hello Marcel,
> 
> > might be, but I don't have enough information to tell you. Can you get  
> > the full error message. Or test it with a simple Python script.
> Unfortunately I cannot really provide that much information, as the 
> single error message comes from QTopia. So it is not a bluez issue, but 
> I hope to get some hints.
> 
> Digging into the Qtopia 4.3 code, I see that the private part of the 
> constructor of QBluetoothLocalDeviceManager contains a new 
> QDBusInterface with the parameters mentioned before. Adding some log 
> messages reveals:
> 
> Bluetooth : new QDBusInterface("org.bluez", "/org/bluez", 
> "org.bluez.Manager", dbc);
> 
> Bluetooth : QDBusAbstractInterfacePrivate::QDBusAbstractInterfacePrivate 
> dynamic
> 
> Bluetooth : QDBusAbstractInterfacePrivate::QDBusAbstractInterfacePrivate 
> service =  "org.bluez"
> 
> Bluetooth : QDBusConnectionPrivate::getNameOwner:  service = "org.bluez"
> 
> Bluetooth : QDBusConnectionPrivate::getNameOwner:  message = 
> QDBusMessage(type=MethodCall, service="org.freedesktop.DBus", 
> path="/org/freedesktop/DBus", interface="org.freedesktop.DBus", 
> member="GetNameOwner", signature="", contents=(QString("org.bluez")) )
> 
> Bluetooth : QDBusAbstractInterfacePrivate::QDBusAbstractInterfacePrivate 
> currentOwner isEmpty, error = 
> "org.freedesktop.DBus.Error.NameHasNoOwner"
> Could not find org.bluez interface
> 
> Maybe you have an idea what is going wrong, and I will continue to dig 
> deeper.
> 
> Regards,
> peter
> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Thu, 27 Mar 2008 20:29:33 +0100
> From: "Patryk Zawadzki" <[email protected]>
> Subject: Re: [Bluez-users] Recent bluez-gnome problems
> To: "BlueZ users" <[email protected]>
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset=UTF-8
> 
> On Wed, Mar 26, 2008 at 5:40 PM, Marcel Holtmann <[email protected]> wrote:
> >  > yes, the options are there but there seems to be a problem with device
> >  > discovery somewhere in my setup. Is running hcid enough for the device
> >  > detection to work? It seems only the already paired devices show up
> >  > (it worked fine at least with bluez-gnome 0.15) so I assume it only
> >  > displays a memorized list of devices not doing discovery at all. How
> >  > do I debug it? I'm a programmer so if you point me to the right
> >  > internals I think I could fix the issues or at least provide you with
> >  > more info.
> >  That should have been fixed with the latest bluez-gnome version.
> 
> As mentioned eaerlier, we are already shipping bluez-gnome 0.25 and
> bluez-{libs,utils} 3.29
> 
> If it works for everyone else it has to be related to our setup so
> please point me in the right direction for debugging.
> 
> -- 
> Patryk Zawadzki
> PLD Linux Distribution
> 
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Fri, 28 Mar 2008 00:15:29 +0100
> From: Marcel Holtmann <[email protected]>
> Subject: Re: [Bluez-users] Recent bluez-gnome problems
> To: BlueZ users <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
> 
> Hi Patryk,
> 
> >>> yes, the options are there but there seems to be a problem with  
> >>> device
> >>> discovery somewhere in my setup. Is running hcid enough for the  
> >>> device
> >>> detection to work? It seems only the already paired devices show up
> >>> (it worked fine at least with bluez-gnome 0.15) so I assume it only
> >>> displays a memorized list of devices not doing discovery at all. How
> >>> do I debug it? I'm a programmer so if you point me to the right
> >>> internals I think I could fix the issues or at least provide you  
> >>> with
> >>> more info.
> >> That should have been fixed with the latest bluez-gnome version.
> >
> > As mentioned eaerlier, we are already shipping bluez-gnome 0.25 and
> > bluez-{libs,utils} 3.29
> >
> > If it works for everyone else it has to be related to our setup so
> > please point me in the right direction for debugging.
> 
> it is actually our fault within bluez-utils-3.29. We accidently  
> removed the device discover calls from the API. Expect a new release  
> soon.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> ------------------------------
> 
> Message: 9
> Date: Thu, 27 Mar 2008 21:05:24 -0600
> From: "Brad Midgley" <[email protected]>
> Subject: Re: [Bluez-users] ACL connection handle
> To: "BlueZ users" <[email protected]>
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Marcel
> 
> As a straw man for the sco routing, would the socket option look
> anything like this? I'm assuming that the driver would report a socket
> connect failure if you specify a route that the driver can't do.
> 
> --- sco.h.orig	2007-12-24 10:01:18.000000000 -0700
> +++ sco.h	2008-03-27 20:57:44.000000000 -0600
> @@ -45,8 +45,12 @@
> 
>  /* set/get sockopt defines */
>  #define SCO_OPTIONS	0x01
> +#define SCO_ANYROUTE	0x00
> +#define SCO_HCIROUTE	0x01
> +#define SCO_PCMROUTE	0x02
>  struct sco_options {
>  	uint16_t	mtu;
> +	uint8_t		route;
>  };
> 
>  #define SCO_CONNINFO	0x02
> 
> -- 
> Brad
> 
> 
> 
> ------------------------------
> 
> Message: 10
> Date: Fri, 28 Mar 2008 13:54:36 +0800
> From: "dong yan" <[email protected]>
> Subject: [Bluez-users] How to test sco over pcm in bluez?
> To: [email protected]
> Message-ID:
> 	<[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hi All:
>       I have bluez3.28 and kernel2.6.18 with eSCO patch and bluez
> 2.6.18mh8 patch in hand.I'm using ST's STLC2500 in the bluetooth
> module.Since stlc2500c support only sco over pcm , i have its pcm
> interface connected to cpu.Right now i've established an eSCO
> connection, the problem is i can't find proper means to test audio
> data transmit/receive based on sco over pcm.
>      I used "aplay -D plug:bluetooth *.wav" and something wrong
> happened,please refer to the log.
> 1.This is how my audio.conf is set:
> [General]
> Enable=Control
> # If we want to disable support for specific services
> # Defaults to supporting all implemented services
> #Disable=Headset
> Disable=
> Master=
> 
> # 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]
> HFP=true
> 
> # Set to true to only support HSP
> # Defaults to false
> DisableHFP=false
> 
> # HFP Gateway features
> # Defaults to false
> 3WayCalling=true
> EchoCancelNoiseCancel=true
> VoiceRecognition=true
> InBandRingtone=true
> VoiceTags=true
> RejectingCalls=true
> EnhancedCallStatus=true
> EnhancedCallControl=true
> ExtendedErrorResultCodes=true
> 
> # Just an example of potential config options for the other interfaces
> [A2DP]
> SourceCount=2
> SBCSources=1
> MPEG12Sources=0
> SBCSinks=
> MPEG12Sinks=
> 
> 2.Settings in asound.conf:
>  pcm.headset {
> type bluetooth
> }
> ctl.headset {
> type bluetooth
> }
> pcm.bluetooth {
> type bluetooth
> device 00:18:13:E7:B8:D6
> profile voice
> }
> 
> 3.The log when tried to play music in bluetooth headset:
> $ /aplay -D plug:bluetooth 1.wav
> audio[192]: Found Headset record
> audio[192]: Discovered Headset service on RFCOMM channel 1
> audio[192]: Found Hansfree record
> audio[192]: Discovered Handsfree service on RFCOMM channel 2
> audio[192]: Found Audio Sink
> audio[192]: Found AV Remote
> audio[192]: Found AV Target
> audio[192]: Selecting default device
> audio[192]: Audio API: sending BT_GETCAPABILITIES_RSP
> Playing WAVE '/tmp1/1.wav' : Signed 16 bit Little Endian, Rate 44100 Hz,
> Stereo
> audio[192]: Audio API: received BT_SETCONFIGURATION_REQ
> audio[192]: config sco - device = 00:18:13:E7:B8:D6 access_mode = 2
> audio[192]: /org/bluez/audio/device0: Connecting to 00:18:13:E7:B8:D6
> channel 2
> audio[192]: State changed /org/bluez/audio/device0:
> HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
> hcid[173]: link_key_request (sba=00:80:E1:00:AB:BA, dba=00:18:13:E7:B8:D6)
> hcid[173]: pin_code_request (sba=00:80:E1:00:AB:BA, dba=00:18:13:E7:B8:D6)
> hcid[173]: Calling PasskeyAgent.Request: name=:1.1,
> path=/org/bluez/passkey_agent_179
> Passkey request for device 00:18:13:E7:B8:D6
> hcid[173]: link_key_notify (sba=00:80:E1:00:AB:BA, dba=00:18:13:E7:B8:D6)
> audio[192]: /org/bluez/audio/device0: Connected to 00:18:13:E7:B8:D6
> audio[192]: Received AT+BRSF=127
> audio[192]: Received AT+CIND=?
> audio[192]: Received AT+CIND?
> audio[192]: Received AT+CMER=3,0,0,1
> audio[192]: Received AT+CHLD=?
> audio[192]: HFP Service Level Connection established
> audio[192]: State changed  KERNEL:sco_connect(): type=2
> /org/bluez/audio/device0:
> HEADSET_STATE_CONNECT_IN_PROGRESh4_check_data_len: Data length is too large
> S -> HEADSET_STATE_CONNECTED
> audio[192]: State changed /org/bluez/audio/device0: HEADSET_STATE_CONNECTED
> -> HEADSET_STATE_PLAY_IN_PROGRESS
> h4_recv: Unknown HCI packet type 00
> audio[192]: connect(): Connection timed out (110)
> audio[192]: config failed
> audio[192]: Audio API: sending BT_SETCONFIGURATION_RSP
> audio[192]: State changed /org/bluez/audio/device0:
> HEADSET_STATE_PLAY_IN_PROGRESS -> HEADSET_STATE_CONNECTED
> ALSA lib pcm_bluetooth.c:460:(bluetooth_hsp_hw_params) BT_SETCONFIGURATION
> failed : Input/output error(5)
> aplay: set_params:979: Unable to install hw params:
> ACCESS:  RW_INTERLEAVED
> FORMAT:  S16_LE
> SUBFORMAT:  STD
> SAMPLE_BITS: 16
> FRAME_BITS: 32
> CHANNELS: 2
> RATE: 44100
> PERIOD_TIME: 125000
> PERIOD_SIZE: (5512 5513)
> PERIOD_BYTES: (22048 22052)
> PERIODS: (3 5)
> BUFFER_TIME: 500000
> BUFFER_SIZE: 22050
> BUFFER_BYTES: 88200
> TICK_TIME: 0
> audio[192]: Unix client disconnected (fd=9)
> l2cap_recv_acldata: Unexpected continuation frame (len 258)
> / $ audio[192]: Received AT+CLAN?
> audio[192]: Badly formated or unrecognized command: AT+CLAN?
> audio[192]: Received AT*EIPS=2,1
> audio[192]: Badly formated or unrecognized command: AT*EIPS=2,1
> audio[192]: Received AT+COLP=1
> audio[192]: Badly formated or unrecognized command: AT+COLP=1
> 
> 
> 
> Can anybody tell me what's wrong with my log?
> Or how to test audio transfer when using the sco over pcm route in hsp/hfp?
> 
> 
> 
> ------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> 
> ------------------------------
> 
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
> 
> 
> End of Bluez-users Digest, Vol 23, Issue 16
> *******************************************


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users