When running a service discovery on Android and a non-standard Bluetooth UUID is found, the returned UUID is not correct. To take an example, the custom UUID
is used by QtBluetooth's btchat example or the bttestui example. Android version 6.0.1 or above return/discover the following incorrect UUID though:
The individual bytes have been incorrectly swapped around. This bug is tracked as
This is an Android bug and QtBluetooth can only work around the issue. User code may use the following code to reverse the byte order:
The bug does not happen when the service's uuid is a standard UUID derived from the Bluetooth base UUID (00000000-0000-1000-8000-00805F9B34FB).