Previous posting matches experience here. Droid phone is exchanging data via RFCOMM with a wearable sensor with Mitsumi C46N BT part. I paired the devices by entering the sensor PIN on the phone in Bluetooth Settings, then the Android app created a BT client socket using the standard 128-bit SPP Service Class UUID. Running sdptool on a linux laptop showed the sensor offering the 16-bit SPP Service Class UUID.
On Dec 2, 4:20 pm, Nick Pelly <[email protected]> wrote: > On Tue, Dec 1, 2009 at 3:45 PM, Patrick <[email protected]> wrote: > > Thanks a lot for your reply! > > > > Your understanding is not right here, UUID is used to lookup the port, > > > not for encryption. The javadoc explains this. > > > The only Javadoc i can find ( > > >http://developer.android.com/reference/android/bluetooth/BluetoothAda... > > and > > >http://developer.android.com/reference/android/bluetooth/BluetoothDev... > > ) > > is not very exact here. The device i'm using is a self developed > > device that uses a hardware chip for all the bluetooth stuff. So don't > > really have a lot influence on this. > > Guess we're back to the NDK, right? > > The non-android BT platform probably already advertises an sdp record. You > just need to work out what UUID to look for. > > Try reading the thread "bluetooth uuid" on this list just 1 week ago, where > some other developers hit this problem and found the UUID for there > non-android platform. > > Also, if you have a rooted device, you can use the shell command 'sdptool' > to browse the sdp records on your non-android device and see what is > advertised. > -- 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
