Package Details: android-udev-git 20220611.r0.g4cf2025-1

Git Clone URL: https://aur.archlinux.org/android-udev-git.git (read-only, click to copy)
Package Base: android-udev-git
Description: Udev rules to connect Android devices to your linux box
Upstream URL: https://github.com/M0Rf30/android-udev-rules
Licenses: GPL3
Conflicts: android-udev
Provides: android-udev
Submitter: robertfoster
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 610
Popularity: 0.027556
First Submitted: 2014-04-26 15:11 (UTC)
Last Updated: 2022-06-11 13:06 (UTC)

Required by (19)

Sources (1)

Latest Comments

bernimoses commented on 2018-07-19 12:32 (UTC)

The file adb_usb.ini does not exist anymore. Can you remove it from package()?

cribbageSTARSHIP commented on 2015-08-19 21:17 (UTC)

I know am late to the party, but using this package I was able to connect my android. I posted about it on reddit: https://redd.it/3hmvoj

robertfoster commented on 2015-04-20 18:39 (UTC)

all my PKGBUILD are managed on github. Check out https://github.com/M0Rf30/PKGBUILD for suggestions and forks

anatolik commented on 2014-04-25 17:25 (UTC)

android-udev is in [community] and the AUR package will be removed soon. Please create android-udev-git package (it is better name for the package anyway) so I can merge this package comments/votes.

anatolik commented on 2014-04-23 18:56 (UTC)

This is an extremely useful package. I would like to give the package higher status and move it to [community] so more people will enjoy it. What do you think?

whaler commented on 2014-04-08 02:24 (UTC)

Is it possible to add Samsung Galaxy Note 8.0? # lsusb Bus 001 Device 009: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1] ---> Galaxy Note (8.0) is not listed. KDE's Dolphin sees the device as a camera, and can travel its user storage file system, but is unable to transfer files from PC to device. The Galaxy Note device itself reports it does not find a proper app with which to communicate with the PC.

miro commented on 2014-04-05 14:20 (UTC)

please add Sony XPERIA V: ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0186", SYMLINK+="android_adb" ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0186", SYMLINK+="android_fastboot"

commented on 2014-04-03 16:24 (UTC)

I think the install file should say "relevant" instead of "relative"

kmacleod commented on 2014-03-18 21:14 (UTC)

Please add LG G2 D803: $ lsusb Bus 002 Device 014: ID 1004:631f LG Electronics, Inc.

amirs commented on 2014-02-27 06:01 (UTC)

can you please add Motorola moto g (Global GSM) ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e82"

Schlummi commented on 2014-02-24 15:17 (UTC)

Geeksphone Revolution: Bus 003 Device 017: ID 8087:0a16 Intel Corp.

Aldasa commented on 2014-02-18 22:40 (UTC)

Datawind Ubislate 7Ci: lsusb: Bus 007 Device 028: ID 2207:0010

Customizer commented on 2014-01-22 20:24 (UTC)

The Fairphone seems to be missing: $ lsusb Bus 002 Device 011: ID 0bb4:0c03 HTC (High Tech Computer Corp.) Please add.

AlexanderR commented on 2014-01-17 16:48 (UTC)

ZTE 790 (stock 4.0.4 firmware) after rebooting in bootloader neither adb nor fastboot detected phone (normally it is detected even without this package right after disabling storage mode). Had to add this identifiers to make it work: $ lsusb Bus 004 Device 010: ID 18d1:d00d Google Inc. ...

robertfoster commented on 2014-01-05 15:05 (UTC)

Please don't esitate to send new rules for your devices

bugbuster commented on 2013-11-06 01:48 (UTC)

There is a small typo: ===> If you have problems with printers or other devices please comment the related line ^^^^^^^

vwyodajl commented on 2013-11-05 06:35 (UTC)

Getting the same errors as @imraro. Only mine starts on line 1 systemd-udevd[191]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 1,starting at character 1 ('#') '# Skip this section below if this device is not connected by USB

imraro commented on 2013-10-31 09:59 (UTC)

Errors in journal: Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 37,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 41,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 56,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 66,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 76,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 80,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 84,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 88,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 92,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 96,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 104,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 248,starting at character 66 (' ') Oct 28 10:55:27 laptop systemd-udevd[176]: invalid key/value pair in file /usr/lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1 ('n')

techlive commented on 2013-10-20 12:22 (UTC)

Please rename the pacage to android-udev-git

lowfatcomputing commented on 2013-09-11 18:41 (UTC)

@dlin "git+https" will use git:// if unblocked and https:// otherwise. source=('android-udev::git+https://github.com/M0Rf30/android-udev-rules.git')

msx commented on 2013-07-21 00:51 (UTC)

Thank you!

archlinuxomane commented on 2013-06-27 10:48 (UTC)

git is a dependency, not listed

commented on 2013-06-25 23:04 (UTC)

The Oppo Find 5 works fine in fastboot, but not in the USB debugging mode.

dlin commented on 2013-06-10 04:02 (UTC)

1. please change source from git:// to https 2. failed to build 3. suggest change this PKGBUILD's layout and name to android-udev-git ==> Starting pkgver()... /tmp/yaourt-tmp-dlin/aur-android-udev/./PKGBUILD: line 23: cd: android-udev: Not a directory ==> Entering fakeroot environment... ==> Starting package()... /tmp/yaourt-tmp-dlin/aur-android-udev/./PKGBUILD: line 16: cd: android-udev: Not a directory

robertfoster commented on 2013-06-09 10:47 (UTC)

and let me know

robertfoster commented on 2013-06-09 10:47 (UTC)

try the Oppo Find 5 now

Lucky commented on 2013-06-09 09:01 (UTC)

