Hello Pintu, I don't know the exact reason why you don't use Tizen 'bluetooth Natvie API' for bluetooth operation. Instread of using bluetooth Native API, you just use bluez's low level commands and tools or your own tool such like pairable on / pair. (If in that tool or command you are using tizen bluetooth Native API, then it will be no problem. But if you don't use bluetooth Native API, then it will be occur some problems.) Because,, in Tizen. we assum. Application or some modules only can access the shell by non root user. So can't control BT device directly. For this reason. We only provide the operation by bluetooth Native API. (capi-network-bluetooth / bt-service / bluez) Anyway..I hope you just try to check the BT operation in common binary. http://download.tizen.org/snapshots/tizen/common/latest/repos/arm-wayland/packages/armv7l/ capi-network-bluetooth-test-0.1.53-57.1.armv7l.rpm Then,,,for this, you can use 'bt_unit_test' tool after installing capi-network-bluetooth-test rpm on above link. (or attached rpm) For enable bluetooth, should call bt_adapter_enable API explict. In that time, bt-service process will be invoked and platform can use tizen BT's all functionality # bt_unit_test # select 1 (bt_initialize) # select 3 (Adapter) # in Adapter menu ## select 2 (bt_adapter_enable) But, for headless devices. In tizen 3.0, we do not yet support to allow or deny method officially. And we are prepairing some methods for headless devices for tizen 4.0. (Actually in tizen 3.0 when we recieve the pairing request..we automatically launch bt-syspopup UI by default. And application will select the popup's yes or no button to response it) I am not sure, 'agent on' and 'default-agent' is working in tizen 3.0 platform. Because in now tizen bluetooth concept is...bt-service & bt-syspopup is doing pairing agent role. Anyway...1 possiblility is..if you verify the operation in tizen 2.4, and the difference is. In tizen 2.4. bt-service is running In tizen 3.0, bt-service in not running. That means,,, if bt-service is running in tizen 3.0, we can pair the remote device without UI. And,, for running bt-service. You should call 'bt_adapter_enable' command explict. Please try to the same test,, after "BT ENABLE" using bt_unit_test. And,,,if it is not working, you should modify some codes for headless target. or we can create some internal APIs for handling pairing request and response. ** I list up tizen platform's bluetooth developers. You can query the detail things to these members direclty. dh79.p...@samsung.com hyuk0512....@samsung.com tt....@samsung.com b.su...@samsung.com h.sand...@samsung.com Thanks, Pyun --------- Original Message --------- Sender : PINTU AGARWAL <pint...@samsung.com> Principal Engineer/SRI-Bangalore-Kernel & BSP/삼성전자 Date : 2016-10-18 15:31 (GMT+9) Title : Re: [Dev] Tizen 3.0 common bluetooth client-server communication Hi Tizen Dev Community, Is anybody out here who can help me with my Bluetooth query? This is the last trial. I have developed a BT client-server application for Tizen 2.4. The bt-client-UI is running on one Tizen device with 2.4 The bt-server service is running on another device also contains 2.4. The client send some character and it is received by the server, which takes some action. Both are paired over Bluetooth and this is working well. However, I am not able to achieve this with Tizen 3.0 common on the server side. I have referred to this repo, to develop the Bt client/server: https://git.tizen.org/cgit/platform/core/api/bluetooth/tree/test?h=accepted/tizen_common On another server device (such as RPi2), I have used Tizen 3.0 common profile (head-less). The client-UI is still on Tizen 2.4 mobile device. I have used “bluetoothctl” to pair the two devices, and paring is working well. The bt_init() is also successful. However, when the client send the command, it is not received by the server. I have given print in the bt receive callback, and it’s not printing anything on the console. What I noticed is that, on the 3.0 common there is no “bt-service” running, but it is “bluetoothd”. Do, I need to change anything, to communicate between BT 2.4 client and BT 3.0 common profile? Please give some clue to proceed further. Thanks! Regards, Pintu From: PINTU KUMAR [mailto:pint...@samsung.com] Sent: Tuesday, October 04, 2016 12:44 PM To: 'Paweł Wieczorek'; 'dev@lists.tizen.org' Cc: 'pravi...@samsung.com' Subject: RE: [Dev] GBS package build for Tizen 3.0 common repo Dear Pawel, Thank you very much for your reply. Yes, I am able to build Tizen 3.0 common package using GBS and the following repo detailed. I am also able to install the rpm on my device. However, now I am not able to scan and connect the Bluetooth device on my Raspberry Pi2 using the USB Bluetooth dongle. Actually scanning is fine, but device discoverable on is failing and I am not able to pair it with another device, even though it shows me the device mac id. I used the following steps: #hciconfig hci0 up #bluetoothctl #power on #agent on #default-agent #pairable on #discoverable on Failed to set discoverable on: org.bluez.Error.Failed #pair 94:76:B7:7D:C9:B2 Attempting to pair … Failed to pair: org.freedesktop.DBus.Error.UnknownMethod Please help, if you know how to fix this problem. Thank You! Regards, Pintu From: Paweł Wieczorek [mailto:p.wieczor...@samsung.com] Sent: Friday, September 30, 2016 9:38 PM To: PINTU KUMAR; dev@lists.tizen.org Cc: pravi...@samsung.com Subject: Re: [Dev] GBS package build for Tizen 3.0 common repo Hi Pintu,
The repository you mentioned (framework/api/bluetooth) is dedicated to Tizen 2 (https://build.tizen.org/package/view_file?file=_service&package=capi-network-bluetooth&project=Tizen%3A2.4%3AMobile). Tizen:Common 3.0 builds capi-network-bluetooth package from a different repository - platform/core/api/bluetooth available at https://git.tizen.org/cgit/platform/core/api/bluetooth (https://build.tizen.org/package/show?package=bluetooth&project=Tizen%3ACommon). Also, GBS fails to resolve package dependencies because your .gbs.conf lacks URLs to Tizen:Base package repository. To access them, add a new repository: [repo.tizen_base_arm] url = http://download.tizen.org/snapshots/tizen/base/latest/repos/arm/packages/ and add it as the first repository for Tizen:Common profile: [profile.tizen_common] repos = repo.tizen_base_arm, repo.tizen_common to your .gbs.conf file. Please find below exemplary configuration file that I use: [general] profile = profile.tizen_common [profile.tizen_common] repos = repo.tizen_base_arm, repo.tizen_common [repo.tizen_base_arm] url = http://download.tizen.org/snapshots/tizen/base/latest/repos/arm/packages/ [repo.tizen_common] url = http://download.tizen.org/snapshots/tizen/common/latest/repos/arm-wayland/packages/ Best regards, Paweł Wieczorek Samsung R&D Institute Poland Samsung Electronics p.wieczor...@samsung.com On 30/09/16 16:39, PINTU KUMAR wrote: Hi All, I need one help for Tizen 3.0 common package build using GBS setup. In my .gbs.conf file I included this for Tizen 3.0 common repo. [profile.tizen_common] [repo.tizen_common] #url = https://download.tizen.org/snapshots/tizen/common/latest/ url = https://download.tizen.org/snapshots/tizen/common/latest/repos/arm-wayland/packages/ And I am trying to build this package: git://git.tizen.org/framework/api/Bluetooth But, I am getting following error during GBS build. Can somebody help, how to do GBS build for Tizen 3.0 common repo. I want to create a new repo for Tizen 3.0 common but the existing repo itself is not build. Please help. ---------------------------------------------------------- # gbs build -A armv7l --include-all –clean info: generate repositories ... gbs 0.24.2 info: prepare sources... info: package files have been exported to: /home/pintu/GBS-ROOT/local/sources/slp/capi-network-bluetooth-0.1.15-1 info: retrieving repo metadata... info: parsing package data... info: building repo metadata ... info: resolving skipped packages ... info: package dependency resolving ... info: *** Build Status Summary *** === the following packages failed to build due to missing build dependencies (1) === capi-network-bluetooth: nothing provides ld-linux.so.3 needed by dbus-glib-devel nothing provides ld-linux.so.3(GLIBC_2.4) needed by dbus-glib-devel nothing provides libexpat.so.1 needed by dbus-glib-devel nothing provides libgcc_s.so.1 needed by dbus-glib-devel nothing provides libgcc_s.so.1(GCC_3.5) needed by dbus-glib-devel nothing provides rtld(GNU_HASH) needed by dbus-glib-devel nothing provides libc.so.6(GLIBC_2.4) needed by dbus-glib-devel -- -- error: <gbs>some packages failed to be built ---------------------------------------------------------- Can somebody point out what is the problem. Thanks, Pintu _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
