Database Users

eclipse using ubuntu

i cant get my eclipse to debug my phone
if i adb devices i get
??????????????? no permissions
ubuntu 10.4

You need to add the samsung USB vendor code into udev.
Press ALT + F2
In the run dialog, enter:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
Enter your password when prompted.
Here is my configuration:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
18d1 = Nexus One
0bb4 = HTC (Dream/Magic/Evo/Hero)
04e8 = Samsung (Moment)
22b8 = Motorola (Droid)
Contained in italics are known phones for sure. I'm going to assume the Vibrant uses the same USB vendor code as the Moment.
ALSO, MAKE SURE THE VENDOR ID (i.e. 04e8) IS ALL LOWERCASE, UNLIKE THIS. I had severe issues figuring out why it still wasn't working after adding, and I found out it IS case sensitive.
Add the Samsung line to your file, and save it. Follow the following instructions.
Open a terminal (Applications -> Accessories -> Terminal).
Type:
Code:
sudo service udev restart
Then unplug and replug your phone.
In the terminal, type:
Code:
adb devices
It should return something like this:
Code:
[email protected]:~$ adb devices
List of devices attached
HT9CZP805116 device
Enjoy!
EDIT:
It may have a different Vendor ID.
If so, in the terminal, type:
Code:
lsusb
It will return something like this:
Code:
[email protected]:~$ lsusb
Bus 002 Device 006: ID 046d:c222 Logitech, Inc. G15 Keyboard / LCD
Bus 002 Device 005: ID 046d:c221 Logitech, Inc. G15 Keyboard / Keyboard
Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 003: ID 046d:c223 Logitech, Inc. G15 Keyboard / USB Hub
Bus 002 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 013: ID 18d1:4e12
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 13 is my Nexus One, so my vendor code would be 18d1. Substitute your result in and you shall achieve win!

i9000 GT not listed at all in adb devices on linux

Maybe this was answered in the wiki, but I can't view it.
In short, I'm trying to get Ubuntu 10.04 to show the phone in adb, so I can start playing around with development.
When I try adb devices in the terminal, The phone isn't listed. I do have USB debugging turned on the phone itself.
I'm using this in the udev rules as specified by the android guide.
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Click to expand...
Click to collapse
The vendor id matches both the guides listed one for samsung, and what I see in lsusb .
It has been documented a long while ago that this was a bug with samsung devices and their descriptor:
... I'm not allowed to post a link to the google code project, but it is issue 5027.
But has this been fixed or worked around? I'd love to get some app testing running on it.

Working
Were you able to get this working? If so, what did you do? I have the same issue.

Superroach said:
Maybe this was answered in the wiki, but I can't view it.
In short, I'm trying to get Ubuntu 10.04 to show the phone in adb, so I can start playing around with development.
When I try adb devices in the terminal, The phone isn't listed. I do have USB debugging turned on the phone itself.
I'm using this in the udev rules as specified by the android guide.
The vendor id matches both the guides listed one for samsung, and what I see in lsusb .
It has been documented a long while ago that this was a bug with samsung devices and their descriptor:
... I'm not allowed to post a link to the google code project, but it is issue 5027.
But has this been fixed or worked around? I'd love to get some app testing running on it.
Click to expand...
Click to collapse
I have it working no problems. Here is my /etc/udev/rules.d/51-android.rules file
Code:
[email protected]:~$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{04e8}=="0bb4", MODE="0666"
[email protected]:~$
Then when you run adb, you will prob have to do a sudo to start the server
Code:
[email protected]:~/Downloads/android-sdk-linux_86/tools$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
[email protected]:~/Downloads/android-sdk-linux_86/tools$ ./adb kill-server
[email protected]:~/Downloads/android-sdk-linux_86/tools$ sudo ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
1000e5d5d317 device
[email protected]:~/Downloads/android-sdk-linux_86/tools$ ./adb devices
List of devices attached
1000e5d5d317 device
Hope this helps!!
oh and
Code:
[email protected]:~$ cat /etc/issue
Ubuntu 10.10 \n \l
[email protected]:~$
Cheers!

