Hi Ankur, > I am new to the BT LE and pls bare with me if I ask some silly questions. Thank you for support. > > I am now using 3.18.12 Linux kernel and Bluez 5.30 version on board. Our product requirement is to support only LE modes. To create PICS for host system using bluez, do I have to take http://git.kernel.org/cgit/bluetooth/bluez.git/tree/android/pics-gap.txt as a reference for selecting the configuration? > If yes, then in that case, why it has Broadcaster and Observer selected to 'False' under line#150-151 in pics-gap.txt as bluez does supports Central/Broadcaster/Observer LE roles as mentioned under bluez-5.30/doc/supported-features.txt? the main focus is central and peripheral role when it comes to Android. The broadcaster and observer roles are connectionless and not much in use. You can select them in the PICS and qualify BlueZ as broadcaster and observer only, but then a lot of the settings need to be chosen correctly. In addition bluetoothd will not be of much help since that is build for central and peripheral roles. > Inaddition, I am having some issue running the testcase TC_IDLE_NAMP_BV_02_C. pts-gts.txt says: "btmgmt advertising on" should work, but it is not working on my side. > > Following Log info: > Test case : TC_IDLE_NAMP_BV_02_C started > - MTC: Successfully received HCI_LE_CLEAR_WHITE_LIST_COMPLETE_EVENT. > - MTC: Successfully received HCI_LE_ADD_DEVICE_TO_WHITE_LIST_COMPLETE_EVENT. > - MTC: Successfully received HCI_LE_SET_SCAN_PARAMETERS_COMPLETE_EVENT. > - MTC: Successfully received HCI_LE_SET_SCAN_ENABLE_COMPLETE_EVENT. > - MTC: Receive Advertising report successfully. > - MTC: Successfully received HCI_LE_SET_SCAN_ENABLE_COMPLETE_EVENT. > - MTC: ATT connection established successfully. > - MTC-INCONC: Error returned in ATT_READ_BY_TYPE_CFM. > - CM_EXIT > - CM_EXIT > - CM_EXIT > - CM_EXIT > - MTC: Test case ended > -Final Verdict: INCONC > TC_IDLE_NAMP_BV_02_C finished > > - Prior to running above command I have also set name using command 'btmgmt name test_dev'. Do I need to run more commands to it? The name also needs to be available via a GAP characteristic. Normally running bluetoothd will do that for you. But if you do that manually, then need to register the GAP services. Regards Marcel -- 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