I had the same permissions problem problem on my Ubuntu 8.04 box. You
can check the permissions with a simple ls -l on the usb hub that
they're connected to, 005 in my case.
$ ls -l /dev/bus/usb/005
crw-rw-r-- 1 root root 189, 512 2008-12-13 13:58 001
crw-rw---- 1 root root 189, 515 2008-12-13 14:00 004
The number for the device increments every time you unplug and plug it
back in, so that's an easy way to determine which device is the G1 in
case you want to set the permissions here every time. However, I
wanted it to be set to something more reasonable automatically. Here's
what I did:
1) Make an "android" group and add yourself to it.
2) Found out the Vendor ID of your device using lsusb. The vendor ID
is the number before the semicolon.
$ lsusb
Bus 005 Device 005: ID 0bb4:0c02 High Tech Computer Corp.
...
3) Create a rules file as root.
# cat - > 70-android.rules
BUS=="usb", SYSFS{idVendor}=="0bb4", GROUP="android", MODE="0660" /
* HTC */
<ctrl>-D
I ended up rebooting my machine for something else, but you can
probably just restart udev. I haven't tried this to verify it will
work.
# /etc/init.d/udev restart
On Dec 12, 12:35 pm, lotusscript <[email protected]> wrote:
> Hi,
>
> I use CentOS 5.2. I had the same problem as you. The way to get
> around it, in my case at least, was to run adb devices as root.
>
> For ubuntu try: su adb devices
>
> I also enabled USB debugging on the phone as set it not to sleep when
> charging
>
> Hope this helps
>
> Phil.
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
