I'm running adb on ubuntu, and my app (that I'd like to test) on a Galaxy S3. Got my S3 in debugging mode, I've edited /lib/udev/rules.d/51.android and .android files, restarted adb, and my laptop, but no luck. Any ideas what I might be doing wrong?
Try this on command prompt:
sudo -s
adb kill-server
adb start-server
Some more things you can try as I often find this helpful.
Check the Data Card, it might have problem.
Plug the data card to another port on the system.
Related
I keep having an issue with the Android Studio ADB not recognizing my devices. So far, the only solution I've found is to do a complete reboot of my entire computer, which isn't practical. I'd like to be able to restart the ADB from terminal, because I have seen other posts on here that claim it will fix the issue. However, I can't figure out where to use the commands "adb kill-server", because doing it at the base directory returns a "command not recognized". Can somebody help me figure out how to navigate into Android from terminal and use the command? Or, does anybody have another solution to the original problem of Android Studio not recognizing my devices?
Thanks in advance! Sorry for the wordiness.
blackbelt:~ blackbelt$ adb kill-server
blackbelt:~ blackbelt$ adb start-server
works on Linux as well as on Mac. In my machine, adb is in PATH
"command not recognized". Can somebody help me figure out how to
navigate into Android from terminal and use the command? Or, does
anybody have another solution to the original problem of Android
Studio not recognizing my devices?
In your case adb is not declared in PATH. You can either export the PATH, or specify the full qualified path to adb in the command line. E.g.
blackbelt:~ blackbelt$ /path/to/platform-tools/adb kill-server
blackbelt:~ blackbelt$ /path/to/platform-tools/adb start-server
or
blackbelt:~ blackbelt$ ./adb kill-server
blackbelt:~ blackbelt$ ./adb start-server
if you are inside platform-tools
Well instead of doing it through command line, if you find that hard you can also do the same from android studio.
Go to tools -> Android -> Android device monitor . Then it will open the separate window where you can see all the devices or emulator attached to the process. On the left hand side below the Devices tab there will be and menu bar, you need to click on the drop down arrow which will give you the option to reset the adb. Here is the image for reference
If you are using windows try to update the device driver for your device make sure the adb is correctly installed. When you connect your device to system see if it is allowed to be used at the system.
if adb kill-server not responding. Find the process id (PID) by typing top in terminal and finding PID next to adb. Then type kill <PID>
For example, for me PID for adb was 70163. Then i typed kill 70163
Simply stop adb:
adb kill-server
Then you can start it again any time:
adb start-server
I bought a new Samsung Galaxy Tab GT-P6200 for developing android application. When I connect my tablet device to the system(with Ubuntu 11.04 OS and with Eclipse ), it doesn't recognize debugging mode even I enable debugging mode in the settings. It automatically connects to MTP-mode(Media Transfer Protocol), and I cannot view the folders in the sdcard. Someone please help me to connect my device in debugging mode.
Have you try restarting the adb server?
Open a Terminal, go to your android-sdk/platform-tools folder and execute:
./adb kill-server
then start it again with root access
sudo ./adb start-server
I remember I faced this problem before. You should try to following:
Check if you have install driver for it(in Help/Software Updates of eclispe)
Also, sudo ./adb kill-server sudo ./adb start-server check if it connected by sudo ./adb devices
Try with other USB port.
Hope it helps
I'm trying to debug an Application on a Xperia cellphone with Cyanogenmod installed, but it doesn't seem to recognize my cell phone. Also, adb seems to be gone, I followed http://developer.android.com/guide/developing/device.html the official guide, but when executing:
$./adb devices
on the plataform-tools/ directory the system doesn't recognize the device.
also I tried
$sudo ./adb devices
any ideas?
thanks to everyone for the help.!! I solved
the problem was that I needed to restart the adb server I did it like this:
$sudo ./adb kill-server
$sudo ./adb start-server
Is there any way to make a phone whose status is offline to online without replug the usb line?
Just copy an paste in notepad with a .bat extension.
Before that make sure your adb.exe is included in system path or alternatively replace the 'adb' with path to adb.exe, For example:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools\adb kill-server
#echo off
adb kill-server
adb start-server
adb devices
cls
echo "Android Debug Bridge Restated!!!"
pause
Disable and enable again USB debugging on the phone. Works most of the time. You can also try restarting the adb server on the desktop machine.
There's an 'adb reconnect' subcommand I hadn't noticed before today: it might only be in the newer versions of adb.
There's also a device-side version, but I don't quite see how the local machine can tell the device to do that without already being connected, so perhaps that's something you can execute in a device-side shell.
I followed the tutorial to set up ZTE tablet device for development. I am developing under Ubuntu 10.04.
After create the rules file: /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
After I plug in the ZTE tablet device with debugging enabled. I run command:
adb kill-server
adb start-server
adb devices
I got :
List of devices attached
???????????? no permissions
I thought may be it is because I did not restart adb as root. SO, I tried to restart adb as root, and I entered the command in my terminal:
sudo adb kill-server , but I got the message in terminal that "sudo: adb: command not found"
But if I enter command without "sudo", that's "adb kill-server" it works.
Is it because my path setting is wrong?????
I set the path under HOME/.bashrc, with :
export PATH=$PATH{}:/home/user/android-sdk-linux_x86/platform-tools:/home/user/android-sdk-linux_x86/platform-tools
Conclude all above, I got two problems:
the adb listed device has no permissions
I can not run adb as root
My questions:
Are the problems all because of my path setting is wrong?
Is it because ZTE tablet device is different from mobile device? Some tricks need to be done for tablet??
something else?
Where am I wrong?
P.S. Since I lost the USB cable shipped with the ZTE tablet, I use a NOKIA USB cable to connect the ZTE tablet with my development Ubuntu machine, could this also cause the above problems???? (With Nokia USB cable, I can still access the ZTE tablet file system anyhow)
Every thing goes fine after I run the command:
sudo -s
adb kill-server
adb start-server
adb devices
Then my ZTE tablet is shown.