Home | History | Annotate | Download | only in adk

Lines Matching full:connected

31             <li><a href="#wait-adk">Wait for and detect connected devices</a></li>
33             <li><a href="#determine-adk">Determine the connected device's accessory mode
144     enumerate the bus, find a connected Android-powered device that supports accessory mode, and
335     connected to your computer for power (this also allows you to <a href="#monitoring">monitor the
336     ADK board</a>). When connected, accept the prompt that asks for whether or not to open the
342   the servos are connected) or by pressing the relay buttons in the application. On the ADK shield,
383   <h3 id="wait-adk">Wait for and detect connected devices</h3>
386   repeatedly and calls <code>AndroidAccessory::isConnected()</code> to check for any connected
387   devices. If there is a connected device, it continuously updates the input and output streams
388   going to and from the board and application. If nothing is connected, it continuously checks for
389   a device to be connected:</p>
414   <h3 id="determine-adk">Determine the connected device's accessory mode support</h3>
416   <p>When a device is connected to the ADK board, it can already be in accessory mode, support
420   the device that is connected hasn't already been handled. If not, it gets the connected device's
436     if (!connected &amp;&amp;
451             connected = configureAndroid();
457         connected = false;
460     return connected;
498 </pre>If this method returns false, the board waits until a new device is connected. If it is
514             connected = configureAndroid();