Hi, On Monday 21 of September 2015 06:43:20 krishnaks@xxxxxxxxxxxxxxxx wrote: > Hi, > > I am using Bluez 5.33 on Android kitkat 4.4.3. > I am testing GATT functionality and I found that sometime > onWriteCharacteristic returns status 1 (BT_STATUS_FAIL). In android > Application I am checking for success status (i.e. 0) which I am getting > most of the time. But occasionally I am getting Status 1 because of which > my application logic is failing. > > When Bluez will send Status 1 and on what basis? How to avoid this? > > > -----------------------Working Log------------------------------- > D/BluetoothGatt( 1359): writeCharacteristic() - uuid: > 1d4de0a0-9f84-11e4-a042-0002a5d5c51b > D/BtGatt.GattService( 1259): writeCharacteristic() - > address=00:00:39:36:85:2F > D/BtGatt.GattService( 1259): onWriteCharacteristic() - > address=00:00:39:36:85:2F, status=0 > D/BluetoothGatt( 1359): onCharacteristicWrite() - Device=00:00:39:36:85:2F > UUID=1d4de0a0-9f84-11e4-a042-0002a5d5c51b Status=0 > ----------------------Log End------------------------- > > > --------------------------Failure Log--------------------------------- > D/BluetoothGatt( 1359): writeCharacteristic() - uuid: > 1d4de0a0-9f84-11e4-a042-0002a5d5c51b > D/BtGatt.GattService( 1259): writeCharacteristic() - > address=00:00:39:36:85:2F > D/BtGatt.GattService( 1259): onWriteCharacteristic() - > address=00:00:39:36:85:2F, status=1 > D/BluetoothGatt( 1359): onCharacteristicWrite() - Device=00:00:39:36:85:2F > UUID=1d4de0a0-9f84-11e4-a042-0002a5d5c51b Status=1 > --------------------------Log End------------------------------- Please enable debug logs for daemon (check android/README for how-to) and provide both debug logs and btmon HCI traces. -- BR Szymon Janc -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
