The App demo “iBKS Hello World” is a project that contains the most important functions to begin interacting with a Beacon.
This document explains how this project, implemented for Android Studio, is structured and what the functions that can be found on it are.
This document is focused for App developers who have no experience in beacon communication management.
- Before you start
- Project iBKS Hello World
- App permission
- Scan Bluetooth devices
- Background Scan
1.Before you start
All you need to start playing with “iBKS Hello World”:
- Android Studio
- Android device with 5.0 version or above
- At least one iBKS Beacon
- Download iBKS Hello World project
2. Project iBKS Hello World
After downloading de “iBKS Hello World” project, you only have to open it on Android studio and compile it. All the needed libraries are included as dependencies and downloaded automatically.
The project is structured to show three important functionalities, each one on a different class:
- ScanActivity: scans and lists the beacons that are advertising around and allows the discovery of services and characteristics.
- NotificationDemo: Shows a notification dialog on the App triggered by a specific beacon packet detected.
- BackgroundScan: Starts background scan that allows to detect beacons and does some actions (send notification, open the app, …) even when the app is stopped.
The first activity started on foreground is “MainActivity” that shows the different options of the app and also checks the app permissions.
3. App permissions
In order to manage Bluetooth in Android it’s necessary to request the user’s permission.
If the Android version is 6.0 or higher, it’s necessary to request location permission. To do this it’s necessary to add permission in AndroidManifest.xml
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
The method which checks the location permissions is
checkLocBT() in MainActivity.
In order to use Bluetooth in Android devices, the first thing to do is check if the device that runs the app has Bluetooth Low Energy (beacons work with this type of protocol) and if it is enabled. In order to enable Bluetooth it’s necessary to add permission in AndroidManifest.xml
<uses-permission android:name="android.permission.BLUETOOTH" /> <uses-permission android:name="android.permission.BLUETOOTH_ADMIN" />
The method which checks the location permissions is
inicializeBluetooth() in MainActivity.
4. Scan Bluetooth devices
All the needed functions used to scan Bluetooth devices are in ScanActivity. The steps to achieve that are:
- Initialize Bluetooth Adapter and set scan settings:
- Start the BLE Scan with the defined settings and the corresponding ScanCallback:
- Wait for Bluetooth packets on
onScanResult) and do some action depending on the RSSI, advertsing, etc.
- Optionally, connect to the device. In the project, the connection is made when a device of the list is clicked:
- Once the connection is made, a
BluetoothGattCallbackcallback is received (
onConnectionStateChange) and it’s possible to discover services, read and write the characteristics and enable notifications (all these actions generate a
BluetoothGattCallbackcallback). At the end of the ScanActivity class there are some examples of these actions.
1 Note: On Samsung devices, the connection must be done on the main thread
The app shows a list of all Bluetooth devices detected with its own RSSI and MAC.
In some cases, it’s useful to show a notification to the user when a specific beacon is detected in a particular distance range. This example is shown in the NotificationDemo.
The most common way to detect a specific beacon is by checking the identifier advertised on the Bluetooth packet, either an iBeacon or Eddystone-UID packet. The steps to achieve that are:
- Start scanning as seen on ScanActivity.
- Wait for Bluetooth packets on ScanCallback callback.
- Check if advertising data contains the desired identifier. In this project, the identifier introduced in the settings dialog is used.
- Optionally, check the RSSI in order to trigger the action only for a particular distance range between the beacon and the user. In this project we defined three different ranges (Immediate, Near, Far)
- If all the conditions are true, show the dialog with the desired information:
6. Background Scan
Another interesting function is the background scan. This one allows us to scan advertisings when the app is in background and also start some actions when the beacon is detected.
The example of a background scan is in BackgroundScan class. In order to execute the background process, it is necessary to add it to AndroidManifest.xml (already added in the project):
<application android:name=".BackgroundScan" ... </application>
The background scan uses an external open source library. In order to use this library it’s necessary to add to the app build.gradle the following dependency (already added in the project):
The steps to configure the background scan are:
- Set Beacon Layouts. In the project there’s an example of iBeacon and Eddystone-UID layouts, but in the open source library you can find more frame types.
- Set the scan period in foreground and background. Please be careful in choosing the period because if it’s too short the Android device will have high battery consumption due to the fact that Bluetooth is scanning very often.
- Create the regions. It is the same as creating a list of identifiers that will be checked in every scan period.
- Binds the BackgroundScan Activity to the BeaconService (
mBeaconManager.bind(this)). When the onBeaconServiceConnection callback is received, enable the regions and start the scan (
- Wait for the callback called on every scan period, through the function didRangeBeaconsInRange, and check if the beacons have been found.
- Optionally, a notification can be send to the user when a beacon is detected. There’s an example code to create a notification in the project.
Last modified: November 10, 2016