I want to controll my bluetooth controller completely programmatically with HCI commands. (Basically mimic the behaviour of other bluetooth controllers, e.g. of android devices) However, with the driver running, there will always be unwanted commands sent automatically. Is it somehow possible to prevent this? Or is this only possible by basically writing my own driver for the bluetooth adapter? I
Tag: hci
Bluetooth Low Energy : Passive Scan – but do not loop forever?
Referencing this post I have successfully managed to get a Linux Device (A Raspberry Pi Model A+) to switch my Bluetooth 4.0 USB dongle into the ‘advertising’ state: or I verified this using an Ipod running the ‘LightBlue Explorer’ App. All good so far. From another Linux box (another Pi) which also has a Bluetooth 4.0 dongle; I can also
Split TTY device based on packet type
I have a TTY device setup to monitor a serial port of a combined bluetooth/GPS chip. I’m using blueZ to implement the bluetooth stack and do everything bluetooth related. The data being sent across this port is all HCI packets, even the GPS data. The GPS data is wrapped in an HCI packet of type 0xXX (indicated by the first