diff options
| author | aavit <eirik.aavitsland@digia.com> | 2013-04-30 12:25:46 +0200 |
|---|---|---|
| committer | Eirik Aavitsland <eirik.aavitsland@digia.com> | 2013-04-30 13:53:30 +0300 |
| commit | b44a5d6c04b3ab8a409577c3dfee9c1d180cb9f7 (patch) | |
| tree | 6187447ae9fca4521803782be7c66a622e177a28 /src/doc/src/b2qt.qdoc | |
| parent | 62fdd5ee286d482b97ab6b3112a3ec76309e209e (diff) | |
Add info about confirming adb connection to device.
Andy ran into this today - since he had not dis- and reconnected after
adding the udev rule during installation, there was no adb connection.
Change-Id: I07e33cbc33cb744c94bb68cc405970dc2686f12a
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
Diffstat (limited to 'src/doc/src/b2qt.qdoc')
| -rw-r--r-- | src/doc/src/b2qt.qdoc | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/src/doc/src/b2qt.qdoc b/src/doc/src/b2qt.qdoc index a856142..045fdef 100644 --- a/src/doc/src/b2qt.qdoc +++ b/src/doc/src/b2qt.qdoc @@ -238,6 +238,22 @@ echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="9018", TAG+="udev-acl"' | sudo tee -a /etc/udev/rules.d/70-boot2qt.rules \endcode + Now disconnect and reconnect the USB cable. Confirm that the + connection is working by running this shell command: + + \code + <SDK_INSTALL_DIR>/targets/android-utils/bin/adb devices + \endcode + + The output should be a list of connected android devices, + identifed with a serial number and a name. Note that the emulator + may be listed as well, its serial number will be its IP and port + number (\c{192.168.56.101:5555}). If your device is missing from + the list, or the serial number is \c{??????}, the connection is + not working properly. If so, check that the device is powered up, + and that the USB cable has been disconnected and reconnected. The + system log files \c{/var/log/udev} and \c{/var/log/syslog} may + provide relevant information in case of connection problems. \section1 Preparing Hardware for Running \B2Q |