I want to use android on eclipse on Windows. I have installed Kies3 and my driver is updated. I enable USB debugging and the API of the project is the same as my devide version.
But when I want to run the project In android device chooser I get Target unknown. State offline and SerialNumber nnnnnnnnnnnnnnnn which is very strange.
Could you help me that when can the problem be?
Try the following methods:
Go to cmd, type adb kill-server and adb start-server;
Reboot your phone.
Restart Eclipse.
Related
I'm struggling with an issue connecting Android Studio to my Google Pixel 2.
When I plug my phone into my laptop, Android Studio now recognizes the physical device and shows 'Google Pixel 2' in the dropdown of devices to run the app on. When I go to run the app, it compiles without error but when it tries to install the app on my phone the connection between my phone and AS is lost (the device is no longer listed in the dropdown) and this error message is shown in the Run dialog:
06/12 17:08:35: Launching 'app' on Google Pixel 2.
Installation did not succeed.
The application could not be installed.
List of apks:
[0] '/home/kirk/Apps/xxxx/android/app/build/outputs/apk/debug/app-debug.apk'
Installation failed due to: 'device 'xxxxxxxx' not found'
Retry
Clicking the Retry link just results in it being launched in an emulator.
I've tried disconnecting and reconnecting the device, revoking the USB debugging authorisations then re-trusting my computer, as well as closing and re-opening Android Studio.
Any ideas?
Android Studio–>Preferences–>Build,Execution,Deployment–>Debugger–>“Use libusb backend”, select false–>Apply–>Ok
Sometimes ADB just need a restart.
adb kill-server
adb start-server
In my case I had a plugin to connect via wifi, like:
Android WIFI ADB
Try to uninstall this type of plugin then clean Android Studio on Invalidate Caches / Restart...
This happened to me when I was sharing Wi-Fi from my PC to the phone.
When I disconnected my phone from my PC's Wi-Fi, everything worked.
It could be an issue with ADB rather than Android Studio
I think it is problem with adb not with android studio I tried updating adb it worked for me. Try once
I have updated my mac mini os to Catalina. After that Android Studio and Xcode not detect connected devices. "adb devices" command not showing any devices.
But, in Android Studio, it detects my device (on troubleshoot mode). But, it was saying, not recognized as Android device. Usb debugging is already enabled. Need help on this Catalina issue.
So far I tried:
Xcode command line tools installed.
Xcode updated.
Android Studio updated.
Android SDK updated.
Tried connecting with different cables.
I think the problem is from the OS, when I see the console log. I see an error
adb#(null): AppleUSBHostUserClient::start: missing entitlement com.apple.appledfr.client
waiting for a patch from apple
For adb it started working again, after i tried to set up the sdk path again ,
export ANDROID_HOME=~/Library/Android/sdk
I did the "Revoke USB debugging authorizations" from the Developer options on the phone and run Xcode so it would install some updates.
Once I did that, it offered up the usual "did you want to allow debugging on this device" option, and everything was back to normal.
After Mac OSX is upgraded, then open Xcode to install the components. Then connect your android phone through USB rather than double type-c. After that, do the "Revoke USB debugging authorizations" from the Developer options on the phone. Then adb devices list will show the connected phone.
Using zsh, I added
ANDROID_HOME=~/Library/Android/sdk
to my .zprofile file (if you don't have one, just create it with touch .zprofile in your home directory) and rebooted.
1) go to and install www.android.com/filetransfer
2) then revoke the USB debugging authorizations on android device
3) make sure you are running the old bash (in Catalina), to do this: chsh -s /bin/bash
4) unplug Android device from USB cable
5) restart Mac Catalina
6) plug back in Android device
7) run terminal (bash)
8) adb devices
it should show up, note: I had tried to run the Android File Transfer app after installing it, but it never would run. With that said, it seems to try and run something when it detects the cable being plugged in. Disclaimer: I don't know if this will work for you, but these are the steps I ran through to get it to work for me
I have updated my Android Studio from v.0.6.1 to v.0.8.1.
Now adb cannot see my physical devices although the driver is installed properly (see screenshot)
Do you have any ideas?
Thanks in advance!
P.S. Android Debug Bridge version 1.0.31
When I reinstall IDE completely, I always have to edit ~/.android/android_usb.ini to add my devices USB VENDOR ID
Double check there are no updates required within the SDK Manager. If not, then go to Android Studio and then on the menu go to Tools > Android > Enable ADB Integration.
Also from the command line run adb devices and ensure that the device is listed there. I don't know what version of Android you have, but make sure USB debugging is turned on and I think since Jelly Bean a popup should appear on screen asking you to confirm that you want to allow the device to connect to the PC.
Hope this helps.
This is not AS problem. Try in terminal
adb kill-server
adb start-server
I just upgraded my Android device to 4.4.2 and now Eclipse will not be able to choose a running Android device when I want to run my project. The Android Device Chooser shows my device up with a serial number as "????????????" and Target as "unknown" and State as "??". Additionally, I have enabled Developer Options with USB Debugging.
what os are you using. i see that on my linux box with some devices. i normally kill adb and restart it as root and the devices shows up and works correctly. found that solution years ago on stack overflow or something like that. not sure if the same thing is needed with windows/osx. on linux, assuming adb is in your path:
$ killall adb
$ sudo adb devices
otherwise os you're trying to connect it to and the specific device information would probably be helpful in tracking it down.
I have a few suggestions. Try them in this order until it works.
Reboot the phone.
Try turning off and then back on "USB Debugging" on your phone (in Developer Options probably).
open cmd > go to the your Android SDK directory > type cd platform-tools > type ./adb kill-server > then finally type ./adb start-server
References:
Eclipse - Target "unknown" in Android device chooser
Android device chooser - My device seems offline
The solution for my device after updating was to completely uninstall the device driver from device manager and reinstalling it. I am using windows and my mobile was shown as Android Phone and not as Nexus 7. Home it helps someone.
I was developing an android application from Eclipse, connecting my Acer ICONIATAB A 500, with Android 3.0.1. And I did not have any problem.
Now I'm trying to developing the same application on Acer ICONIATAB A 501, with Android 3.2
and my ADB can't find the new device, while Windows can find it! I set in my tablet Debug USB option active, and I installed the appropriate driver on Windows.
I installed even the last Google USB driver (Rev. 7)
I tried to list the device find form adb with command
adb devices
from command line, but List of devices attached is empty.
What can i do?
execute these line
adb kill-server
adb start-server
if it is mobile device check that in settings, developers options , debugging mode is checked or not
You need to install LGUnitedMobileDriver package from the LG website, even though Windows 7 automatically installed USB drivers for the phone.
Try to update your Android-SDK on your computer (in Eclipse or whatever IDE you are using), this helped me solve a similar Problem.