# Bluetooth
> Bluetooth is a wireless technology standard for exchanging data over short distances from fixed and mobile devices, and building personal area networks ... [Wikipedia](https://en.wikipedia.org/wiki/Bluetooth)
* [Intel® Edison Boards Bluetooth® User Guide](http://www.intel.com/support/edison/sb/CS-035381.htm)
* [Setting Up a New Intel Edison Set Up Bluetooth](http://rwx.io/blog/2015/02/18/seting-up-an-edison/)
* [Turn your Intel Edison into an iBeacon](https://github.com/smoyerman/edison-ibeacon)
* [Sparkfun Bluetooth Profiles](https://learn.sparkfun.com/tutorials/bluetooth-basics/bluetooth-profiles)
## Opkg Packages
```bash
blink-led-dbg_0.1-r0_core2-32.ipk
blink-led-dev_0.1-r0_core2-32.ipk
blink-led_0.1-r0_core2-32.ipk
bluetooth-rfkill-event-dbg_1.0-r0_core2-32.ipk
bluetooth-rfkill-event-dev_1.0-r0_core2-32.ipk
bluetooth-rfkill-event_1.0-r0_core2-32.ipk
bluez5-dbg_5.37-r0_core2-32.ipk
bluez5-dev_5.37-r0_core2-32.ipk
bluez5-doc_5.37-r0_core2-32.ipk
bluez5-obex_5.37-r0_core2-32.ipk
bluez5-testtools_5.37-r0_core2-32.ipk
bluez5_5.37-r0_core2-32.ipk
```
```bash
root@edison:~/bluez-alsa/build# opkg list | grep blue
bluetooth-rfkill-event - 1.0-r0 - bluetooth-rfkill-event version 1.0-r0 Bluetooth rfkill event daemon for
bluetooth-rfkill-event-dbg - 1.0-r0 - bluetooth-rfkill-event version 1.0-r0 - Debugging files Bluetooth rfkill
bluetooth-rfkill-event-dev - 1.0-r0 - bluetooth-rfkill-event version 1.0-r0 - Development files Bluetooth
bluez5 - 5.37-r0 - Linux Bluetooth Stack Userland V5 Linux Bluetooth stack V5 userland
bluez5-dbg - 5.37-r0 - Linux Bluetooth Stack Userland V5 - Debugging files Linux Bluetooth
bluez5-dev - 5.37-r0 - Linux Bluetooth Stack Userland V5 - Development files Linux Bluetooth
bluez5-doc - 5.37-r0 - Linux Bluetooth Stack Userland V5 - Documentation files Linux Bluetooth
bluez5-obex - 5.37-r0 - Linux Bluetooth Stack Userland V5 Linux Bluetooth stack V5 userland
bluez5-testtools - 5.37-r0 - Linux Bluetooth Stack Userland V5 Linux Bluetooth stack V5 userland
kernel-module-bcm-bt-lpm - 1.0-r2 - bcm-bt-lpm kernel module bcm-bt-lpm kernel module; bcm43xx_bluetooth
libasound-module-bluez - 5.37-r0 - Linux Bluetooth Stack Userland V5 Linux Bluetooth stack V5 userland
pulseaudio-lib-bluez5-util - 6.0-r0 - PulseAudio library for bluez5-util PulseAudio library for bluez5-util
pulseaudio-module-bluetooth-discover - 6.0-r0 - PulseAudio module for bluetooth-discover PulseAudio module for
bluetooth-discover
pulseaudio-module-bluetooth-policy - 6.0-r0 - PulseAudio module for bluetooth-policy PulseAudio module for bluetooth-
pulseaudio-module-bluez5-device - 6.0-r0 - PulseAudio module for bluez5-device PulseAudio module for bluez5-device
pulseaudio-module-bluez5-discover - 6.0-r0 - PulseAudio module for bluez5-discover PulseAudio module for
bluez5-discover
webmin-theme-blue-theme - 1.700-r0 - Webmin theme for blue-theme Webmin theme for blue-theme
```
## Kernel Integration
> BlueZ. Official Linux Bluetooth Protocol Stack
>
> > Bluetooth tools and daemons. This package contains tools and system daemons for using Bluetooth devices. BlueZ is the official Linux Bluetooth protocol stack. It is an Open Source project distributed under GNU General Public License (GPL). [Bluez Homepage](http://www.bluez.org/)
* [BlueZ’ GIT Repository](http://git.kernel.org/cgit/bluetooth/bluez.git/tree/)
Bluetooth Kernel Subsystem
* [bluetooth.git](http://git.kernel.org/?p=linux/kernel/git/bluetooth/bluetooth.git;a=summary)
* [bluetooth-next.git](http://git.kernel.org/?p=linux/kernel/git/bluetooth/bluetooth-next.git;a=summary)
Bluez Tools
* **hciconfig** - HCI device configuration utility
* **hciattach** - HCI UART driver initialization utility
* **l2ping** - L2CAP ping
* **hcidump** - HCI packet analyzer
* **hcitool** - Generic writing and monitoring to the HCI interface
* bluetooth-agent
* bluetoothctl
### Kernel Display Message
#### Bluetooth Built-In Controller
```bash
root@edison:~# dmesg | grep -i blue
[ 0.235619] Bluetooth: Core ver 2.16
[ 0.235722] Bluetooth: HCI device and connection manager initialized
[ 0.235752] Bluetooth: HCI socket layer initialized
[ 0.235778] Bluetooth: L2CAP socket layer initialized
[ 0.235876] Bluetooth: SCO socket layer initialized
[ 0.922994] Bluetooth: HCI UART driver ver 2.2
[ 0.923015] Bluetooth: HCI H4 protocol initialized
[ 1.588016] Bluetooth: RFCOMM TTY layer initialized
[ 1.588081] Bluetooth: RFCOMM socket layer initialized
[ 1.588100] Bluetooth: RFCOMM ver 1.11
[ 1.588116] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.588130] Bluetooth: BNEP filters: protocol multicast
[ 1.588160] Bluetooth: BNEP socket layer initialized
[ 1.588175] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.588202] Bluetooth: HIDP socket layer initialized
```
#### Bluetooth USB Dongle
````bash
root@edison:~# dmesg
...
[ 85.022971] usb 1-1: new full-speed USB device number 2 using dwc3-host
[ 85.085188] usb 1-1: New USB device found, idVendor=0a12, idProduct=0001
[ 85.085218] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 85.085240] usb 1-1: Product: Bluetooth V2.0 Dongle
[ 85.085259] usb 1-1: Manufacturer: Bluetooth v2.0
```sh
### Kernel Modules
```sh
root@edison:~# lsmod
Module Size Used by
usb_f_acm 14335 1
...
bcm_bt_lpm 13708 0
bcm4334x 587105 0
````
## Applications / Libraries
> ConnMan
>
> > Daemon for managing Internet connections within embedded device and integrates a vast range of communication features usually split between many daemons such as DHCP, DNS and NTP. The result of this consolidation is low memory consumption with a fast, coherent, synchronized reaction to changing network conditions. [ConnMan Homepage](https://01.org/connman)
>
> RFKill
>
> > A small userspace tool to query the state of the rfkill switches, buttons and subsystem interfaces. Some devices come with a hard switch that lets you kill different types of RF radios: 802.11 / Bluetooth / NFC / UWB / WAN / WIMAX / FM. Some times these buttons may kill more than one RF type. The Linux kernel rfkill subsystem exposes these hardware buttons and lets userspace query its status and set its status through a /dev/rfkill. Given that at times some RF devices do not have hardware rfkill buttons rfkill the Linux kernel also exposes software rfkill capabilities that allows userspace to mimic a hardware rfkill event and turn on or off RF. [Rfkill Homepage](https://wireless.wiki.kernel.org/en/users/documentation/rfkill)
>
> Python interface to Bluetooth LE on Linux [Github](https://github.com/IanHarvey/bluepy)
```bash
root@edison:~# rfkill list
0: phy0: wlan
Soft blocked: no
Hard blocked: no
1: brcmfmac-wifi: wlan
Soft blocked: no
Hard blocked: no
2: bcm43xx Bluetooth: bluetooth
Soft blocked: yes
Hard blocked: no
```
### Setup
#### Opkg
```bash
root@edison:~# opkg install bluez5-dev
```
#### Pip
```bash
root@edison:~# pip install pyserial pybluez
```
#### Apt-Get
```bash
root@edison:~# apt-get install bluetooth pulseaudio pulseaudio-module-bluetooth pavucontrol bluez-firmware
root@edison:~# /etc/init.d/bluetooth start
```
### Programs
```bash
root@edison:~# systemctl status bluetooth.service
root@edison:~# systemctl stop bluetooth
root@edison:~# systemctl start bluetooth
root@edison:~# systemctl enable bluetooth
root@edison:~# rfkill unblock bluetooth
root@edison:~# rfkill list bluetooth
2: bcm43xx Bluetooth: bluetooth
Soft blocked: no
Hard blocked: no
4: hci0: bluetooth
Soft blocked: no
Hard blocked: no
root@edison:~# hciconfig hci0 down
root@edison:~# hciconfig hci0 up
root@edison:~# hciconfig hci0 status
hci0: Type: BR/EDR Bus: UART
BD Address: 98:4F:EE:03:39:02 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN
...
root@edison:~# hciconfig hci0 piscan
...
root@edison:~# hcitool scan
```
#### Python
```python
root@edison:~# git clone https://github.com/karulis/pybluez
Cloning into 'pybluez'...
remote: Counting objects: 1082, done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 1082 (delta 5), reused 0 (delta 0), pack-reused 1061
Receiving objects: 100% (1082/1082), 415.85 KiB | 407.00 KiB/s, done.
Resolving deltas: 100% (658/658), done.
Checking connectivity... done.
root@edison:~# cd pybluez/examples
root@edison:~/pybluez/examples# ls
advanced ble bluezchat simple
```
#### Npm
Install "Locate Beacon" Android App
```bash
root@edison:~# opkg update
root@edison:~# opkg install bluez5-dev
root@edison:~# npm install -g async
root@edison:~# npm install noble
root@edison:~# npm install bleno
root@edison:~# node node_modules/bleno/test-ibeacon.js
bleno - iBeacon
on -> stateChange: poweredOn
on -> advertisingStart
```
### Usage Models
#### Device Pairing
```bash
root@edison:~# rfkill unblock bluetooth
root@edison:~# bluetoothctl
[bluetooth]# scan on
[bluetooth]# scan off
[bluetooth]# pair 40:78:6A:26:4A:C2
[bluetooth]# connect 40:78:6A:26:4A:C2
[bluetooth]# paired-devices
[bluetooth]# info 40:78:6A:26:4A:C2
[bluetooth]# exit
root@edison:~# rfcomm bind - 40:78:6A:26:4A:C2 1
root@edison:~# ls /dev/rfcomm0
```
#### Text
```bash
root@edison:~# systemctl status bluetooth.service
root@edison:~# systemctl start bluetooth
root@edison:~# systemctl enable bluetooth
root@edison:~# rfkill unblock bluetooth
root@edison:~# rfkill list bluetooth
root@edison:~# hciconfig hci0 status
Make Your Device Discoverable
root@edison:~# hcitool scan
root@edison:~# rfcomm bind 0 40:78:6A:26:4A:C2
```
#### SPP
```
root@edison:~# systemctl enable bluetooth
root@edison:~# rfkill unblock bluetooth
```
```bash
root@edison:~# vi /etc/dbus-1/system.d/bluetooth.conf
```
```bash
...
...
```
```bash
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C MyEdison [default]
[NEW] Device 98:4F:EE:06:1B:99 edison
[bluetooth]# show
Controller 98:4F:EE:04:1A:8C
Name: edison
Alias: MyEdison
Class: 0x6c0110
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no
[bluetooth]#
```
```bash
root@edison:~# wget https://downloadmirror.intel.com/24909/eng/SPP-loopback.py
```
```bash
root@edison:~# python SPP-loopback.py -C 22 &
[3] 462
```
```bash
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C MyEdison [default]
[NEW] Device 98:4F:EE:06:1B:99 edison
[bluetooth]# show
Controller 98:4F:EE:04:1A:8C
Name: edison
Alias: MyEdison
Class: 0x6c0110
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no
[bluetooth]#
```
```bash
[bluetooth]# exit
[DEL] Controller 98:4F:EE:04:1A:8C MyEdison [default]
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C MyEdison [default]
[NEW] Device 5B:78:E1:26:DF:12 5B-78-E1-26-DF-12
[NEW] Device E4:56:CA:13:F1:5F Kontakt
[NEW] Device 46:1F:08:C5:D9:DD 46-1F-08-C5-D9-DD
[NEW] Device BC:85:56:1D:DD:BA PCJESU
[NEW] Device 20:C3:8F:88:49:99 RECAM53SJX07788
[NEW] Device 94:65:9C:1B:FC:AA DESKTOP-NFCK84P
[NEW] Device 54:27:1E:18:86:32 Bluetooth USB Host Controller
[NEW] Device C0:D9:62:06:AA:F6 Bluetooth USB Host Controller
[NEW] Device 40:78:6A:26:4A:C2 XT1008
[NEW] Device 20:C9:D0:7E:C1:D8 MacBook Pro de Carlos
[NEW] Device 4A:C6:4B:F5:E9:FD 4A-C6-4B-F5-E9-FD
[NEW] Device 20:16:04:18:56:94 HC-05
[NEW] Device 5C:AC:4C:E4:B4:A0 Dell Wireless 365 Bluetooth Module
[NEW] Device 34:E6:AD:01:5A:F8 IVAN
[NEW] Device A4:5E:60:BC:87:C2 Lluvia
[NEW] Device 80:E6:50:06:2F:7B MacBook Pro de Darius
[NEW] Device E4:F8:9C:19:69:40 RESG
[NEW] Device 28:C2:DD:21:D5:28 OSCAROMAÑA
[NEW] Device 9C:B7:0D:4C:EA:DC ELKIN-PC
[NEW] Device 12:27:07:00:09:24 ILIUM S420
[NEW] Device A4:5E:60:EA:3D:0E Dan Amador
[NEW] Device 34:36:3B:60:81:E9 Jonatan
[NEW] Device 52:57:A0:D5:5F:CC 52-57-A0-D5-5F-CC
[NEW] Device 43:F0:FB:66:86:E3 43-F0-FB-66-86-E3
[NEW] Device EA:A2:C0:D8:0A:0E Kontakt
[NEW] Device F1:C1:83:A4:17:0C Evolutel
[NEW] Device 4F:5E:E1:48:16:5F 4F-5E-E1-48-16-5F
[NEW] Device 62:40:14:83:78:AE 62-40-14-83-78-AE
[NEW] Device 62:D9:82:60:9E:83 62-D9-82-60-9E-83
[NEW] Device 4B:51:23:FE:59:00 4B-51-23-FE-59-00
[NEW] Device 6C:AD:AD:DE:F0:47 6C-AD-AD-DE-F0-47
[NEW] Device 69:A4:03:B7:6C:06 69-A4-03-B7-6C-06
[NEW] Device 5F:56:C1:11:DA:22 5F-56-C1-11-DA-22
[NEW] Device 98:4F:EE:06:1B:99 edison
[NEW] Device 2C:D0:5A:80:7A:44 AARCEMOR-MOBL3
[CHG] Controller 98:4F:EE:04:1A:8C Discoverable: no
[bluetooth]# pair 40:78:6A:26:4A:C2
Attempting to pair with 40:78:6A:26:4A:C2
[CHG] Device 40:78:6A:26:4A:C2 Connected: yes
[CHG] Device 40:78:6A:26:4A:C2 Modalias: bluetooth:v001Dp1200d1436
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 40:78:6A:26:4A:C2 Paired: yes
Pairing successful
[CHG] Device 40:78:6A:26:4A:C2 Connected: no
[bluetooth]# trust 40:78:6A:26:4A:C2
[CHG] Device 40:78:6A:26:4A:C2 Trusted: yes
Changing 40:78:6A:26:4A:C2 trust succeeded
[bluetooth]#
```
```bash
systemctl enable bluetooth
rfkill unblock bluetooth
bluetoothctl
agent KeyboardDisplay
default-agent
pair 40:78:6A:26:4A:C2
trust 40:78:6A:26:4A:C2
connect 40:78:6A:26:4A:C2
```
```bash
root@edison:~# git clone https://git.kernel.org/pub/scm/bluetooth/bluez.git
root@edison:~# cd bluez/
root@edison:~/bluez# ls
AUTHORS Makefile.obexd android doc peripheral
COPYING Makefile.plugins attrib emulator plugins
COPYING.LIB Makefile.tools bootstrap gdbus profiles
ChangeLog NEWS bootstrap-configure gobex src
HACKING README btio lib test
INSTALL TODO client monitor tools
Makefile.am acinclude.m4 configure.ac obexd unit
root@edison:~/bluez# cd test/
root@edison:~/bluez/test# dir
bluezutils.py pbap-client test-device
dbusdef.py sap_client.py test-discovery
example-advertisement service-did.xml test-gatt-profile
example-gatt-client service-ftp.xml test-health
example-gatt-server service-opp.xml test-health-sink
exchange-business-cards service-record.dtd test-heartrate
ftp-client service-spp.xml test-hfp
get-managed-objects simple-agent test-manager
get-obex-capabilities simple-endpoint test-nap
list-devices simple-obex-agent test-network
list-folders simple-player test-profile
map-client test-adapter test-proximity
monitor-bluetooth test-alert test-sap-server
opp-client test-cyclingspeed test-thermometer
root@edison:~/bluez/test# ./test-profile -u 101 -n edisonSpp -s -P 3 -C 22 serial22
```
*
#### SPP Rfcomm
```bash
root@edison:~# rfkill unblock bluetooth
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C edison [default]
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# scan on
[bluetooth]# pair
[bluetooth]# trust
[bluetooth]# connect
[bluetooth]# exit
```
```bash
root@edison:~# rfkill unblock bluetooth
root@edison:~# hciconfig hci0 up
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C MyEdison [default]
[NEW] Device 98:4F:EE:06:1B:99 edison
[NEW] Device 2C:D0:5A:80:7A:44 AARCEMOR-MOBL3
[NEW] Device 40:78:6A:26:4A:C2 XT1008
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Device 40:78:6A:26:4A:C2 Connected: yes
[CHG] Device 40:78:6A:26:4A:C2 Connected: no
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# quit
Agent unregistered
[DEL] Controller 98:4F:EE:04:1A:8C MyEdison [default]
root@edison:~# rfcomm listen hci0 &
[1] 377
root@edison:~# Waiting for connection on channel 1
Connection from 40:78:6A:26:4A:C2 to /dev/rfcomm0
Press CTRL-C for hangup
root@edison:~#
```
Connect from Android device from BlueTerm application
```bash
root@edison:~# cat /dev/rfcomm0
```
Write data from Android device from BlueTerm application
#### BlueTooth Headsets
#### Bluetooth Sound
```bash
root@edison:~# opkg install alsa-utils kernel-module-snd-usb-audio bluez5 gstreamer pulseaudio
root@edison:~# opkg install kernel-module-ftdi-sio
root@edison:~# rfkill unblock bluetooth
root@edison:~# bluetoothctl
[NEW] Controller 98:4F:EE:04:1A:8C edison [default]
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# scan on
[bluetooth]# pair
[bluetooth]# trust
[bluetooth]# connect
```
#### Serial Port Profile (SPP)
Libraries
For C Bluetooth Development:
```bash
root@edison:~# sudo apt-get install libbluetooth-dev
```
For Python Bluetooth Development:
```bash
root@edison:~# sudo apt-get install python-bluez
```
For Python Bluetooth in Edison (using pip, if for some reason you don't have it, learn [How-To Install Pip](https://pip.pypa.io/en/stable/installing/#pip-included-with-python)):
```bash
root@edison:~# pip install pybluez
```
There are two common ways to test SPP, one is by using D-BUS, the other is by using RFCOMM transport protocol.
To test using D-Bus we can use [this python script](http://downloadmirror.intel.com/24909/eng/SPP-loopback.py), copy it to Edison, enable the bluetooth device and run it:
```bash
root@edison:~# rfkill unblock bluetooth
root@edison:~# python SPP-loopback.py &
```
Then in an android device install a [Bluetooth SPP Manager](https://play.google.com/store/apps/details?id=at.rtcmanager).
At this point you need to pair the Intel Edison with your android device (see example above on how to use **bluetoothctl**, **hcicontrol** or any other user level application in your Edison).
Once paired, open the Bluetooth SPP Manager app, hit search, and when the Intel Edison appears tap on in to connect. now you can send text messages to Edison which can be seen on the terminal window of the Edison.
I know this need a lil' bit further explanation. just dropped here so i won't forget. Also what is going to be added is how to programmatically do the device discovering, pairing and SPP using c and python
## Audio
*
*
*
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://theiotlearninginitiative.gitbook.io/embedded-linux/subsystems/bluetooth.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.