adb devices empty list - android

I have problem with installing android development environment. I do following:
1) I installed the openjdk
2) download eclipse and sdk from developer.anroid.com site
3) type lsusb in shell and know vendor id: 10d6:0c02
4) create 51-android.rules in /etc/udev/rules.d folder:
SUBSYSTEM=="usb", ATTR{idVendor}=="0c02", MODE="0666", GROUP="plugdev"
5) and i edit the adb_usb.ini file, i add the 0x0c02 string
6) I enable debugging on my device
6) i run adb kill-server and adb start server and run adb devices and i get empty list
What is wrong? My pc is HP Envy 4 1055er and ubuntu 13.04 os. Please help me.

you're confusing the ProductId with the VendorID. Try adding 0x10d6 to the files instead of 0x0c02

Related

Trouble Connecting Azpen Tablet to Linux PC

I purchased a new tablet which is manufactured by a company called Azpen. The product page for the device is http://www.azpenpc.com/product_t64.html I'm trying to develop apps for it and I'm a beginner. I connected the device to my Linux machine (running CentOS 5.3) but something isn't working right. I can't install the simple HelloWorld program via 'ant debug install'. Here's the output of some adb commands, which I ran as a regular user, then as root:
# adb usb
error: insufficient permissions for device
# adb devices
List of devices attached
???????????? no permissions
I did 'adb kill-server ; adb start-server' as root, but this didn't help.
Does anyone know what the problems is? My next attempt at debugging this myself was to create a new rules file in /etc/udev/rules.d, but I don't know what 'idVendor' to use for Azpen devices. Can anyone help with this?
ps. I also posted this on http://forums.androidcentral.com
I ran 'dmesg' and grepped for 'idVendor' in the output and found:
usb 2-1.2: New USB device found, idVendor=18d1, idProduct=0003
So I added this line to /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
then restarted adb as root: 'adb kill-server ; adb start-server' and it worked.

Device not getting detected in DDMS in Ubuntu 12.04 - 32bit

I am using Ubuntu 12.04 32bit. I have a Micromax Ninja A87 Android phone running GB 2.3.5.
My problem is the phone does not get detected. When I try on a windows 7 pc, it does get detected.
Here are all the steps I followed but still no lucks.
$ lsusb
Output: Bus 002 Device 006: ID 1c9e:9e08 OMEGA TECHNOLOGY
I created the 51-android.rules file and have this as the contents:
SUBSYSTEM=="usb", ATTR{idVendor}=="1c9e", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
Alternatively I tried this link also - http://forum.xda-developers.com/showthread.php?t=1475740
Done chmod a+r on 51-android.rules
Restarted udev , also restarted my PC.
done kill-server & start-server
But still when I do "adb devices" -- it doesn't detect my phone.
Here are some more info:
1)USB debugging is enable in phone.
2)Whenever i connect my phone to pc, it shows a popup in PC("usbmodem mass storage has been connected").
while checking the vendorId and productId in windows(phone always detected by windows system), it shows 1c9e:9e18. But as mentioned, in ubuntu it shows 1c9e:9e08. So tried to switch to the same vendorId/productId in ubuntu i.e 1c9e:9e18. So created a rule in /etc/usb_modeswitch.d/1c9e:9e08 and put the below contents in the file.
Code:
DefaultVendor=0x1c9e
DefaultProduct=0x9e08
TargetVendor=0x1c9e
TargetProduct=0x9e18
SierraMode=1
NoDriverLoading=1
add below code to the file /lib/udev/rules.d/40-usb_modeswitch.rules
ATTR{idVendor}="1c9e", ATTR{idProduct}="9e08", RUN+="usb_modeswitch '%b/%k'"
Once done run :
sudo usb_modeswitch -v 0x1c9e -p 0x9e08 -S -R -W
Now adb will recognise the phone.
For further reference you can go through the below link:
http://forum.xda-developers.com/showthread.php?t=1968465

