Thank you for this solution Daniel! This is very unpublicized. The key difference is the string: "createInsecureRfcommSocket"
versus the string used in the standard publicized hack: "createRfcommSocket" Apparently some devices demand it to be "unsecured" else it fails with "permission Denied" exception. So, just changing that string value did the trick! Thank you. Our code now tries both in succession, first trying the insecure method. Thank you, thank you. This one was a doozie for us. To ensure my response is clear, here is the code that solved this issue for us: IntPtr createRfcommSocket = JNIEnv.GetMethodID(item.Class.Handle, "createInsecureRfcommSocket", "(I)Landroid/bluetooth/BluetoothSocket;"); IntPtr _socket = JNIEnv.CallObjectMethod(item.Handle, createRfcommSocket, new Android.Runtime.JValue(1)); ConnectionSock = Java.Lang.Object.GetObject<BluetoothSocket>(_socket, JniHandleOwnership.TransferLocalRef); Make special note of line #1 the "createInsecureRfcommSocket" vs. the "createRfcommSocket" string posted by others. -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/Bluetooth-problem-tp5713291p5713662.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
