Hi, Yes I have this working correctly in similar scenario you describe with InsecureRfcomm, try creating & connecting an outgoing socket connection to the device and make sure you are using the correct UUID string for the device. eg
'Hint: If you are connecting to a Bluetooth serial board then try using the well-known SPP UUID 00001101-0000-1000-8000-00805F9B34FB. However if you are connecting to an Android peer then please generate your own unique UUID.' http://developer.android.com/reference/android/bluetooth/BluetoothDevice.html Yes you need 2.3.3 or greater. Regards On Jun 24, 9:23 pm, Si <[email protected]> wrote: > I have done some further trawling around the internet and as far as I > can tell until recently the standard API only supported pairing (with > a passkey). > > It would appear though that this functionality has been included in > 2.3.3 (http://developer.android.com/sdk/android-2.3.3.html) > > "Android 2.3.3 adds platform and API support for Bluetooth nonsecure > socket connections. This lets applications communicate with simple > devices that may not offer a UI for authentication." > > Has anybody got any examples that connect to "non-secure" devices that > do not exchange a passkey? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en

