Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules too broad for Asus; catching my bluetooth dongle. #72

Closed
hanetzer opened this issue Jan 21, 2016 · 1 comment
Closed

Rules too broad for Asus; catching my bluetooth dongle. #72

hanetzer opened this issue Jan 21, 2016 · 1 comment

Comments

@hanetzer
Copy link

As titled. The rules are too broad and catch my
0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth dongle:

ls -l /dev/bus/usb/006/
total 0
crw-rw-r--  1 root root     189, 640 Jan 20 19:19 001
crw-rw----+ 1 root adbusers 189, 641 Jan 20 19:19 002
crw-rw-r--  1 root root     189, 643 Jan 20 19:19 004

No harm being done as far as I can tell, but I thought you'd like to know.

JoesCat added a commit to JoesCat/android-udev-rules that referenced this issue Jan 21, 2016
…30#72

Also if vendor==Asus then skip other tests and go directly to match_found.
M0Rf30 added a commit that referenced this issue Jan 21, 2016
Mainly fix issue #72 to exclude bluetooth dongle
@M0Rf30
Copy link
Owner

M0Rf30 commented Jan 21, 2016

fixed by JoesCat. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants