Hi corentin, Some BT socket related CAPIS have been implemented this week.
1. Can you "git clone" the latest version of platform/core/connectivity/bluetooth-frwk DEVEL branch on Tizen.org? And 2. Can you "git clone" the latest version of platform/upstream/bluez DEVEL branch on Tizen.org? (socket CAPIS don't very match the interfaces of Bluez5.X, therefore, we add some socket related interfaces on DEVEL branch of Bluez5.X ) (Please use the latest version of platform/upstream/bluez DEVEL branch on Tizen.org ) Then please test bt_socket_create_rfcomm() c api again. Best Regards Zheng Wu -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, July 3, 2014 12:17 AM To: Zheng, Wu Cc: Le Foll, Dominique; Xu, Martin; Jia, Pei P; Gu, Chao Jie; Wu, JiangboX Subject: Re: Bluetooth TCT : HOWTO + 1st status Hi Zheng Wu, Please find below my updated status. Corentin > > --- TCT current status --- > > For the moment, when running the whole TCT bluetooth test, app hangs > up probably due to an initialization issue. > > When running an unitary test case (like > BluetoothAdapter_getDevice_exist.html), the test passes ! > But after I can not perform any other test case. I've fixed the initialization bug in bluetooth crosswalk extension preventing from running many TCT tests. If you need it, the change is not merged yet, but is available here : https://github.com/crosswalk-project/tizen-extensions-crosswalk/pull/340 With this fix, now single tests can be run one by one. The whole test suite stops when checking bt_socket_create_rfcomm() c api. I am may not up-to-date... If not, when will it be integrated ? > > It appears that this sequence is failed : > - bt_initialize > - bt_adapter_set_device_discovery_state_changed_cb > - bt_adapter_enable > ... > - bt_adapter_unset_device_discovery_state_changed_cb > - bt_deinitialize > - bt_initialize > - bt_adapter_set_device_discovery_state_changed_cb ---> failed > > Do you see something wrong ? Or is it a problem in NTB ? This is a problem in NTB source code. Following above capi call sequence, bt_adapter_set_device_discovery_state_changed_cb() returns BT_ERROR_ALREADY_DONE error at the pointer condition on "unpaired_device_removed_node". There is probably something missing or wrong when unsetting callbacks... > > > Best regards, > Corentin > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
