bluez5 pairing devices

bluez5 pairing devices

[Ssagarr Patil]

Hi Folks,

I am very new to bluetooth, so sorry for a novice query.

1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or should I use bluez4 ?
2: With bluez5 I am able to scan devices and also see the device on other device but I am not able to pair them 
    Is there some sort of deamon required to pair them ?

Regards,
--Sagar

 		 	   		  

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

> I am very new to bluetooth, so sorry for a novice query.
> 
> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or should I use bluez4 ?
> 2: With bluez5 I am able to scan devices and also see the device on other device but I am not able to pair them 
>     Is there some sort of deamon required to pair them ?

BlueZ 5 requires a Bluetooth subsystem with management API support. So at least kernel 3.4 or you have to use Linux backports to at least bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard of success from people doing that, but I have not personally done that.

Regards

Marcel

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel=2C=0A=
=0A=
Thanks for the response.=0A=
=0A=
>> I am very new to bluetooth=2C so sorry for a novice query.=0A=
>>=0A=
>> 1: I am using 2.6.37 Linux kernel=2C can bluez5 stack be used on this or=
 should I use bluez4 ?=0A=
>> 2: With bluez5 I am able to scan devices and also see the device on othe=
r device but I am not able to pair them=0A=
>> Is there some sort of deamon required to pair them ?=0A=
>=0A=
> BlueZ 5 requires a Bluetooth subsystem with management API support. So at=
 least kernel 3.4 or you have to use Linux backports to at least bring the =
Bluetooth subsystem to your 2.6.37 kernel. And I have heard of success from=
 people doing that=2C but I have not personally done that.=0A=
>=0A=
Probably that would take me more time in back porting. In case of 2.6.37 wh=
at version of bluez4 would be best ?=0A=
=0A=
Regards=2C=0A=
Sagar=0A=
 		 	   		  =

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

>>> I am very new to bluetooth, so sorry for a novice query.
>>> 
>>> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or should I use bluez4 ?
>>> 2: With bluez5 I am able to scan devices and also see the device on other device but I am not able to pair them
>>> Is there some sort of deamon required to pair them ?
>> 
>> BlueZ 5 requires a Bluetooth subsystem with management API support. So at least kernel 3.4 or you have to use Linux backports to at least bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard of success from people doing that, but I have not personally done that.
>> 
> Probably that would take me more time in back porting. In case of 2.6.37 what version of bluez4 would be best ?

the Linux backports project does that automatically. Give it a try. You are not the person with this problem, but it is not something were BlueZ upstream will be of much assistance.

I think that our android/README has even some instructions on how to get that started for an Android build. You might be able to adapt that quickly.

Just remember that BlueZ 4 is no longer maintained. So with any problems you encounter, you are on your own.

Regards

Marcel

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel,

Thanks for the response.

>>>> I am very new to bluetooth, so sorry for a novice query.
>>>>
>>>> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or should I use bluez4 ?
>>>> 2: With bluez5 I am able to scan devices and also see the device on other device but I am not able to pair them
>>>> Is there some sort of deamon required to pair them ?
>>>
>>> BlueZ 5 requires a Bluetooth subsystem with management API support. So at least kernel 3.4 or you have to use Linux backports to at least bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard of success from people doing that, but I have not personally done that.
>>>
>> Probably that would take me more time in back porting. In case of 2.6.37 what version of bluez4 would be best ?
>
> the Linux backports project does that automatically. Give it a try. You are not the person with this problem, but it is not something were BlueZ upstream will be of much assistance.
>
Any quick pointers on doing this ?

> I think that our android/README has even some instructions on how to get that started for an Android build. You might be able to adapt that quickly.
>
I am more interested in Linux.

Regards,
Sagar
 		 	   		  

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

>>>>> I am very new to bluetooth, so sorry for a novice query.
>>>>> 
>>>>> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or should I use bluez4 ?
>>>>> 2: With bluez5 I am able to scan devices and also see the device on other device but I am not able to pair them
>>>>> Is there some sort of deamon required to pair them ?
>>>> 
>>>> BlueZ 5 requires a Bluetooth subsystem with management API support. So at least kernel 3.4 or you have to use Linux backports to at least bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard of success from people doing that, but I have not personally done that.
>>>> 
>>> Probably that would take me more time in back porting. In case of 2.6.37 what version of bluez4 would be best ?
>> 
>> the Linux backports project does that automatically. Give it a try. You are not the person with this problem, but it is not something were BlueZ upstream will be of much assistance.
>> 
> Any quick pointers on doing this ?

https://backports.wiki.kernel.org/

>> I think that our android/README has even some instructions on how to get that started for an Android build. You might be able to adapt that quickly.
>> 
> I am more interested in Linux.

It is still running the same Linux kernel. That is why I said, you might be able to adapt that to your needs.

Regards

Marcel

Re: bluez5 pairing devices

[Szymon Janc]

Hi,

On Tuesday 17 of March 2015 09:42:44 Marcel Holtmann wrote:
> Hi Sagar,
> 
> >>>>> I am very new to bluetooth, so sorry for a novice query.
> >>>>> 
> >>>>> 1: I am using 2.6.37 Linux kernel, can bluez5 stack be used on this or
> >>>>> should I use bluez4 ? 2: With bluez5 I am able to scan devices and
> >>>>> also see the device on other device but I am not able to pair them Is
> >>>>> there some sort of deamon required to pair them ?
> >>>> 
> >>>> BlueZ 5 requires a Bluetooth subsystem with management API support. So
> >>>> at least kernel 3.4 or you have to use Linux backports to at least
> >>>> bring the Bluetooth subsystem to your 2.6.37 kernel. And I have heard
> >>>> of success from people doing that, but I have not personally done
> >>>> that.>>> 
> >>> Probably that would take me more time in back porting. In case of 2.6.37
> >>> what version of bluez4 would be best ?>> 
> >> the Linux backports project does that automatically. Give it a try. You
> >> are not the person with this problem, but it is not something were BlueZ
> >> upstream will be of much assistance.> 
> > Any quick pointers on doing this ?
> 
> https://backports.wiki.kernel.org/
> 
> >> I think that our android/README has even some instructions on how to get
> >> that started for an Android build. You might be able to adapt that
> >> quickly.> 
> > I am more interested in Linux.
> 
> It is still running the same Linux kernel. That is why I said, you might be
> able to adapt that to your needs.

Just an note that recent backports dropped support for kernels older than 3.0.
So some older release might be needed for 2.6.37.

-- 
BR
Szymon Janc

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Szymon/Marcel,

> On Tuesday 17 of March 2015 09:42:44 Marcel Holtmann wrote:
>> Hi Sagar,
>>
[Snip]
> Just an note that recent backports dropped support for kernels older than 3.0.
> So some older release might be needed for 2.6.37.
>
I have managed to backport it thanks.


But bluetoothctl doesnt detect it, It says the following:

# bluetoothctl 
[bluetooth]# power on
No default controller available
[bluetooth]# 

Here is output of hciconfig:

$ hciconfig  -a
hci0:   Type: BR/EDR  Bus: UART
        BD Address: 34:B1:F7:E2:DE:CB  ACL MTU: 1021:6  SCO MTU: 180:4
        UP RUNNING PSCAN ISCAN 
        RX bytes:12525 acl:56 sco:0 events:262 errors:0
        TX bytes:2948 acl:52 sco:0 commands:108 errors:0
        Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF 
        Link mode: SLAVE ACCEPT 
        Name: 'bt_hw'
        Class: 0x001f00
        Service Classes: Unspecified
        Device Class: Invalid Device Class!
        HCI Version: 4.1 (0x7)  Revision: 0x0
        LMP Version: 4.1 (0x7)  Subversion: 0xac7c
        Manufacturer: Texas Instruments Inc. (13)

# 

And I scan devices using hcitool as well.

Any pointers why bluetoothctl fails ?

Regards,
Sagar

 		 	   		  

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

>> Just an note that recent backports dropped support for kernels older than 3.0.
>> So some older release might be needed for 2.6.37.
>> 
> I have managed to backport it thanks.
> 
> 
> But bluetoothctl doesnt detect it, It says the following:
> 
> # bluetoothctl 
> [bluetooth]# power on
> No default controller available
> [bluetooth]# 

you need a running bluetoothd for bluetoothctl.

> Here is output of hciconfig:
> 
> $ hciconfig  -a
> hci0:   Type: BR/EDR  Bus: UART
>         BD Address: 34:B1:F7:E2:DE:CB  ACL MTU: 1021:6  SCO MTU: 180:4
>         UP RUNNING PSCAN ISCAN 
>         RX bytes:12525 acl:56 sco:0 events:262 errors:0
>         TX bytes:2948 acl:52 sco:0 commands:108 errors:0
>         Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
>         Link policy: RSWITCH HOLD SNIFF 
>         Link mode: SLAVE ACCEPT 
>         Name: 'bt_hw'
>         Class: 0x001f00
>         Service Classes: Unspecified
>         Device Class: Invalid Device Class!
>         HCI Version: 4.1 (0x7)  Revision: 0x0
>         LMP Version: 4.1 (0x7)  Subversion: 0xac7c
>         Manufacturer: Texas Instruments Inc. (13)
> 
> # 

Just our of curiosity, does this chip support BR/EDR Secure Connections? You might need to check with hciconfig hci0 features or run btmon to see the fully decoded list.

> And I scan devices using hcitool as well.
> 
> Any pointers why bluetoothctl fails ?

btmgmt, hciconfig etc. operate on the kernel level interfaces. Which you normally use for testing or development. For everything else, run bluetoothd and then bluetoothctl will work.

Regards

Marcel

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel,

> Subject: Re: bluez5 pairing devices
> From: marcel@holtmann.org
> Date: Wed, 18 Mar 2015 09:28:55 -0700
> CC: szymon.janc@tieto.com; linux-bluetooth@vger.kernel.org
> To: hugarsagar@outlook.com
>
> Hi Sagar,
>
>>> Just an note that recent backports dropped support for kernels older than 3.0.
>>> So some older release might be needed for 2.6.37.
>>>
>> I have managed to backport it thanks.
>>
>>
>> But bluetoothctl doesnt detect it, It says the following:
>>
>> # bluetoothctl
>> [bluetooth]# power on
>> No default controller available
>> [bluetooth]#
>
> you need a running bluetoothd for bluetoothctl.
>
Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.

>> Here is output of hciconfig:
>>
>> $ hciconfig -a
>> hci0: Type: BR/EDR Bus: UART
>> BD Address: 34:B1:F7:E2:DE:CB ACL MTU: 1021:6 SCO MTU: 180:4
>> UP RUNNING PSCAN ISCAN
>> RX bytes:12525 acl:56 sco:0 events:262 errors:0
>> TX bytes:2948 acl:52 sco:0 commands:108 errors:0
>> Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy: RSWITCH HOLD SNIFF
>> Link mode: SLAVE ACCEPT
>> Name: 'bt_hw'
>> Class: 0x001f00
>> Service Classes: Unspecified
>> Device Class: Invalid Device Class!
>> HCI Version: 4.1 (0x7) Revision: 0x0
>> LMP Version: 4.1 (0x7) Subversion: 0xac7c
>> Manufacturer: Texas Instruments Inc. (13)
>>
>> #
>
> Just our of curiosity, does this chip support BR/EDR Secure Connections? You might need to check with hciconfig hci0 features or run btmon to see the fully decoded list.
>
>From the logs seems it does support:

Bluetooth monitor ver 5.29
= New Index: 34:B1:F7:E2:DE:CB (BR/EDR,UART,hci0)               [hci0] 0.041017

Regards,
Sagar

 		 	   		  

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel,

