summaryrefslogtreecommitdiff
path: root/core/java
diff options
context:
space:
mode:
authorNick Pelly <npelly@google.com>2010-02-24 11:34:03 -0800
committerAndroid (Google) Code Review <android-gerrit@google.com>2010-02-24 11:34:03 -0800
commita141ecff2fa21263404f32114c7cd27f4191af01 (patch)
tree0f2ce5772b8158dcfad392a7d9fd9aa72c12d846 /core/java
parent4b69fea63fd0dd873381b2115a16d46dd4012775 (diff)
parentea5056e5a705048f8495131ab0dcf087a2633fed (diff)
Merge "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."
Diffstat (limited to 'core/java')
-rw-r--r--core/java/android/bluetooth/BluetoothDevice.java4
1 files changed, 4 insertions, 0 deletions
diff --git a/core/java/android/bluetooth/BluetoothDevice.java b/core/java/android/bluetooth/BluetoothDevice.java
index cf9c58f12283..e77e76f79b2c 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.
* <p>The remote device will be authenticated and communication on this
* socket will be encrypted.
+ * <p>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.
* <p>Requires {@link android.Manifest.permission#BLUETOOTH}
*
* @param uuid service record uuid to lookup RFCOMM channel