maybe you need to change the rule... this work fine for me on
crunchbang... and it is a debian based distro...
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666",
OWNER="your_linux_username"
remember to change your idVendor and OWNER...
On Sat, Feb 19, 2011 at 12:09 PM, ydm wrote:
> I'm
It's probably a matter of permissions on the device file.
The examples for Ubuntu specify MODE=”0666″, perhaps there is a way to do
this in Debian as well. Then you won't have to start adb as root (althogh it
should be harmless, it's an extra step).
-- Kostya
2011/2/19 ydm
> You're great! Than
You're great! Thank you! Now it works!
On Feb 19, 4:55 pm, Alessandro Pellizzari wrote:
> On Sat, 19 Feb 2011 05:03:00 -0800, ydm wrote:
> > $ ./adb devices
> > * daemon not running. starting it now on port 5037 * * daemon started
> > successfully *
> > List of devices attached
> >
On Sat, 19 Feb 2011 05:03:00 -0800, ydm wrote:
> $ ./adb devices
> * daemon not running. starting it now on port 5037 * * daemon started
> successfully *
> List of devices attached
> no permissions
I also tried creating udev rules bot got nowhere.
I now initialise adb server as r
I'm using the Java ADT.
Actually without any drivers the Galaxy tab works fine with adb on
Ubuntu. Now I'm trying to set up the dev tools on another computer
with Debian installed on it. I'm following the same procedure, but no
results...
On Feb 19, 3:41 pm, Daniel Drozdzewski
wrote:
> On Sat, Fe
5 matches
Mail list logo