>>> # bluetoothctl
>>> [bluetooth]# power on
>>> No default controller available
>>> [bluetooth]#
>>
>> you need a running bluetoothd for bluetoothctl.
>>
> Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.
>
A further debug showed me this:

Mar 19 12:51:51 evm systemd[1]: Starting Bluetooth service...
Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth daemon 5.29
Mar 19 12:51:51 evm systemd[1]: Started Bluetooth service.
Mar 19 12:51:51 evm bluetoothd[189]: Starting SDP server
Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth management interface 1.1 initialized
Mar 19 12:51:51 evm bluetoothd[189]: Failed to read info for index 54749: Invalid Index (0x11)
Mar 19 12:51:51 evm connmand[149]: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist

org.bluez.Manager service is missing in from services shouldnt it come from bluez5 ?

Regards,
Sagar

>>> Here is output of hciconfig:
>>>
>>> $ hciconfig -a
>>> hci0: Type: BR/EDR Bus: UART
>>> BD Address: 34:B1:F7:E2:DE:CB ACL MTU: 1021:6 SCO MTU: 180:4
>>> UP RUNNING PSCAN ISCAN
>>> RX bytes:12525 acl:56 sco:0 events:262 errors:0
>>> TX bytes:2948 acl:52 sco:0 commands:108 errors:0
>>> Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
>>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>>> Link policy: RSWITCH HOLD SNIFF
>>> Link mode: SLAVE ACCEPT
>>> Name: 'bt_hw'
>>> Class: 0x001f00
>>> Service Classes: Unspecified
>>> Device Class: Invalid Device Class!
>>> HCI Version: 4.1 (0x7) Revision: 0x0
>>> LMP Version: 4.1 (0x7) Subversion: 0xac7c
>>> Manufacturer: Texas Instruments Inc. (13)
>>>
>>> #
>>
>> Just our of curiosity, does this chip support BR/EDR Secure Connections? You might need to check with hciconfig hci0 features or run btmon to see the fully decoded list.
>>
> From the logs seems it does support:
>
> Bluetooth monitor ver 5.29
> = New Index: 34:B1:F7:E2:DE:CB (BR/EDR,UART,hci0)               [hci0] 0.041017
>
> Regards,
> Sagar
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
 		 	   		  

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

>>>> # bluetoothctl
>>>> [bluetooth]# power on
>>>> No default controller available
>>>> [bluetooth]#
>>> 
>>> you need a running bluetoothd for bluetoothctl.
>>> 
>> Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.
>> 
> A further debug showed me this:
> 
> Mar 19 12:51:51 evm systemd[1]: Starting Bluetooth service...
> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth daemon 5.29
> Mar 19 12:51:51 evm systemd[1]: Started Bluetooth service.
> Mar 19 12:51:51 evm bluetoothd[189]: Starting SDP server
> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth management interface 1.1 initialized
> Mar 19 12:51:51 evm bluetoothd[189]: Failed to read info for index 54749: Invalid Index (0x11)

this looks like an endian bug to me. That is no a valid index. Unless you really added 54749 Bluetooth dongles on your system. So something is screwed up that that needs to be investigated.

> Mar 19 12:51:51 evm connmand[149]: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist
> 
> org.bluez.Manager service is missing in from services shouldnt it come from bluez5 ?

It uses D-Bus Object Manager to retrieve all objects.

Regards

Marcel

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel,

----------------------------------------
> Subject: Re: bluez5 pairing devices
> From: marcel@holtmann.org
> Date: Thu, 19 Mar 2015 07:08:21 -0700
> CC: szymon.janc@tieto.com; linux-bluetooth@vger.kernel.org
> To: hugarsagar@outlook.com
>
> Hi Sagar,
>
>>>>> # bluetoothctl
>>>>> [bluetooth]# power on
>>>>> No default controller available
>>>>> [bluetooth]#
>>>>
>>>> you need a running bluetoothd for bluetoothctl.
>>>>
>>> Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.
>>>
>> A further debug showed me this:
>>
>> Mar 19 12:51:51 evm systemd[1]: Starting Bluetooth service...
>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth daemon 5.29
>> Mar 19 12:51:51 evm systemd[1]: Started Bluetooth service.
>> Mar 19 12:51:51 evm bluetoothd[189]: Starting SDP server
>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth management interface 1.1 initialized
>> Mar 19 12:51:51 evm bluetoothd[189]: Failed to read info for index 54749: Invalid Index (0x11)
>
> this looks like an endian bug to me. That is no a valid index. Unless you really added 54749 Bluetooth dongles on your system. So something is screwed up that that needs to be investigated.
>
Not sure what’s wrong here! because I have ported v3.5 bluetooth stack.

