I'm trying to use the APP Droidcam on my phone, the PC client allows you to connect via ADB but with downloading the Android 2.1 SDK and trying just about everything I've found through google search. With typing: adb devices, in the terminal I continue to get: List of devices attached and a blank. Running lsusb it shows my phone is attached.
$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ adb devices
List of devices attached
$
Not really sure how to fix this issue or what to adjust. Any advice would be well appreciated!!
is debugging turned on ?
settings > Applications > development > usb debugging
Related
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!
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.
I have asus tf300t and linux ubuntu 12.04
I dont see my device when connected via USB,
lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
of course adb devices comes empty too.
I do have SDK installed and had no problem with other device, samsung galaxy S3.
For some reason the ASUS is not detecting that it is connected. No notification in android. no lsusb in linux (((
anyone have any advice?
BTW do I connect the USB cable to the docking KBD or the tablet?
If still open ….
What about the system log files like
Code:
dmesg
resp.
Code:
tail -n 10 -f /var/log/messages
after plug in of your device?
By the way, I have an issue with my Asus Memo Pad FHD 10 and fastboot!
http://forum.xda-developers.com/showthread.php?t=2527305
Best regards
rudi
Pursuant to this thread which is actually in the wrong location:
http://bit.ly/1ywwimI
I can't seem to get access to the PIT using Hiemdall or Jodin. I can get a verified connection but only if I use USB 3.0.
Please asisst before Samsung Bloatware and p0wned Car Home drives me batty.
I used CF-Autoroot with Heimdal and it worked fine...
Fuzzi99 said:
I used CF-Autoroot with Heimdal and it worked fine...
Click to expand...
Click to collapse
Speaking as a software developer of 10+ years myself, "Works for me" is a response you see occasionally from other developers. Almost always, it indicates a communication issue which is to say that some tiny but crucial detail was omitted somewhere by one party or another. A more appropriate response is, "I'm unable to reproduce this." The former is provocative and is often take as, "I got mine, so hose off." which in it's turn results in undesirable team dynamics (the other guy wants to choke you).
Fuzzi99 said:
I used CF-Autoroot with Heimdal and it worked fine...
Click to expand...
Click to collapse
Getting ready to take another crack at it.
What else can you tell me about that process? What version of Linux was it? I'm on Ubuntu 14.04
Does Heimdal need to be suid root or will plain Sudo work?
Was it on a USB 2.0 port or 3.0? Does your Linux machine have both?
I've got:
[email protected]:~$ lspci | grep USB && lsusb | grep hub
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
...and on the other machine I've got:
[email protected]:~$ lspci | grep USB && lsusb | grep hub
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jcllings said:
Getting ready to take another crack at it.
What else can you tell me about that process? What version of Linux was it? I'm on Ubuntu 14.04
Does Heimdal need to be suid root or will plain Sudo work?
Was it on a USB 2.0 port or 3.0? Does your Linux machine have both?
Click to expand...
Click to collapse
I'm running Linux Mint based on Ubuntu 13.10 ran with sudo and a usb 2.0 port as it only has usb 2.0 and 1.1
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller (rev 01)
Bus 001 Device 001: ID 1d6b:002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:001 Linux Foundation 1.1 root hub
Sent from my fabulous Note 4 Exynos
I was able to mount Yureka and sd card until Lollipop update. Now Yureka is not detected and it only charges (no notification for usb connection). I tried to follow this guide to mount MTP ubuntuforums.org/ showthread.php ? t= 2226702 but lsusb command gives output
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 013: ID 0cf3:3004 Atheros Communications, Inc.
Bus 001 Device 094: ID 05c6:9039 Qualcomm, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 5986:0525 Acer, Inc
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I cannot find difference in output before or after connecting yureka
Please help as i want to use it for android development in linux
You can use twrp recovery for that .