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) >>> >>> 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. > With gattool and hcitool lecc I am able to pair. But I am not sure How to get the data from le device ? Any pointers on doing this ? Thanks for your support. Regards, Sagar -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