please add the Oppo Find 5 (http://www.gsmarena.com/oppo_find_5-5161.php) MTP ON | ID 22d9:2764 MTP ON + ADB ON | ID 22d9:2765 ADB ON | ID 22d9:2767 MTP OFF + ADB OFF | ID 22d9:2768 FASTBOOT | ID 18d1:d00d Google Inc. RECOVERY | ID 18d1:d001 Google Inc. Sorry for spaming :/ i think now i got all ids

mtorromeo commented on 2013-05-21 12:59 (UTC)

@Morfeo: I suggest you to use a specific commit reference for the source file so that you don't have checksums updating all the time. Like this: https://github.com/M0Rf30/android-udev-rules/raw/19dd5d796c60f3f858a8f9c6912559684f50e29f/51-android.rules When you want to update the software you change both the commit and the checksums. Tracking master should only be done in a *-git PKGBUILD.

prettyvanilla commented on 2013-05-13 00:07 (UTC)

And it's been updated again yesterday...

JKAbrams commented on 2013-05-10 12:29 (UTC)

It's been updated so the checksum is off, correct checksum right now: md5 3ecf3f716250917e9007a63456e2bf70 https://github.com/M0Rf30/android-udev-rules/issues/12

raudi commented on 2013-05-05 12:25 (UTC)

I just noticed that enabling usb debugging changes the device id of my nexus 4 and nexus 7. Here is what lsusb gives me when USB debugging is enabled on my nexus 7: ID 18d1:4e42 Google Inc. When it is disabled: ID 18d1:4e41 Google Inc. For the Nexus 4 it is the same: ADB enabled: ID 18d1:4ee2 Google Inc. ADB disabled: ID 18d1:4ee1 Google Inc. But since this id is already in the rules(Under Nexus 10 which seems to have a different id after a quick websearch!), it works. Finally I know why my nexus 7 in fastboot mode wasn't recognized in qtadb. Please add the additional Nexus 7 id and clean up the Nexus 4/10 one. Also I don't know if it is intentional, but under Samsung is a second set of Nexus 4 and Nexus 7 rules, which are a bit different. If they are necessary (I don't know enough about udev to know), please move them to google, to make it logical, or remove them.

robertfoster commented on 2013-01-17 15:35 (UTC)

I've written a warning in post-installation...IMHO the best solution would be to collect every productid for every phone

raudi commented on 2013-01-16 20:12 (UTC)

I also have problems with my printer. After I installed this udev rules, it wouldn't be discovered by CUPS. It's a Kyocera FS 1020D and commenting the Kyocera line out makes it work again. I think there are a lot more Kyocera printers than phones (I only know of one, the echo), so it should be considered to remove the Kyocera line, comment it out, or at least give some kind of warning. The best solution, if it is possible, is of course to edit the rule, so it applies only to this one Kyocera phone.

mamamia88 commented on 2013-01-10 16:25 (UTC)

Never mind i can see it's in /usr/lib from reading packagebuild so can i delete the /etc/udev directory?

mamamia88 commented on 2013-01-10 16:22 (UTC)

Did the directory move? No files showing up in /etc/udev and trying to use go-mtpfs

robertfoster commented on 2012-12-19 20:12 (UTC)

nexus 4 7 and 10 added

SeeLook commented on 2012-11-13 11:36 (UTC)

Hi! The rules overrides group for my Samsung Usb printer to adbgroups, so cupsd can't accesses it.

robertfoster commented on 2012-11-09 17:57 (UTC)

nexus gsm and T&A chine phones added

adrianbs commented on 2012-11-08 14:06 (UTC)

Hi! I don't see the Galaxy Nexus (GSM) in your file. idVendor is 18d1 and idProduct is 4e30. Thanks!

trusktr commented on 2012-10-31 07:35 (UTC)

namcap is showing this message: android-udev E: unknown is not a common license (it's not in /usr/share/licenses/common/) What does that mean? Is it safe to install?

chungy commented on 2012-10-22 21:12 (UTC)

I believe libmtp is an unnecessary dependency. Also udev has been merged into systemd, so it should depend on systemd instead.

manuel commented on 2012-07-13 18:00 (UTC)

Could you add this too? # Mediacom Smartpad 715i SUBSYSTEM=="usb", ATTR{idVendor}=="2207", ATTR{idProduct}=="0000", GROUP="adbusers", SYMLINK+="android_adb" Thank you!

techryda commented on 2012-05-08 16:13 (UTC)

Please change the install location from /lib to /usr/lib as Arch is in the process of moving -cp $srcdir/51-android.rules $pkgdir/lib/udev/rules.d/51-android.rules -chmod a+r $pkgdir/lib/udev/rules.d/51-android.rules +cp $srcdir/51-android.rules $pkgdir/usr/lib/udev/rules.d/51-android.rules +chmod a+r $pkgdir/usr/lib/udev/rules.d/51-android.rules Thanks! See the following links for more background info: - https://wiki.archlinux.org/index.php/DeveloperWiki:UsrMove - https://fedoraproject.org/wiki/Features/UsrMove - http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge

PonsAsinorem commented on 2012-03-22 20:38 (UTC)

Fyi, SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c8d", SYMLINK+="android_adb" is not an Evo 4G, Incredible rev 0002, it's still an Incredible rev 0002, not Evo4G.

commented on 2012-03-22 08:24 (UTC)

# Xperia Arc S SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="414f", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="414f", SYMLINK+="android_fastboot"

big_gie commented on 2012-03-19 01:35 (UTC)

Samsung Galaxy Ace (GT-S5830) "Cooper" (debug mode) SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="689e", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="689e", SYMLINK+="android_fastboot"

axil42 commented on 2012-01-19 19:12 (UTC)

Nope, it just works ;)

commented on 2012-01-19 16:31 (UTC)

@markelos thanks for your reply. Do I have to copy it to /etc/udev/rules.d?

commented on 2012-01-19 16:28 (UTC)

@markelos thanks for your reply. Do I have to copy it to /etc/udev/rules.d?

axil42 commented on 2012-01-19 15:46 (UTC)

/lib/udev/rules.d as stated in pkgbuild.

commented on 2012-01-19 15:27 (UTC)

Where does the rules file get installed to? I just installed the package and don't have a rules file in /etc/udev/rules.d.

brandonw commented on 2011-12-07 00:50 (UTC)

Morfeo, could you please add the udev entries for the kindle fire? # Lab126 SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", GROUP="adbusers" # Amazon Kindle Fire SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", SYMLINK+="android_fastboot" Thanks!

robertfoster commented on 2011-12-06 21:25 (UTC)

thank you.added new entries

commented on 2011-12-06 15:23 (UTC)

"18D1" is the usb id for nexus devices. my nexus s works just fine here with it. Cherrs. my current rules file: http://pastebin.com/caBmFxLa

robertfoster commented on 2011-11-28 14:15 (UTC)

@Luminger: idVendor for google devices is 18d1 as you can see here http://developer.android.com/guide/developing/device.html @audrius: there's no rule on line 2 that include SYSFS. the rule adhere to new udev specifies.

audrius commented on 2011-11-28 08:53 (UTC)

Getting errors: Nov 28 04:45:26 localhost udevd[238]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/51-android.rules:2 Nov 28 04:45:26 localhost udevd[238]: invalid rule '/etc/udev/rules.d/51-android.rules:2' etc etc etc... Probably this is related with previous post. Can this be solved please?

commented on 2011-11-24 18:41 (UTC)

CTown is right, as I posted some month ago it should be "16d1" and not "18D1". Also this package is failing with the actual udev version which has dropped support for SYSFS. It would be great If you could fix the package up to be complient with the current udev.

archan.paul commented on 2011-10-28 06:52 (UTC)

Add support for Samsung Galaxy i5700 # Samsung Galaxy i5700 SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="681c",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="681c",SYMLINK+="android_fastboot" ref: http://archan.wordpress.com/2010/10/12/getting-adb-working-with-archlinuxsamsung-i5700cyanogen-cm6-froyo/

encbladexp commented on 2011-10-16 09:20 (UTC)

Please create adbusers as systemgroup (GID < 1000) ;-)

commented on 2011-09-26 17:33 (UTC)

@Morfeo: ZTE Blade works now.

commented on 2011-09-24 21:04 (UTC)

Nice package, helps a lot. By the way the value of SYSFS{idVendor} for Google devices should be "18d1" NOT "18D1". Just wanted to point that out!

stativ commented on 2011-09-17 09:02 (UTC)

Screw that, I removed the other package.

stativ commented on 2011-09-16 13:37 (UTC)

markelos: yeah, I would do that when it's decided which package too keep. Given the number of votes I think udev-android-rules has more users and therefore it might affect more users when deleted.

axil42 commented on 2011-09-16 12:40 (UTC)

We could request a merge also ;)