Is it true we cannot pair LE devices in bluez4.101 ?


Regards
Sagar
 		 	   		  

Re: bluez5 pairing devices

[Marcel Holtmann]

Hi Sagar,

>>>>>> # bluetoothctl
>>>>>> [bluetooth]# power on
>>>>>> No default controller available
>>>>>> [bluetooth]#
>>>>> 
>>>>> you need a running bluetoothd for bluetoothctl.
>>>>> 
>>>> Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.
>>>> 
>>> A further debug showed me this:
>>> 
>>> Mar 19 12:51:51 evm systemd[1]: Starting Bluetooth service...
>>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth daemon 5.29
>>> Mar 19 12:51:51 evm systemd[1]: Started Bluetooth service.
>>> Mar 19 12:51:51 evm bluetoothd[189]: Starting SDP server
>>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth management interface 1.1 initialized
>>> Mar 19 12:51:51 evm bluetoothd[189]: Failed to read info for index 54749: Invalid Index (0x11)
>> 
>> this looks like an endian bug to me. That is no a valid index. Unless you really added 54749 Bluetooth dongles on your system. So something is screwed up that that needs to be investigated.
>> 
> Not sure what’s wrong here! because I have ported v3.5 bluetooth stack.

maybe the backport has some issues that got fixed. The latest stable kernel is 3.19.2.

> Is it true we cannot pair LE devices in bluez4.101 ?

LE support with BlueZ 4 is limited to not really working at all. So if want to work on LE, then you need mgmt API support and a recent Bluetooth subsystem and BlueZ 5.

Regards

