Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>...the OP’s own answer is <em>wrong</em> in so far, that there are no “special system permissions”. – The “no permission” problem boils down to ... no permissions.</p> <p>Unfortunately it is not easy to debug, because adb makes it a secret which device it tries to access! On Linux, it tries to open the “USB serial converter” device of the phone, which is e.g. /dev/bus/usb/001/115 (your bus number and device address will vary). This is sometimes linked and used from /dev/android_adb.</p> <p><code>lsusb</code> will help to find bus number and device address. Beware that the device address will change for sure if you re-plug, as might the bus number if the port gets confused about which speed to use (e.g. one physical port ends up on one logical bus or another).</p> <p>An lsusb-line looks similar to this: Bus 001 Device 115: ID 4321:fedc bla bla bla</p> <p><code>lsusb -v</code> might help you to find the device if the “bla bla bla” is not hint enough (sometimes it does neither contain the manufacturer, nor the model of the phone).</p> <p>Once you know the device, check with your own eyes that <code>ls -a /dev/bus/usb/001/115</code> is really accessible for the user in question! Then check that it works with <code>chmod</code> and fix your udev setup.</p> <p>PS1: /dev/android_adb can only point to one device, so make sure it does what you want.</p> <p>PS2: Unrelated to this question, but less well known: adb has a fixed list of vendor ids it goes through. This list can be extended from ~/.android/adb_usb.ini, which should contain 0x4321 (if we follow my example lsusb line from above). – Not needed here, as you don’t even get a “no permissions” if the vendor id is not known.</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid Debug Bridge (adb) device - no permissions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRobert Siemer
    1. USRobert Siemer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust a note, if you don't have lsusb installed. You can install it by doing sudo apt-get install usbutils locate
      singulars
      1. PO
      1. USStephan Branczyk
    2. CODo you have a hint what to do if the device list is empty? I think I have checked everything, including permissions to the USB post in `/dev/bus/usb/...`: http://android.stackexchange.com/q/47938/13266
      singulars
      1. PO
      1. USkrlmlr
    3. COThis worked for me on Linux Mint. I found that changing the permissions of /dev/bus/usb/002/013 to 777 allowed me to see my device in adb devices. Thanks.
      singulars
      1. PO
      1. USMungoRae
 

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