stativ commented on 2011-09-16 08:48 (UTC)

Morfeo: Did you contact maintainer of the udev-android-rules whether he still maintains his package? If he doesn't you could take over the udev-android-rules (you would get plenty votes for free) package and this package can be removed then.

robertfoster commented on 2011-09-06 09:21 (UTC)

try now

commented on 2011-09-02 13:53 (UTC)

For some reason it's not working out for my ZTE Blade. # lsusb | grep -i 19d2 - /etc/udev/rules.d/51-android.rules (standard input):Bus 002 Device 014: ID 19d2:1354 ONDA Communication S.p.A. /etc/udev/rules.d/51-android.rules:SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666", GROUP="adbusers" # grep adbusers /etc/group adbusers:x:101:csaba # ls -l /dev/bus/usb/002/014 crw-rw-r-- 1 root root 189, 141 Sep 2 15:39 /dev/bus/usb/002/014 Any idea anyone?

Anonymo commented on 2011-08-30 23:44 (UTC)

Just wanted to mention how useful this package is. Thanks.

robertfoster commented on 2011-08-30 14:28 (UTC)

fixed mtp detection

robertfoster commented on 2011-08-30 13:17 (UTC)

duplicated entries removed added many vendors from google official site organized entries with Vendor general entry followed by specific products rules

agru commented on 2011-08-21 13:28 (UTC)

Perhaps all Samsung should be combined (only one MODE entry) The Tab 10.1 uses MTP to transfer files (the symlink name is not really necessary but I thought it appropriate) Note to all Tab 10.1 users: libmtp 1.1.0 does not work with the tab, see bug: http://sourceforge.net/tracker/?func=detail&aid=3372454&group_id=158745&atid=809061 I also think that a note about the package "udev-android-rules" being replace by this could be good. # Samsung Galaxy Tab 10.1 SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685e", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685e", SYMLINK+="android_fastboot" SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", SYMLINK+="android_mtp"

commented on 2011-08-18 12:21 (UTC)

# Hero H2000 (chinese phone...) SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0001",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"

muni commented on 2011-08-17 09:28 (UTC)

# Acer ICONIA TAB A500 SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="3325", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="3325", SYMLINK+="android_fastboot"

robertfoster commented on 2011-08-12 17:17 (UTC)

here..updated rules for your android devices...syntax fits the new udev one. Please post your device rules and I will add them

rufflove commented on 2011-08-07 02:35 (UTC)

# rules for Samsung Galaxy i7500 SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6640",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6640",SYMLINK+="android_fastboot"

robertfoster commented on 2011-08-06 23:00 (UTC)

please use this to adhere to new udev syntax sed -i -e "s|SYSFS|ATTR|g" \ -e "s|sysfs|attr|g" \ -e 's|"bin/sh|"/bin/sh|g' *.rules

commented on 2011-07-22 08:49 (UTC)

I got boot warning! udevd[315]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/51-android.rules:2

commented on 2011-06-25 16:35 (UTC)

# Motorola Xoom # -- Xoom ID 1 SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="22b8",ATTR{idProduct}=="70a8",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="22b8",ATTR{idProduct}=="70a8",SYMLINK+="android_fastboot" # -- Xoom ID 2 SUBSYSTEM=="usb",ATTR{idVendor}=="22b8",ATTR{idProduct}=="70a9",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="22b8",ATTR{idProduct}=="70a9",SYMLINK+="android_fastboot"

nvllsvm commented on 2011-06-14 01:04 (UTC)

# Nook Color SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0660", GROUP="adbusers"

AshtonBRSC commented on 2011-05-06 23:24 (UTC)

# Asus Eee Pad Transformer (and other Asus?) SUBSYSTEM=="usb", SYSFS{idVendor}=="0b05", MODE="0660", GROUP="adbusers"

commented on 2011-04-11 19:55 (UTC)

# Rules for the Google NEXUS S SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e21", SYMLINK+="android_adb" SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e21", SYMLINK+="android_fastboot"

big_gie commented on 2011-03-27 23:01 (UTC)

Is the .install script missing?

commented on 2011-03-27 19:59 (UTC)

# LG (Swift) GT540 SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666" SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d00d", SYMLINK+="android_fastboot"

commented on 2011-03-23 17:18 (UTC)

updated rules

commented on 2011-03-23 14:22 (UTC)

# rules for Samsung Galaxy Tab SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6877",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6877",SYMLINK+="android_fastboot"

commented on 2011-03-21 00:02 (UTC)

@marlock I'm pretty sure it is, I haven't found any other way to get it to work

big_gie commented on 2011-03-19 19:52 (UTC)

Archos 43: SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666" SUBSYSTEM=="usb",ATTR{idVendor}=="0e79",ATTR{idProduct}=="1417",SYMLINK+="android_adb" SUBSYSTEM=="usb",ATTR{idVendor}=="0e79",ATTR{idProduct}=="1417",SYMLINK+="android_fastboot"

oskude commented on 2011-03-10 16:28 (UTC)

you could add this device too, works here (with Archos 101). Bus 001 Device 006: ID 0e79:1411 Archos, Inc.

commented on 2011-01-20 20:36 (UTC)

@grogers3.14: are you sure that the usb_modeswitch is needed for any Huawei phone? if so maybe it's ok to add your rule. @Luminger: Waiting for more reports from other users @Anachron: I'll update the install file in the way you said @jordz: the rule for sony ericsson is already in the rules file...

commented on 2011-01-18 09:14 (UTC)

Can you add the Sony Ericsson X10 mini pro? lsusb: 0fce:2138 Sony Ericsson Mobile Communications AB Xperia X10 mini pro (Debug)

Anachron commented on 2011-01-04 15:54 (UTC)

