summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoão Paulo Rechi Vita <jprvita@openbossa.org>2012-02-17 17:03:55 -0300
committerJoão Paulo Rechi Vita <jprvita@openbossa.org>2012-02-17 17:03:55 -0300
commit7884714d9d35a77736dc72af8557e931e932dffa (patch)
treea98a4410341667f6a99804ead0065e3c602ecc06
parentef483ece79c8bbfc7e1caf48fda6cf5b632bb566 (diff)
downloadbluez-le-docs-7884714d9d35a77736dc72af8557e931e932dffa.tar.gz
bluez-le-docs-7884714d9d35a77736dc72af8557e931e932dffa.tar.xz
bluez-le-docs-7884714d9d35a77736dc72af8557e931e932dffa.zip
howto: more language and format reviewDELIVERY-W07-20120217
-rw-r--r--howto.tex31
1 files changed, 15 insertions, 16 deletions
diff --git a/howto.tex b/howto.tex
index 7532803..f168b5a 100644
--- a/howto.tex
+++ b/howto.tex
@@ -377,9 +377,6 @@ NoInputNoOutput}.
After pairing with a new device, the \verb|test-device| script can be used to
interact with the remote device.
-There are 11 different operations that you can perform with the
-\verb|test-device| script:
-
\begin{enumerate}
\item List all known Bluetooth devices.
@@ -401,8 +398,9 @@ or discover all primary services.
$ test-device create <device address>
\end{verbatim}
-\item Remove a device from either a Bluetooth address or a path in D-Bus's
-object path form.
+\item Remove all the information related to a device on the local storage. This
+information includes settings, SDP information, and linkkeys. The argument can
+be either the device address or D-Bus object path.
\begin{verbatim}
$ test-device remove <device address or object path>
@@ -449,8 +447,10 @@ $ test-device alias <device address> [alias]
\end{verbatim}
\item Set the value of the property named {\em Trusted} by passing as third
-argument either the values {\em yes} or {\em no} (this command also requires an
-address to be passed as second argument).
+argument with either the values {\em yes} or {\em no}. Marking a device as
+trusted for the adapter means that no authorization will be asked for the user
+(through the user-agent) on an incoming connection from that device. This
+applies to BR/EDR devices only.
\begin{verbatim}
$ test-device trusted <device addres> [yes/no]
@@ -469,14 +469,15 @@ $ test-device blocked <device address> [yes/no]
\subsection{Generic Attribute API}
-Generic Attribute API documentation is available at doc/generic-api.txt. It
-is still experimental API. GATT based services have different requirements
-regarding (re)connection behaviour making abstractions difficult. The idea
-behind this API is to provide a generic method to external GATT client
-applications to handle characteristics directly.
+Generic Attribute API documentation is available at {\em doc/generic-api.txt}.
+It's still an experimental API. GATT based services have different requirements
+regarding (re)connection behaviour, making abstractions difficult. The idea
+behind this API is to provide a generic method so external GATT client
+applications can handle characteristics directly.
-An application can use the Generic Attribute API or use profile specific APIs.
-Currently available APIs: Proximity, Find Me and Thermometer.
+Applications can use the Generic Attribute API or use profile specific APIs.
+Currently available profile APIs are {\em Proximity}, {\em Find Me}, and {\em
+Thermometer}.
The \verb|test-attrib| is a script which tests the Generic Attribute D-Bus API.
Before using \verb|test-attrib| the remote device needs to be paired using
@@ -521,8 +522,6 @@ $ test-attrib chars <Service object path>
The \verb|test-adapter| script will make use of the Adapter D-Bus API to handle
Bluetooth adapters.
-There are basically 9 operations that you can perform with \verb|test-adapter| script:
-
\begin{enumerate}
\item Retrieve Bluetooth adapter's address.