Lines Matching refs:accessory
36 <li><a href="{@docRoot}guide/topics/connectivity/usb/accessory.html">
44 designed to help Android hardware accessory builders and software developers create accessories
147 <li>Select <strong>Search for Devices</strong> to locate the ADK 2012 accessory and follow
154 interacting with the ADK accessory.</li>
164 <p class="note"><strong>Note:</strong> Your device must support Android USB accessory
207 <p class="note"><strong>Note:</strong> Your device must support Android USB accessory
272 software and program the ADK 2012 accessory. The following instructions explain how to setup and run
315 accessory to an Android device over Bluetooth.</li>
317 accessory to an Android device through a USB cable.</li>
336 to load software onto accessory hardware may be inconvenient or undesirable.</p>
348 <p>To build a program for your accessory:</p>
350 <li>Place your accessory code in the {@code MakefileBasedBuild/app} directory, including all
357 <p>To load the program on your accessory hardware:</p>
360 <li>Attach the accessory via USB cable to your development computer.</li>
361 <li>Check which port the accessory is attached to and modify the {@code UART} variable in the
364 <li>Execute the following command to load the program on the accessory:
370 <p>The essential feature of any Android accessory is its ability to connect and communicate with an
371 Android device. Creating a fast and reliable connection between your accessory and Android devices
372 is the first order of business when building software for an accessory. This section describes the
378 <p>The ADK 2012 app and hardware accessory use a Bluetooth Serial Port Profile (SPP) connection to
379 communicate. This connection allows two way communication between the ADK accessory and Android
384 accessory and the Android application uses SPP.</p>
389 accessory calls a {@code btStart()} method during the {@code setup()} method to enable radio
441 <p>Once Bluetooth is enabled with the code shown above, the accessory listens for connection
442 requests. The ADK library handles listening and connection details, so the accessory calls
456 {@code btStart()} method) and processed accordingly. The ADK accessory sends messages back through
464 and negotiates a connection with the ADK 2012 accessory. Here is a summary of the relevant code:</p>
474 output by the accessory (the {@code BT_ADK_UUID} variable mentioned earlier), otherwise the protocol
477 objects from the socket to communicate with the accessory:</p>
489 <p>The ADK 2012 app and hardware accessory can also use a USB connection to communicate, similar to
495 accessory code must make a few calls to initialize USB connectivity, including setting the accessory
513 <p class="note"><strong>Note:</strong> The identification strings must match the USB accessory
515 connect with the accessory.</p>
517 <p>Once USB is enabled with code shown above, the accessory listens for connection requests. The ADK
518 library handles listening and connection details, so the accessory calls {@code
530 <p>The accessory must then check for a live USB connection to process commands and send
567 <p>The ADK 2012 app uses the support library to implement the USB accessory connections, in order to
580 <p>Note that the app only receives events when the USB accessory identification information matches
590 <p>Connections from other USB devices are not received by the ADK 2012 accessory.</p>
592 <p>Once the connection is established, the app can communicate with the accessory through file input
614 <p>The ADK 2012 provides a reference implementation of this functionality for accessory developers.
615 No software application is required to be installed on the connected Android device, accessory
618 on the accessory.</p>
621 The first few calls are in the accessory {@code setup()} routine, which prepare the accessory for
652 audio output, see the {@code libraries/ADK/accessory.c} library file.</p>