After doing `gpasswd -a USERNAME adbusers`, you have to log out and back in to be a member of the group. Should this be mentioned in the .install file? I did not know that and spent some time trying to access my phone.

commented on 2010-12-22 19:14 (UTC)

Maybe somebody noticed this as well: The Nexus One rule does (atleast for me) nothing. At first I did not found a solution for my issue but here it is (which should affect any other rule with this "error"): udev doesn't seem to like that the "d" within 'SYSFS{idVendor}=="18D1"' is written in caps - I modified it to 18d1 and - magicaly - adb worked. If anyone has problems with this you may try this. If someone can proof this also I would say that you update the package and lowercase any hexvalue within the udev.rule.

commented on 2010-12-13 22:20 (UTC)

My phone, the Huawei U8110 (or T-Mobile Pulse Mini) requires a call to usb_modeswitch before it will be detected by adb. This can be set to run automatically with a udev rule, but then the package would have to depend on usb_modeswitch (in community repo). Perhaps add it as an optdepend? usb_modeswitch command: /usr/sbin/usb_modeswitch -W -v 12d1 -p 1030 -V 12d1 -P 1034 -M '5553424370ab71890600000080010a11060000000000000000000000000000' -s 20 Possible udev rule: SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", SYSFS{idProduct}==1030, RUN+="<ABOVE COMMAND>"

commented on 2010-12-08 17:41 (UTC)

added Google's VendorID

commented on 2010-12-08 17:19 (UTC)

Would be great if you add the VendorID for the Nexus One (which isn't the HTC one). $ lsusb | grep Nexus Bus 001 Device 010: ID 18d1:4e12 Google Inc. Nexus One Phone (Debug)

vnoel commented on 2010-12-08 14:49 (UTC)

Yes, seems ok :) I will try it right away

commented on 2010-12-08 13:43 (UTC)

perfect! the install file is ready i changed the lines in 51-android.rules into SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0660", GROUP="adbusers" i think we are ready to update, is it correct?

vnoel commented on 2010-12-08 11:38 (UTC)

But what do you mean? Asking people doing it by themselves or creating the group for them in the install file? I would be in favor of the second case, so it is not important if it is complicated or not since it is automatically done and check for cases where the group has already been added. If it is for the first case, yes, I agree with you, groupadd is simple enough by itself. By the way, virtualbox seems to do the same as rtkit: http://repos.archlinux.org/wsvn/community/virtualbox-ose/trunk/virtualbox.install But they do not use -r for groupadd in order for it to not be a system group. So, I propose the following install file: post_install() { getent group adbusers >> /dev/null || /usr/sbin/groupadd adbusers || return 1 /bin/cat << EOF ===> In order to use adb, you have to be in the 'adbusers' group ===> For that, use: gpasswd -a USERNAME adbusers EOF } post_upgrade() { post_install } post_remove() { getent group adbusers &>/dev/null && /usr/sbin/groupdel adbusers }

commented on 2010-12-08 11:11 (UTC)

it seems more complicated... i prefer groupadd -f adbusers because it's the method used for virtualbox and i'm sure it works. by the way if this method doesn't work we can change it in future i'll update package soon

vnoel commented on 2010-12-08 10:31 (UTC)

Yes, seems nice to me :) We can copy what they do in official packages, for example rtkit add a new group in its install file: http://repos.archlinux.org/wsvn/packages/rtkit/trunk/rtkit.install Then tell people to add their user to the group.

commented on 2010-12-08 09:35 (UTC)

i like adbusers :) maybe we can add these lines in the .install file: # Add adbusers group groupadd -f adbusers # Add your user to the adbusers group: # gpasswd -a USERNAME adbusers

vnoel commented on 2010-12-07 12:34 (UTC)

Hi, As discussed on android-sdk, we could continue here to see what could be used as a group for enabling access to the devices. For example at work, our machines can be accessed by anyone using ssh and with the current rules in this package anyone could access my phone connected to my machine! The same way we have group for accessing disks, cdrom, camera or printer, we could have one for accessing adb devices :) I propose adbusers but maybe this is not the best.