wyild1 said:
I have it working no problems. Here is my /etc/udev/rules.d/51-android.rules file
Code:
[email protected]:~$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{04e8}=="0bb4", MODE="0666"
[email protected]:~$
Click to expand...
Click to collapse
No, this is confusing.
0bb4 is the USB VendorID of HTC
We would need "681c" here as {idProduct} for our SGS
Watching the bootlog UDEV told me SYSFS is being replaced by ATTR and ATTRS
According to UDEV the rule should look like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6877|68a9|681c|681d", ENV{ACL_MANAGE}="1"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", OWNER="whatever", GROUP="whenever", MODE="0666"
Where ATTR{idProduct} means the four modes from GT-I9000:
6877-> Kies-Mode
68a9-> Mediaplayer-Mode
681c-> Debug-Mode
681d-> MassStorage-Mode
But there are many things which can break this simple "add a xx-android.rule solution".
This issue has been fixed now in Ubunutu 10.10
You can plug in the phone (using USB-Debug-Mode), both drives show up correctly and you can mount them without any problems
Does "lsusb | grep -i samsung" show up your device?
Should look like this:
Bus 001 Device 002: ID 04e8:xxxx Samsung Electronics Co., Ltd

?????
Hi,
I am a newbie in linux and i try to make adb work on ubuntu 10.10. My mob is the samsung galaxy s i9000.I tried a few methods, actually installed ABD and java 6.0, managed to run ADB as a command but i can not make the correct permissions for my phone.Any expert?
Thanks a lot

[Q] USB mass storage in linux

Is there a way to connect to a linux system as a mass storage device to access the SD and internal memory?
I have had other android devices and never had any issue with just plugging it in and it just popping up. I am running linux mint KDE (Ubuntu based). This is the first device i tried with Honeycomb. It seems to use Acer sync instaed stock usb storage mode anyway.

A500 to Ubuntu USB
I could not get my Ubuntu machines to recognize the tablet when I plugged in the USB cable. Bummer.
Digging around I found a similar issue experienced by Xoom owners. The original article describing the fix is here. The steps listed there are for the Xoom, not the Acer, although the fix is almost the same.
I am posting the slightly modified instructions again here for clarity and brevity.
I did this fix on both Ubuntu 10.10 (Maverick) and 11.04 (Natty). Your mileage may vary.
1. Get the mtpfs package installed on your machine.
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box). For me, this was required for file transfers to work.
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Open your Terminal app on the Ubuntu machine.
5. Use the lsusb command to get the vendor id. Type "lsusb" in Terminal.
6. The output should look something like this:
Code:
[email protected]:~$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 006: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 005: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
Bus 001 Device 003: ID 04f2:b16b Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The line with "Acer, Inc." in it tells you the VendorID. In the example above, it's 0502.
** Disconnect the USB cable at this point **
7. Create a UDEV rule file. Use your editor of choice, mine is nano.
Code:
sudo nano /etc/udev/rules.d/51-android.rules
The file should contain this line when you are finished:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
8. Create a mount point and make yourself the owner.
Code:
sudo mkdir /media/a500
sudo chown [B][COLOR="darkred"]user[/COLOR]:[COLOR="darkred"]user[/COLOR][/B] /media/a500
IMPORTANT: Replace user:user with your user name and default group on your Ubuntu machine. For most people it will be your login name. If your login is "bob", then replace user:user with bob:bob, capice?
9. Add the mount point to fstab.
Code:
sudo nano /etc/fstab
At the bottom of the file, type this stuff:
Code:
# mount point for moto xoom
mtpfs /media/xoom fuse user,noauto,allow_other 0 0
10. Modify fuse.conf. Uncomment user_allow_other.
Code:
sudo nano /etc/fuse.conf
Look for #user_allow_other and remove the #.
11. Add yourself to the fuse group.
Code:
sudo nano /etc/group
Look for the line starting with "fuse" and put your login at the end of that line (if it's not already there).
12. Reboot.
You should see your mount point in Nautilus when you open it. After plugging in the USB cable, you can click the a500 entry under Places to mount the tablet.
Be sure to unmount it before disconnecting it. (always a good practice)
It took some time for some large folders to display. Patience is good.
From what I read, better fixes are on the horizon, but who knows when. For now, this allows me to get my music and movies on the tablet more rapidly than using wifi.
Thanks to roberj13 over at forum.xda-developers.com for the original post.

adb connection to kindle with linux problems

I'm on unbuntu 11.10, my kindle has CM7 on it, when it's plugged in and I run ./adb devices it shows up as a bunch of question marks and says no permissions. My phone connects fine in adb, so its not a problem with adb. The kindle also connects fine for USB storage and stuff.

i used to have the problem when I was running ubuntu, but even since I started running arch I haven't had that problem. It has something to do with user privelidges and the way I fixed it was by running
Code:
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
stating the adb server using root fixed the problem for me.
btw this isn't the right forum for questions.

Theres no questions forum for the kindle yet. I tried killing and re-starting adb with the sudo command, and it still shows question marks and no permissions

when in run lsusb i get 4 linux foundation root hubs for device1 and for device2 i get
ID 1949:0006 Lab126

Try sudo su or sudo ./adb devices
Sent from my Incredible 2 using XDA App

tried sudo ./adb devices and still question marks and no permissions.

Here's what I know, which isn't much. Maybe some of it will help?
Set up your /etc/udev/rules.d/51-android.rules file like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
Replace <username> with your user name.
The kindle reports idProduct 0005 when in recovery (at least mine did).
It's worth a shot.

teookie said:
Here's what I know, which isn't much. Maybe some of it will help?
Set up your /etc/udev/rules.d/51-android.rules file like this:
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0006", MODE="0600", OWNER="<username>"
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", ATTR{idProduct}=="0005", MODE="0600", OWNER="<username>"
Replace <username> with your user name.
The kindle reports idProduct 0005 when in recovery (at least mine did).
It's worth a shot.
Click to expand...
Click to collapse
Yea, this should fix your problem.
Open terminal and do this...
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
which will open up 51-android.rules in gedit so that you can add this rule...
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
Save the document and then close and reopen terminal.
Type...
Code:
adb devices
If you do not see your device try rebooting your computer
I do not have the rule set up the way it is quoted from the above post but you can add that in addition to the rule that I posted here.
This is the way my rules look for all of my devices. Notice that for some devices I have "subsystem" and subsystems" rules set up but there does not seem to be a difference in gaining access for ADB. I think I set up "subsystems" on a few devices a while ago for porting clockwork to a few devices or some other random thing. Either way you should just need the "subsystem" rule that I posted in the code box above.
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="3610", MODE="0666", OWNER="brian"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d00d", MODE="0666", OWNER="brian"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", ATTRS{idProduct}=="7820", MODE="0666", OWNER="brian"
Click to expand...
Click to collapse
Good luck!!
(This thread should be moved to General. Mods?)

I was having this issue yesterday as well... Fixed be making sure I edited usb.ini in ./android folder with 0x1949 and 0x0006 then i restarted computer.{ just to feel good about myself} rebooted. typed sudo su put my password in typed ./adb kill-server typed ./adb start-server typed ./adb devices and POW im running just fine. Ubuntu 11.10 here

my linux can't list the deivce
my dmesg is:
[ 1283.317124] usb 2-2: new high speed USB device using ehci_hcd and address 13
[ 1283.434819] usb 2-2: New USB device found, idVendor=1949, idProduct=0006
[ 1283.434828] usb 2-2: New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 1283.434835] usb 2-2: Product: kindle
[ 1283.434840] usb 2-2: Manufacturer: Amazon
[ 1283.434846] usb 2-2: SerialNumber: 0123456789ABCDEF
----
when I use adb-linux devices, it said nothing. : (includibg run with sudo)
>./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
how can I checked and connect it. my kindle can't boot up, it's always in opening-screen "Kindle fire".

ixc said:
my linux can't list the deivce
my dmesg is:
[ 1283.317124] usb 2-2: new high speed USB device using ehci_hcd and address 13
[ 1283.434819] usb 2-2: New USB device found, idVendor=1949, idProduct=0006
[ 1283.434828] usb 2-2: New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 1283.434835] usb 2-2: Product: kindle
[ 1283.434840] usb 2-2: Manufacturer: Amazon
[ 1283.434846] usb 2-2: SerialNumber: 0123456789ABCDEF
----
when I use adb-linux devices, it said nothing. : (includibg run with sudo)
>./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
how can I checked and connect it. my kindle can't boot up, it's always in opening-screen "Kindle fire".
Click to expand...
Click to collapse
Did you do what post #9 said?
printf "0x1949\n0x0006\n" >>~/.android/adb_usb.ini
adb kill-server
adb devices

I'm on Ubuntu 11.10. I spent a few hours trying different things, but adding SikYou's rule to 51-android.rules:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
Click to expand...
Click to collapse
...finally solved the issue for me. "adb devices" now shows my Kindle Fire.

sahara installation on ubuntu 16.04

Welcome
Sahara installation on ubuntu 16.04, all you need is there
https://github.com/openpst/sahara
Done
Time to test
Vale Piotr
Adding test results
[email protected]:~$ lsusb
Bus 002 Device 004: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Sahara install Qualcomm driver
It save me lot of work
[email protected]:~$ fastboot devices
[email protected]:~$
fastboot don't find device
[email protected]:~$ adb devices -l
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb connect
Usage: adb connect <host>[:<port>]
must learn a bit
SALT and SP_Flash_Tool-5.1916_Linux don't see port
Vale