How can usb debugging for Kindle Fire can be enabled on a Linux (Ubuntu)?

I am trying to do some Android development on a Kindle Fire, however I am having trouble making my Ubuntu 11.04 recognize the device for using it with the ADB. I've added a line like this SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", GROUP="plugdev" in my etc/udev/rules.d/51-android.rules file, restarted the computer and plugged in the Fire but still adb devices did not show it.
Any suggestions?
It seems that it works if you edit ~/.android/adb_usb.ini and add 2 lines containing 0x1949 and 0x006 and restart the adb server using
adb kill-server
adb start-server
Also, the 51-android.rules file contains the Lab126 vendor id.
You may also need to edit the inf file. See the instructions here:
http://g-ecx.images-amazon.com/images/G/01/sdk/Connecting_your_Kindle_Fire_to_ADB.pdf
Add a single line to: ~/.android/adb_usb.ini. The content of the line: 0x1949
Restart server
$ adb kill-server
$ sudo adb start-server
Worked for me on Ubuntu 11.10
There will be a number of steps you have to take. Basically you need to edit an ini file. Different steps is needed for MAC and PC.
Kindle Fire: Enable USB Debugging

Samsung Pop 5570 does not connect in Ubuntu 10.10. in development mode

Adb devices is not listing my Samsung Pop 5570 wen connected in with USB debugging on in ubuntu 10.10
adb devices
?????????? no permissions
i did add the 51-android.rules file in /etc/udev/rules.d folder but still adb devices shows that devices wit ?????? no permissions.
51-android.rules file has the following contents:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="04e8", MODE="0666"
please let me know if i am missing something
I resolved the issue by appending #samsung in the 51-android.rules file and copying the "adb" command to /bin folder.
$ restart udev
$ cp adb /bin
$ sudo adb kill-server
$ sudo adb start-server
$ sudo adb devices
List of devices attached
S5570e905be1c device
Edit: I suspect your subsystem name is the culprit (simply try "usb" instead). However, I am unable to comment as to whether or not that subsystem name is still valid in 10.10 as I do not know what changes have been made to udev.
First step would be to verify that your vendor id is correct with lsusb (that appears to be Samsung's vendor id, but it can't hurt to check).
I am also running 10.10, but I have an HTC device. Here is my rule file's content:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
After editing the file, I unplugged my device. Just in case, I kill adb's daemon:
sudo adb kill-server
I then reconnected my device and executed "adb devices". adb started the daemon without sudo. My device was listed properly.
I resolved the above problem by prefixing the 51-android-rules file with #samsung, i mean,
'#samsung SUBSYSTEM=="usb_device", SYSFS{idVendor}=="04e8", MODE="0666"'.
I killed the adb server and restarted in SU mode and then ran
$sudo adb devices,
i was able to see my device listed.

Setting up android phone with eclipse

I have been developing a project app to learn about android, I can upload my app to my htc desire on my desktop using linux ubuntu and eclipse, I have the same setup on my laptop but I cannot upload apps to my phone. When I try to install the app to the phone it shows up in avd manager as ??????? ????? Unknown, I've googled this and the general advice is to setup a script which I have tried but I get an error message saying path does not exist, when I try to kill the adb server it says no such command even though I am in root and can see the adb file in the sdk folder, I am completely lost here anyone help with this.....
Thanks in advance
Looks like you are running Linux on your laptop. Try these steps as your normal user:
If you haven't already set up the udev rules for your device, follow these steps:
1. sudo gedit /etc/udev/rules.d/51-android.rules
2. copy/paste this line into that rules file: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. sudo service udev restart
Then, restart the adb server:
cd </path/to/your>/android-sdk/tools directory
sudo ./adb kill-server
sudo ./adb start-server
If it's not there already, you can add the /path/to/your/android-sdk/tools to your $PATH variable so you don't need to cd to the directory and also won't have to use the ./ to use the adb command.
You may need to unplug/replug the USB cable to your phone after you do all this.

Categories

Resources