StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Edit:</strong> </p> <p>After re-reading the question, it is clear that I misunderstood that the host machine was running Android. As udev does not exist in Android, the answer below does not answer the question. I am leaving this answer here in case anyone is looking for information on getting Android devices recognized by a non-Android linux host PC. </p> <p><strong>End Edit</strong></p> <p>The default permissions on those drivers (/dev/bus/usb/###/###) are determined by udev. In particular, it parses the configuration files in /etc/udev/rules.d and /lib/udev/rules.d in numerical order to determine the defaults.</p> <p>To override the defaults, you will need to create your own udev .rules file. To do so, you need the vendor ID of the device you want to grant permission to. lsusb will print out the device id for any particular device, and if you want a list of all vendors, you can try <a href="http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/" rel="nofollow">this</a>. </p> <p>So in your /etc/udev/rules.d/99-android.rules file, fill in the following line for each vendor you want to support:</p> <pre><code>SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE:="0666" </code></pre> <p>Note that in the example linked to above, they use = instead of := and SYSFS instead of ATTRS. I don't know why, but I found that that file didn't work verbatim on my machine.</p> <p>After writing the file, </p> <pre><code>restart usbserial </code></pre> <p>and re-plug your device. It should now default to 666 permissions.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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