Languages

Menu
Sites
Language
Bluetooth LE scan on Gear S2 for non-connectable devices

I am working on a native Tizen service app on a Gear S2 that scans for beacons using Bluteooth LE.

bt_adapter_le_start_scan(ble_scan_cb, NULL);

I am able to get a callback for my BLE beacon when I put it into "configurable" mode (which makes the beacon connectable).  However, the typical operating state for a beacon is non-connectable.  When the beacon is not connectable, I never get a callback from the scan for the beacon.

Is it possible to scan for non-connectable BLE devices on a Gear S2?

 

Edited by: Michael Harper on 31 Oct, 2016
List

Responses

5 Replies
Yasin Ali

Hi~,

Would you please explain more about non-connectable BLE devices.

Also check this link if you find anything helpful

: https://developer.tizen.org/dev-guide/2.4.0/org.tizen.tutorials/html/native/network/bluetooth_tutorial_n.htm#le_scan

Thanks

Michael Harper

A BLE device that is "not connectable" is essentially a transmitter. It is able to broadcast an advertising packet (e. g. iBeacon, AltBeacon, Eddystone formats) but otherwise cannot be connected via GATT.  The PDU portion of the advertising packet indicates that the device is "not connectable."

Unfortunately, the link provides sample code that is essentially identical to my own BLE scanning code.

Aussi Guy

Hey Michael,

lets clarify your query (interesting one !!):

1) You want to scan for non-connectable BLE devices (which only broadcasts but does not allow to be connected by GATT) using your gear S2 app.

   So your gear S2 has to be in 'connectable' mode but other BLE devices are 'non-connectable'. Am I correct to assume that ? 

2) You mentioned when you make your Gear S2 'not connectable', there is no callback from the scan for the beacon.

    Isn't that obvious? Can you please explain more with simple image or diagram?

3) Is there any example of the mechanism you are trying to implement? Have you seen this in any other OS (Android or iOS or Windows)?

 

Michael Harper

Hi Aussi Guy,

FYI I am not doing anything in terms of setting the Gear S2 itself to be connectable or non-connectable.  I'm simply running a BLE scan on the Gear S2.

The use case is common on Android and iOS when you are scanning for a beacon (iBeacon, AltBeacon, Eddystone beacon).  The beacon itself is normally not connectable via GATT unless you've specifically placed the beacon into a "configuration" mode.  The beacon information is present in the BLE advertising packet for the beacon, but again, the beacon itself is normally not "connectable."

To reiterate, with the beacon in its typical not-connectable operating mode, the beacon is never reported to the Gear S2 during a BLE scan.

Here is an example of someone scanning for beacons on Android:

https://www.pubnub.com/blog/2015-04-15-build-android-beacon-ibeacon-detector/

Yasin Ali

Please see this link

https://developer.tizen.org/forums/native-application-development/bluetooth-le-scan-non-connectable-devices

try with "bt_adapter_foreach_bonded_device()" and check retrived information.
your post is an interesting one. if you got any progress please share it.