I'm doing Out Of Band (= OOB) Bluetooth Pairing through NFC. I have a Bluetooth LE Device which has an NFC tag containing the information for OOB Pairing. When the user taps the NFC tag with its smartphone, it should do the Bluetooth pairing between the device and the phone. When the pairing is done, we want our application to be started and to display the data received through Bluetooth (ex: a Heart Rate graph). The Android Application uses a Broadcast Receiver to monitor the event BluetoothAdapter.ACTION_CONNECTION_STATE_CHANGED. By this way, it can be notified when a Bluetooth device is connected. If this BT device has the expected name, it will open the application.
I’m contacting you today because it works well if my Bluetooth Device implements a HID Profile but it doesn't work if I use another profile like a Heart Rate Profile (we have tested many profiles). I don't know if this is a bug or if it is intended. As a workaround, I have put the 2 profiles (HID + Heart Rate) in my Bluetooth device and then it works. When I tap the NFC tag, the Bluetooth connection is setup (it uses the OOB information contained in the tag), my application is started and it starts displaying the Heart Rate Data. Is it a normal that OOB Pairing doesn’t work if I use a profile like Heart Rate profile? For my tests, I‘ve used a Pixel 3 phone with Android 9 and a Nexus 6P with Android 8.1 Thank you -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/87b93fe0-34c1-4d56-bf79-2b3666e960f4%40googlegroups.com.
