Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks for the response Dennis. The way I envision the handshake happening is the user will connect the tablet to the device via a USB connection. The USB connection will facilitate the passing of keys/mac addresses for each device. Having the MAC address of each device I should be able to pair bluetooth with each other pragmatically set with the correct keys. This seemed to be what OOB pairing is all about. This is a custom job and not a app planned for the android market. So, if this is not the correct way to handle this type of pairing then I'm open to design suggestions.
      singulars
    2. COI search the android documentation some more and found some methods listed as @hide that seem useful. One such method is "createBondOutofBand". Is this something I can call through reflection or is there sill BlueZ stack changes needed? I am also still unsure on how to handle this on the server which is the non-android. By handle I mean methods I need to call into BlueZ that would let the server pair OOB. Thanks for any help!
      singulars
    3. CO@Brian: OOB pairing requires a Hash and Randomizer value from each of the Bluetooth HCIs (you can also do unidirectional authentication if only one side can send data, but this isn't the case here). I assume you'd get your values from the android side using [`readOutOfBandData`](http://www.androidjavadoc.com/2.3/android/bluetooth/BluetoothAdapter.html#readOutOfBandData%28%29), but I don't develop for android, so can't verify anything.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload