Go to file
Joe Da Silva 27216f35b4 Code and repetition reduction
Reduce the amount of repeated code referring to debug AND fastboot by
using just 1 enviroment variable in the ID test section of the script.
Add an "android" SYMLINK so developers know device is connected, but
the real debug SYMLINK is supposed to be "android_adb" as per docs.
2016-01-22 07:19:40 -08:00
ubuntu Updating new manufacturers and directory 2015-09-19 17:40:58 -05:00
51-android.rules Code and repetition reduction 2016-01-22 07:19:40 -08:00
README.md Rename README to README.md 2015-11-07 19:05:16 +01:00
license.txt GP3 licensed 2014-09-28 19:11:52 +02:00

README.md

Description

These rules refer to

http://developer.android.com/guide/developing/device.html

and include many suggestions from the Archlinux and Github Community

Installation

If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux: Log in as root and create this file: /etc/udev/rules.d/51-android.rules. Use this format to add each vendor to the file: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"

In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node. Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules. please refer to 51-android.rules in ubuntu directory Now execute: chmod a+r /etc/udev/rules.d/51-android.rules

Try group plugdev rather than plugindev. Then restart udev: sudo udevadm control --reload-rules sudo service udev restart

Add plugdev to sudo useradd -G plugdev