From ea5056e5a705048f8495131ab0dcf087a2633fed Mon Sep 17 00:00:00 2001 From: Nick Pelly Date: Wed, 24 Feb 2010 11:19:10 -0800 Subject: [PATCH] Add documentation to help developers make an RFCOMM conection to a Bluetooth serial board. They all use a well-known UUID that is not really explained anywhere official, and this always trips developers up. Change-Id: I53bda44b580f472b1ff1ad196b25485b68f4b5d5 --- core/java/android/bluetooth/BluetoothDevice.java | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/core/java/android/bluetooth/BluetoothDevice.java b/core/java/android/bluetooth/BluetoothDevice.java index cf9c58f122832..e77e76f79b2c4 100644 --- a/core/java/android/bluetooth/BluetoothDevice.java +++ b/core/java/android/bluetooth/BluetoothDevice.java @@ -664,6 +664,10 @@ public final class BluetoothDevice implements Parcelable { * determine which channel to connect to. *

The remote device will be authenticated and communication on this * socket will be encrypted. + *

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. *

Requires {@link android.Manifest.permission#BLUETOOTH} * * @param uuid service record uuid to lookup RFCOMM channel