Marcel

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel=2C=0A=
=0A=
>=0A=
>>>>>>> # bluetoothctl=0A=
>>>>>>> [bluetooth]# power on=0A=
>>>>>>> No default controller available=0A=
>>>>>>> [bluetooth]#=0A=
>>>>>>=0A=
>>>>>> you need a running bluetoothd for bluetoothctl.=0A=
>>>>>>=0A=
>>>>> Isnt bluetoothd part of bluez5 stack ? as I am not able to see it.=0A=
>>>>>=0A=
>>>> A further debug showed me this:=0A=
>>>>=0A=
>>>> Mar 19 12:51:51 evm systemd[1]: Starting Bluetooth service...=0A=
>>>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth daemon 5.29=0A=
>>>> Mar 19 12:51:51 evm systemd[1]: Started Bluetooth service.=0A=
>>>> Mar 19 12:51:51 evm bluetoothd[189]: Starting SDP server=0A=
>>>> Mar 19 12:51:51 evm bluetoothd[189]: Bluetooth management interface 1.=
1 initialized=0A=
>>>> Mar 19 12:51:51 evm bluetoothd[189]: Failed to read info for index 547=
49: Invalid Index (0x11)=0A=
>>>=0A=
>>> this looks like an endian bug to me. That is no a valid index. Unless y=
ou really added 54749 Bluetooth dongles on your system. So something is scr=
ewed up that that needs to be investigated.=0A=
>>>=0A=
>> Not sure what=92s wrong here! because I have ported v3.5 bluetooth stack=
.=0A=
>=0A=
> maybe the backport has some issues that got fixed. The latest stable kern=
el is 3.19.2.=0A=
>=0A=
>> Is it true we cannot pair LE devices in bluez4.101 ?=0A=
>=0A=
> LE support with BlueZ 4 is limited to not really working at all. So if wa=
nt to work on LE=2C then you need mgmt API support and a recent Bluetooth s=
ubsystem and BlueZ 5.=0A=
>=0A=
With gattool and hcitool lecc I am able to pair.=A0 But I am not sure How t=
o get the data from le device ?=0A=
Any pointers on doing this ?=0A=
=0A=
Thanks for your support.=0A=
=0A=
Regards=2C=0A=
Sagar=0A=
 		 	   		  =

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel=2C=0A=
=0A=
>>=0A=
>> maybe the backport has some issues that got fixed. The latest stable ker=
nel is 3.19.2.=0A=
>>=0A=
>>> Is it true we cannot pair LE devices in bluez4.101 ?=0A=
>>=0A=
>> LE support with BlueZ 4 is limited to not really working at all. So if w=
ant to work on LE=2C then you need mgmt API support and a recent Bluetooth =
subsystem and BlueZ 5.=0A=
>>=0A=
> With gattool and hcitool lecc I am able to pair.  But I am not sure How t=
o get the data from le device ?=0A=
> Any pointers on doing this ?=0A=
>=0A=
$ # hcitool=A0 lecc 54:4A:16:5E:1B:9D=0A=
Connection handle 1025=0A=
=0A=
Does it create a fd ? so that me C app can access ?=0A=
=0A=
# gatttool=A0 -b 54:4A:16:5E:1B:9D -I=0A=
[=A0=A0 ][54:4A:16:5E:1B:9D][LE]> connect=0A=
[CON][54:4A:16:5E:1B:9D][LE]> char-desc=0A=
[CON][54:4A:16:5E:1B:9D][LE]> =0A=
handle: 0x0001=2C uuid: 2800=0A=
handle: 0x0002=2C uuid: 2803=0A=
handle: 0x0003=2C uuid: 2a00=0A=
handle: 0x0004=2C uuid: 2803=0A=
handle: 0x0005=2C uuid: 2a01=0A=
=0A=
I am not sure how to get events=2C how to hook for my application and get t=
he packets.=0A=
=A0=0A=
Regards=2C=0A=
Sagar=0A=
 		 	   		  =

RE: bluez5 pairing devices

[Ssagarr Patil]

Hi Marcel=0A=
=0A=
>>>=0A=
>>> maybe the backport has some issues that got fixed. The latest stable ke=
rnel is 3.19.2.=0A=
>>>=0A=
>>>> Is it true we cannot pair LE devices in bluez4.101 ?=0A=
>>>=0A=
>>> LE support with BlueZ 4 is limited to not really working at all. So if =
want to work on LE=2C then you need mgmt API support and a recent Bluetooth=
 subsystem and BlueZ 5.=0A=
>>>=0A=
>> With gattool and hcitool lecc I am able to pair. But I am not sure How t=
o get the data from le device ?=0A=
>> Any pointers on doing this ?=0A=
>>=0A=
> $ # hcitool  lecc 54:4A:16:5E:1B:9D=0A=
> Connection handle 1025=0A=
>=0A=
> Does it create a fd ? so that me C app can access ?=0A=
>=0A=
> # gatttool  -b 54:4A:16:5E:1B:9D -I=0A=
> [   ][54:4A:16:5E:1B:9D][LE]> connect=0A=
> [CON][54:4A:16:5E:1B:9D][LE]> char-desc=0A=
> [CON][54:4A:16:5E:1B:9D][LE]>=0A=
> handle: 0x0001=2C uuid: 2800=0A=
> handle: 0x0002=2C uuid: 2803=0A=
> handle: 0x0003=2C uuid: 2a00=0A=
> handle: 0x0004=2C uuid: 2803=0A=
> handle: 0x0005=2C uuid: 2a01=0A=
>=0A=
> I am not sure how to get events=2C how to hook for my application and get=
 the packets.=0A=
>=0A=
Gentle Ping.=0A=
=0A=
Regards=2C=0A=
Sagar=0A=
 		 	   		  =