On Tue, Dec 1, 2009 at 8:11 AM, Patrick <lordthunder...@gmail.com> wrote: > Hey, > > New here, hope to be in the right group. > I'm trying to wrap my head around the new bluetooth API. As I > understand the BluetoothSocket and ServerSocket classes, they need a > UUID to "encrypt" the socket connection.
Your understanding is not right here, UUID is used to lookup the port, not for encryption. The javadoc explains this. > While this is a nice feature, > this doesn't allow me to use another device to connect to an Android > Powered device, does it? So long as the other device allows you to export a simple SDP record with the RFCOMM port number and a UUID then you are ok. I have not come across a device that does not do this. > I'm also trying to create a backports.android.bluetooth socket on 1.6 > to connect to a computer/wearable device. But reading the docks, this > shouldn't really be possible with even 2.0... > I hope I'm making a huhge mistake here. > > Thanks, > > Patrick > > -- > 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+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
