FastBle:
BLE藍牙開發(fā)框架
https://github.com/Jasonchenlijian/FastBle
藍牙的種類
藍牙分經典藍牙和低功耗藍牙,這里介紹的是低功耗藍牙也就是BLE藍牙開發(fā)泡仗。
初始化
Application.class
BleManager.getInstance().init(getApplication());
BleManager.getInstance()
.enableLog(true)
.setReConnectCount(1, 5000)//重連次數(shù)以及間隔時間
.setSplitWriteNum(20)//拆分寫入數(shù)
.setConnectOverTime(10000)//連接超時時間
.setOperateTimeout(5000);//操作超時時間
搜索
val scanRuleConfig = BleScanRuleConfig.Builder()
// .setDeviceName(true, DEVICE_NAME) // 只掃描指定廣播名的設備蟀伸,可選
.setAutoConnect(true) // 連接時的autoConnect參數(shù),可選寄症,默認false
.setScanTimeOut(10000) // 掃描超時時間祸穷,可選拓提,默認10秒
.build()
BleManager.getInstance().initScanRule(scanRuleConfig)
BleManager.getInstance().scan(object : BleScanCallback() {
override fun onScanFinished(scanResultList: MutableList<BleDevice>?) {
//搜索完成,scanResultList搜索到的所有設備
}
override fun onScanStarted(success: Boolean) {
//開始搜索
}
override fun onScanning(bleDevice: BleDevice?) {
//bleDevice:搜索到的設備
if (bleDevice?.name == DEVICE_NAME) {
//搜索到對應設備后停止搜索并連接
stopScan()
BleManager.getInstance().connect(bleDevice, bleGattCallback)
}
}
});
//停止搜索
private fun stopScan() {
if (BleManager.getInstance().scanSate == BleScanState.STATE_SCANNING) {//判斷是否正在搜索
BleManager.getInstance().cancelScan()
}
}
連接
BleManager.getInstance().connect(bleDevice, bleGattCallback)
private val bleGattCallback = object : BleGattCallback() {
override fun onStartConnect() {
//開始連接
}
override fun onDisConnected(isActiveDisConnected: Boolean,device: BleDevice?,gatt: BluetoothGatt?,status: Int) {
//斷開連接
}
override fun onConnectSuccess(bleDevice: BleDevice?, gatt: BluetoothGatt?, status: Int) {
//連接成功
}
override fun onConnectFail(bleDevice: BleDevice?, exception: BleException?) {
//連接失敗
}
}
之前連接過的設備可以把設備mac儲存起來鸿吆,下次直接調用下面代碼可以直接連接囤采,速度會比重新搜索連接快很多
val deviceMac = SharedUtil.read(SP_DEVICE_MAC, null)
if (deviceMac != null) {
val device = BleManager.getInstance().bluetoothAdapter.getRemoteDevice(deviceMac)
if (device != null && device.name == DEVICE_NAME) {//判斷是否是正確的設備
stopScan()
BleManager.getInstance().connect(BleDevice(device), bleGattCallback)
}
}
獲取通知
設備連接成功后,調用下面代碼即可創(chuàng)建通知的監(jiān)聽惩淳,其中如果獲取到的Byte數(shù)組過大時蕉毯,返回的數(shù)據(jù)是進行分包處理的,需要自行將其連接才是一段完整的數(shù)據(jù)
BleManager.getInstance().notify(BleDevice bleDevice,
String uuid_service,
String uuid_notify,
BleNotifyCallback callback)
這里我的設備的uuid_service為0000ffe0-0000-1000-8000-00805f9b34fb
uuid_notify為0000ffe1-0000-1000-8000-00805f9b34fb
uuid_write為0000ffe2-0000-1000-8000-00805f9b34fb
但是可能有的設備不一樣思犁,這時候可以調用gatt!!.services
獲取到所有服務代虾,查找到你所需要的uuid_service,uuid_notify則可以通過 gatt!!.getService(uuid_service).characteristics
里獲取
其中有一個坑是在FastBle框架中激蹲,創(chuàng)建通知監(jiān)聽的時候會出現(xiàn)this characteristic not support notify!
這個錯誤棉磨,這個是因為框架內部過早調用gatt.discoverServices()
后導致gatt.getService()
時為空導致的。所以下面中学辱,我會先進行判空乘瓤,如果為空的話則延遲一秒調用gatt.discoverServices()
环形。之后內部會再次調用BleGattCallback中onConnectSuccess回調,在確保service不為空才進行調用BleManager.getInstance().notify()
//在BleGattCallback中onConnectSuccess回調調用
if (gatt!!.getService(UUID.fromString("0000ffe0-0000-1000-8000-00805f9b34fb")) == null) {
//判斷service是否為空
Handler(Looper.getMainLooper()).postDelayed({
gatt.discoverServices()
}, 1000)
return
}
//獲取通知
BleManager.getInstance()
.notify(
bleDevice,
"0000ffe0-0000-1000-8000-00805f9b34fb",//uuidService
"0000ffe1-0000-1000-8000-00805f9b34fb",//uuidNotify
object : BleNotifyCallback() {
override fun onCharacteristicChanged(data: ByteArray?) {
//獲取到的數(shù)據(jù)
if (data != null) {
getResult(data)
}
}
override fun onNotifyFailure(exception: BleException?) {
//錯誤
}
override fun onNotifySuccess() {
//成功
}
})
其他
表明衙傀、寫入抬吟、讀取也是類似的調用,這里就不詳細寫了
//表明
BleManager.getInstance().indicate(
BleDevice bleDevice,
String uuid_service,
String uuid_indicate,
BleIndicateCallback callback)
//寫入
BleManager.getInstance().write(
BleDevice bleDevice,
String uuid_service,
String uuid_write,
byte[] data,
BleWriteCallback callback)
//讀取
BleManager.getInstance().read(
BleDevice bleDevice,
String uuid_service,
String uuid_read,
BleReadCallback callback)
釋放資源
BleManager.getInstance().destroy()