You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
On Android O we are unable to resolve our own mac address using BRO mode because the Gatt client requestUuid is always null and since we use it to compare with expected uuid, the condition will never be fulfilled (see here).
I noticed however, that the mServiceUuid first 24 characters (as string) are the same as bluetoothGattCharacteristic.getUuid()'s. But I don't know if it has something to do with BRO mode specific UUID or anything else.
Anyway, when I compared bluetoothGattCharacteristic.getUuid() and mServiceUuid first 24 chars instead of bluetoothGattCharacteristic.getUuid() and requestUuid, I was able to resolve device's own BT mac address.
The text was updated successfully, but these errors were encountered:
On Android O we are unable to resolve our own mac address using BRO mode because the Gatt client
requestUuid
is always null and since we use it to compare with expected uuid, the condition will never be fulfilled (see here).I noticed however, that the
mServiceUuid
first 24 characters (as string) are the same asbluetoothGattCharacteristic.getUuid()
's. But I don't know if it has something to do with BRO mode specific UUID or anything else.Anyway, when I compared
bluetoothGattCharacteristic.getUuid()
andmServiceUuid
first 24 chars instead ofbluetoothGattCharacteristic.getUuid()
andrequestUuid
, I was able to resolve device's own BT mac address.The text was updated successfully, but these errors were encountered: