[android-developers] [Bluetooth] Creating an insecure RFCOMM socket still requires pairing

I am using the listenUsingInsecureRfcommWithServiceRecord and
createInsecureRfcommSocketToServiceRecord calls in order to connect
one Android device to another.

On the first setting I had a Nexus One and a Nexus S both running
Android 2.3.6 - on this setting, connecting did not pop "Pairing
Request" Dialog.

On the second setting I tried the same Nexus One with a Samsung Galaxy
S2 running Android 2.3.3 - on this setting the "Pairing Request"
dialog did pop on both devices. This is weird as both devices are on
API level 10 which is supposed to support insecure connection.

Did anyone else bump into this strange behavior? Can someone verify
that this is a problem in 2.3.3, or perhaps in the specific model I
tested? Is there any workaround?

If necessary I can post relevant parts from the logcat.

Thanks,
Micha

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en