I am using ubuntu Linux 10.04 Pc in that my Samsung Galaxy 7\" (GT-P6210) homeycomb 3.2 is not detecting for development its showing in ecl
Just stop and start adb server as root. Permissions issue will go away. Also udev step can be skipped.
Maybe adding the vendor ID in ~/.android/adb_usb.ini
would help?
Add a line with just 0x<!!!Your Vendor ID here!!!>
, then run adb kill-server
and adb start-server
.
See this answer here: https://askubuntu.com/a/341696/387779.
It just saved me after nights of searching/testing/editing/pluging in and out and in again... so I thought it might be worth sharing. Thanks to Uygar Y for his answer.
I am using Ubuntu, what I did is killing and restarting the ADB server with a sudo privilege.
sudo adb kill-server
sudo adb start-server
I'm having the same problem. Strangely, I can sometimes get the device to list correctly, but other times, it just won't work. Restarting my Linux laptop resolves the issue. What a pain!!
Today, I discovered that if I suspend my laptop, then turn it back on, it detects the device correctly again! That really beats restarting the OS.
Try this way, 1.Close Eclipse (IDE) first. 2.Execute this command on terminal " adb kill-server" 3.Now connect device to system wait, 10-20 seconds. 4.Execute this command on terminal " adb start-server", Check device status with "adb devices " command. 5 .Now open eclipse.
If, when you run adb devices
, you see ????????????
in the list of devices, try stopping (adb kill-server
) and restarting (adb start-server
) the adb
daemon.
Note that Samsung 04E8
is not a valid entry in 51-android.rules
for udev
. The correct line is:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Also, make sure that you update the udev
daemon after making this rules file change (sudo restart udev
).