From 0355976f628857b2675377fa4f2de12b3b5a44aa Mon Sep 17 00:00:00 2001 From: David Warren Date: Wed, 13 May 2009 12:02:27 -0700 Subject: [PATCH] AI 148793: Integrating publicly posted Bluetooth content. Automated import of CL 148793 --- pdk/docs/guide/bluetooth.jd | 130 +++++++++++++++++++++++++++++++++++- 1 file changed, 127 insertions(+), 3 deletions(-) diff --git a/pdk/docs/guide/bluetooth.jd b/pdk/docs/guide/bluetooth.jd index f9594d02a..5d5e8064c 100755 --- a/pdk/docs/guide/bluetooth.jd +++ b/pdk/docs/guide/bluetooth.jd @@ -9,11 +9,15 @@ pdk.version=1.0 UART Driver
Bluetooth Power On / Off
-Tools
+Compiling
+Troubleshooting
+Tools
+Feature Support
+

Introduction

-

Android's Bluetooth stack uses BlueZ version 3.36 for GAP, SDP, and RFCOMM profiles, and is a SIG-qualified Bluetooth 2.0 host stack.

+

Android's Bluetooth stack uses BlueZ version 3.36 for GAP, SDP, and RFCOMM profiles, and is a SIG-qualified Bluetooth 2.0 + EDR host stack.

Bluez is GPL licensed, so the Android framework interacts with userspace bluez code through D-BUS IPC to avoid proprietary code.

@@ -54,8 +58,31 @@ Solid elements represent Android blocks and dashed elements represent partner-sp

+Compiling

Compiling

-

Tools

+

To compile Android with Bluetooth support enabled, add the following line to BoardConfig.mk. +

+BOARD_HAVE_BLUETOOTH := true
+
+ +

Troubleshooting

+

Debugging

+

To debug your bluetooth implementation, start by reading the logs (adb logcat) and look for ERRROR and WARNING messages regarding Bluetooth. + Andoird uses Bluez, which comes with some useful debugging tools. The snippet below provides examples in a suggested order:

+
+hciconfig -a  			# print BT chipset address and features. Useful to check if you can communicate with your BT chipset.
+hcidump -XVt  			# print live HCI UART traffic.
+hcitool scan  			# scan for local devices. Useful to check if RX/TX works.
+l2ping ADDRESS  		# ping another BT device. Useful to check if RX/TX works.
+sdptool records ADDRESS # request the SDP records of another BT device.
+
+ +

Deamon Logs

+

Deamon logs for hcid (STDOUT) and hciattach (STDERR) are sent to /dev/null by default. Edit init.rc and init.PLATFORM.rc to run these daemons under logwrapper, which redirects output to logcat.

+

hciconfig -a and hcitool

+

If you compile your own system.img for Android, and hciconfig -a works but hcitool scan doesn't, try installing the firmware for the Bluetooth chipset. This firmware isn't yet available in the open source codebase, but you can adb pull and then adb pushit from a stock T-Mobile G1 (located in /etc/firmware/brf6300.bin).
+

+

Tools

BlueZ provides a rich set of command line tools for debugging and interacting with the Bluetooth sub-system, including:

+ + +

Feature Support

+

This section provides a change history of Bluetooth features added in each Android release and provides some rough guidance as to future features.

+

Android 1.0 release

+
Platform features
+ +
Qualifications
+ +
Example products
+ +

 

+

Android 1.1 release

+

No Bluetooth changes since 1.0

+

 

+

Android 1.5 release (cupcake)

+

Platform features

+ +

Qualifications

+ +
 
+

Future releases

+

This section offers a rough guide of which features the team is developing for the next release. This feature list may change without notice. It isn't possible to post scheduling advice to the mailing lists.

+ + +

Development Notes

+