Databases
StackOverflow2013
Postsdbo
PODetecting device for debugging (ADB) does not work
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODetecting device for debugging (ADB) does not work
    primarykey
    data
    text
    <p>I've turned USB debugging on on my Archos 43 Internet Tablet (Android 2.3.26), but adb does not detect the device.</p> <p>I have Kubuntu 11.04.</p> <p>Output of shell command "lsusb":</p> <pre><code>michael@schlepptop777:~/.android_sdk/platform-tools$ lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0e79:1411 Archos, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub </code></pre> <p>So my "Vendor ID" is 0e79, isn't it?</p> <p>For the next step I've created the following file:</p> <pre><code>sudo kate /etc/udev/rules.d/51-android.rules </code></pre> <p>with the following content:</p> <pre><code>SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666" </code></pre> <p>After that I've set the permissions:</p> <pre><code>sudo chmod a+rx /etc/udev/rules.d/51-android.rules </code></pre> <p>Then I've saved it and restarted udev:</p> <pre><code>sudo /etc/init.d/udev restart </code></pre> <p>And after doing all that steps adb still does not display my device:</p> <pre><code>michael@schlepptop777:~/.android_sdk/platform-tools$ ./adb devices List of devices attached &lt;empty line, because stackoverflow does not display this&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USSpitfire777
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODetecting device for debugging (ADB) does not work
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODetecting device for debugging (ADB) does not work
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODetecting device for debugging (ADB) does not work
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you tried restarting ADB as well, and then maybe disconnecting/reconnecting the device, rebooting the PC?
      singulars
      1. PODetecting device for debugging (ADB) does not work
      1. USStéphane
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload