Related
I'm running Android Studio Arctic Fox 2020.3.1 Patch 2 on my Dell XPS 13-9370 running Linux Ubuntu Ubuntu 20.04.3 LTS and when I try to connect either of my two Pixel 2s via USB, Studio fails to see them. I have USB debugging enabled and have tried setting Default USB configuration to both File transfer and PTP, to no effect. I also tried swapping USB cables and all the other steps described in the Android Studio Troubleshoot Device Connections.
I should mention that I have no problem connecting Studio to my Samsung Tab A running Android 11, or to any of the emulated devices. They all connect just fine. When I plug the USB cable into the Pixel 2s, I don't even get the permission prompt, even after revoking USB permissions.
I've been knocking my head against a wall on this for a couple of days now, trying out every relevant suggestion I've found on Stack Overflow. I used to have no problem connecting my two Pixel 2 devices up until a few days ago. The problem also occurs on the previous version of Android Studio. I thought it might have something to do with several new third-party apps I installed, but I forced stop them, rebooted the device and still the problem remains.
You can hard reset your devices because in some cases that works.
Otherwise, You can use the developer options wirelessly on your phone.
Just read this article for a step by step guide for how to do this.
Use Android device for development wirelessly
are you using same usb cable for other devices in which it is working ?
try this once - open developer option and select 'Select USB Configuration' . make it mtp and also check if usb debugging is turned on.
Instead of doing it with a cable you could do it wireless just install the plugin adb wifi rest all the instructions are given when you will install that plugin.
Android WiFi ADB
Steps to do this(in short)
Connect your device to your computer using a USB cable.
Then press the button picture of a button to be pressed on the toolbar and disconnect your USB once the plugin connects your device over WiFi.
You can now deploy, run and debug your device using your WiFi connection.
NOTE: Remember that your device and your computer have to be in the same WiFi connection.
Sometimes it happens for the USB connector manager of your operating system. You can uninstall the USB connector manager from your OS Device manager and then restart your laptop. I faced this issue several times and this solution worked for me.
Try to install Genymotion Emulator and Launch it first before running your app. I did it and it helped me and i think it will be work
I have Android Studio on Windows 8.1 and I want to run my android app on my Samsung Galaxy S7 phone.
Here are the details:
USB debugging in my phone is ON
adb version is 1.0.36
Under Device Manger -> Portable Devices -> My Phone, the status is 'The device is working properly'
I also installed Google USB driver in SDK Tools
My desktop can detect my phone since I can read and write files using Windows Explorer
I tried the following but still, adb devices still does not recognize my phone.
Tried USB Configuration MTP
Tried USB Configuration PTP
Tried using different USB cables
Tried restarting Android Studio before and after I plug my device to my desktop
Did I miss any configuration? Any help is appreciated!
Thanks!
I too had the same problem.
I tried the following and it worked.
Make sure Developer options and USB debugging is enabled on your device
Then on your Windows system.
Open device manager and locate your device's ADB Interface Driver
Right click and choose properties
Check in the general tab if your device is working properly
If it is not enabled then go to Driver tab and select enable
You may have to try enabling your device a few times(7-8)
If this works then you may see the below message on the General tab
This device is working properly.
You need to restart your computer before the changes you made to this device will take effect.
And that's how I made it work.
install drivers for your device and enable developer mode for your device
While the simple answer here is enable debug mode and install drivers, I think the answer should mention that if nothing works , do install google drivers. I stumbled on a video explaining the same, so adding the link here.
https://www.youtube.com/watch?v=asbkkV-IIZc
It helped fix my issue with oneplus device. Also, I could get the google usb drivers from android studio > sdk manager > sdk tools section.
Hoping to save someone else's time.
If you entered command adb devices in cmd and don't see your device ID, you can to open Windows Task Manager and close adb.exe task. Then you need to open again cmd and enter adb start-server and check devices again.
If you don't see your device ID after all then maybe problem in phone or drivers.
I found the answer here
I just need to install Samsung USB driver and it worked fine. I guess the Google USB driver did not work for me.
Also, I didn't know that I need to install a USB driver even if I can already read/ write files to my phone when I connect it to my desktop.
In Device Manager, I was looking at the wrong device (Portable Devices). I should have been looking at Other devices and there I can see that the Samsung phone has no drivers installed.
Thanks!
I had the same problem. Just try another USB port on your computer.
rebooting of the android device worked for me. Also, try to use the port USB 2.0
I was also facing the same issue on my MAC-OS. Restarting the MAC fixed the issue.
I also installed Android File Transfer to check if this was only a debugging issue or if it was an issue with the connected devices. Even AFT wasn't working so it was definitely not a debugging issue.
I also got this message on launching Studio after restarting the MAC.
sometimes windows firewall prohibit the adb.exe in platform-tolls folder
first check your phone and be sure about "usb debugging" is "on"
check that Default USB configuration is on "transferring files"
if you checked 1,2 but the problem is not solved you should reinstall platform-tools from "SDK manager" then "SDK tools" uncheck "Android SDK platform-tools" click apply then reinstall it by check "Android SDK platform-tools"
Android Studio 0.3.6
Fedora 18 3.11.7-100.fc18.x86_64
Nexus 5 Kitkat
Hello,
I have been using my Samsung Galaxy Tab 3 7.0 running Android 4.1.2 everything works fine with adb.
However, I have just bought a new Nexus 5 device, and when I do the following command adb devices it doesn't show my Nexus 5.
Under Android SDK Manager | Extras | Google USB Driver | status "Not compatiable with Linux"
Because I am running Fedora 18 if I need drivers what drivers for the USB do I need?
Because the Samsung works fine and I can deploy and run my apps, I think my setup is correct. So I am wondering if there is something wrong with my Nexus 5.
I have tried the following:
adb kill-server
adb start-server
Setting the Nexus 5 Camera PTP and media device MTP didn't work.
Many thanks for any suggestions,
I had a similar problem with my Nexus 4(Android version 4.4.2), it wasn't listed in adb devices.
Make sure USB debugging is enabled from device, and do the following on your PC:
Update Android SDK (Google USB Driver)
From PC Control Panel, System -> Device manager -> Right click Nexus 4 -> Update driver.
Set android-sdk-folder\extras\google\usb_driver as path to search, include subfolders checked.
If windows tells you that the driver is up to date, just uninstall the driver (right click on nexu4 -> uninstall driver) and start from step 2 again.
After that, open a cmd and type adb kill-server and then a adb devices, now it will include your device.
https://developer.android.com/studio/run/oem-usb.html
Follow these steps,
Enable Developer options in your device. To enable the developer mode, Settings->About phone, tap Build number option 7 times continuously
Go to Settings-> Developer options and Turn on USB debugging
Make sure you reconnected the device via USB and grant permission on the dialog that appears.
From the above steps it didn't work try this step, Go to Settings->Security and turn on Unknown Sources
What you need to do is this:
Settings | About Phone
Scroll to the bottom to build number.
Tap on build number about 7 times. Each time you will get a popup message saying you are x steps away from being a developer
When you get to the final step you will get a message saying now you are a developer
Go back into settings and you will see a new setting Developer options there you will see a lot of options for developers. Enable USB debugging
Re-connect you phone to the usb, and you should see you device under adb devices.
I hope this answer helps someone else.
This simple steps worked for me, I debug on my Nexus 5 and 5X devices on Windows 8.1.
The steps to follow are these:
1) Enable from Developers Options the Debug USB Mode
2) Unplug the device from the computer
3.1) Go to Settings → Storage, in the ActionBar, click the option menu and choose USB computer connection.
3.2) If you didn't find the 3.1) option then go to Settings → Developers Options → Select USB Configuration.
4) Select Camera (PTP) connection.
5) Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection, or something like that.
6) If it doesn't work try to toggle the Debug USB Mode in the Developers Options
Finally, you should see it now in the DDMS and voilà.
My windows solution:
Go here and download and unzip to an easy location:
http://developer.android.com/sdk/win-usb.html#top
Right click 'My Computer' or 'Computer'
Select properties
Select Device manager
Look for your device. It should have a yellow mark above it.
Click 'update driver software'.
select browse my computer for driver software.
select the usb_driver folder you saved earlier.
install it
and wala. magic.
For those who are still frustrated, if you are using the experimental ART runtime, try switching back to dalvik (in developer options on device)
Here is simple solution for Windows 7 and Nexus 5 on Android 5.
Download the Nexus 5 Drivers from http://androidhost.org/jelry
Extract the zip contents and place all files in a single folder on your desktop.
Connect your device to your computer.
Launch the Device Manager on your PC.
Now you should see the Nexus 5 listed in the hardware list.
Right-click the ‘Nexus 5′ line and then click on Update Driver Software.
Next, click the ‘browse my computer’ option.
In the new window click on ‘Browse…’ button.
Go to folder unzipped at step 2. Select the folder where you extract the USB Drivers. Click Next. – make sure to tick the subfolder box too.
Now, the Windows installer will search for Nexus 5 drivers, click Install when asked for permission.
Wait for the process to complete and then check the Device Manager list to confirm that the installation was successful.
Original: http://www.android.gs/download-and-install-google-nexus-5-usb-drivers-adb-fastboot/
Note: do not forget to enable USB debugging on your device :)
Something nobody has mentioned yet:
Some cables do NOT support data. I was sitting here wondering why my Nexus 5 was refusing to show up on OSX. It turned out I was using a cable that didn't support data.
I swapped to a different cable which did support it, and suddenly I was able to use USB debugging.
If anyone is trying to connect Nexus 5 to a formatted Windows XP then follow these steps:
Download and install media transfer protocol porting kit:
MTP porting kit
Download and install WMFDistributable-11 for XP:
WMFDist-11 XP
Download and install LG United Mobile Driver v3.10.1:
stackoverflow is not allowing to share more than 2 links, please google this.
Connect your device.
Go to Device Management
Right click on Nexus 5 and click Update Driver
Select Yes this time only
Select Install Software Automatically
Wait for sometime.. and enjoy transferring files
ADB and driver versions matter. The newer the device, the lower the chances of an older version ADB to work correctly.
Apps using their own ADB copy need to be updated or at least have their ADB updated manually.
When installing Helium / Carbon for instance, it uses an old / incomplete ADB. Newer devices might not link to the ADB server for this very reason.
What I'm writing here should work for any future devices on Windows and possibly *nix OSes.
First the systems must be prepared.
on Android:
activate developer mode, either from an app (like Helium, when prompted) or by accessing the about phone section, taping build number until the developer mode unlocks
in developer settings enable USB debugging
in security settings allow unknown sources
(when connected with USB cable) set USB connectivity to PTP mode (camera device, if so labeled)
in Windows:
uninstall older USB driver (with file removal) if there is one, but only when the device is connected and in developer mode, otherwise
that particular device won't be listed
install latest USB driver after the device has been plugged in and developer mode is active, the device will be listed as unknown or other in Device Manager; the drivers can be downloaded separately from Google Android support site, these are the same as vendor drivers, with only fewer ID's in inf file making the driver not being recognized for all Android devices
if the driver does not recognise the device, no problem, install it generically: Manual Install > Show All Devices > Have Disk > pick inf location of the Android USB driver and from the list select Android ADB Interface; there's not need to edit the inf by adding hardware ids, the end result is the same
each of the modes, PTP and MTP will have their own driver entry, so if the device asks for MTP, the same driver installation procedure must be followed, again
Once these steps are/were previously done correctly, adb must be tested.
If Android SDK was installed previously, open a command prompt where adb.exe is
and test the listing of the device.
adb start-server
IMPORTANT NOTE: This command will prompt the device to allow the communication between the computer it's been linked to on the first run. The prompt will also list an RSA key specific to the PC in question. Without this prompt on start-server, ADB will NOT work! Nor will any application relying on ADB.
adb devices
Must list the device(s). If the list is empty, and most likely the RSA prompt did not occur, then no communication will work. If the list is empty the current ADB (and SDK) must be updated or installed fresh (in the case of apps bringing in their own ADB runtime, like Helium / Carbon).
In the case of applications that do bring their own ADB, if the version is old, and these apps insist in using it instead of the SDK one, these files need to be replaced with the latest ones from Android SDK. Plain and simple copy & paste.
As for Android SDK, the only required packages to be installed are SDK Tools and Platform-tools. There, ADB.exe will need some support libraries, on Windows these files are AdbWinApi.dll and AdbWinUsbApi.dll. After all is done, the SDK can be uninstalled from SDK Manager while being able to retain the ADB tool if this is the only runtime used, depending on the case in question.
After doing all steps like enable debug, ... I had to put a sim card and reboot the phone
Solution for Windows 7 and Nexus 5 (should be applicable for any Nexus device):
I figured out that my system was installing the Nexus 5 default driver for windows automatically the moment I was connecting my Nexus 5 to my system through USB. So uninstalling the default driver was in vain and it gets installed automatically anyways.Moreover if you uninstall the default driver, you won't be able to locate Nexus 5 under Devices in Computer Management. So here is what i did and worked for me!
Computer-->right Click-->Manage-->Device Manager-->Portable Device-->Nexus 5-->Update Driver Software
Choose 'Browse my computer for driver software'
1.Make sure to give this location: %APPDATA%\Local\Android\sdk\extras\google\usb_driver
Click Next and you are done.
I have suffered the same issue and was able to solve it by simply changing on my Android device (Nexus 5X) in Developer options > Select USB Configuration to RNDIS (USB Ethernet)
For those trying to connect their android phone in adb with no luck and have tried every USB configuration (MTP, PTP, RNDIS). It is worthing noting that in my case with my Nexus 5X on Windows 7 I successfully connected the phone to adb only by choosing the Charging USB Configuration. With any other configuration (MTP, PTP, ...) it doesn't work.
USB Driver: Google USB Driver v11
ADB Version: Android Debug Bridge version 1.0.39
Madx's answer is a strong hint. Now I can make MTP work for my Ubuntu 20 and Nexus 5X (Android 8) device. MTP is an easy solution in Windows for smartphone users. However, to me and many Ubuntu/Linux users, current Ubuntu/Linux MTP tools "LOOK" messy and unstable for Android devices, e.g. No folder is shown for android phone in Nautilus.
Delving deeper I find it might be a security enhancement done by GOOGLE in the Android device/phone side. Direct internal data access remains a privilege for the developers. And one needs to set/reset MTP as a developer for Android device in order to make Ubuntu MTP tools work. There is nothing wrong with Ubuntu/Linux MTP tools.
The steps for MTP data access are an extension to Madx's answer:
(For Android device) Enable from Developers Options the Debug USB Mode.
Unplug the device from the computer.
3.1) Go to Settings → Storage, in the ActionBar, click the option menu and choose USB computer connection.
3.2) If you didn't find the 3.1) option then go to Settings → Developers Options → Select USB Configuration.
4.1) Select MTP connection.
4.2) Select Camera (PTP) connection.
4.3) Select MTP connection again. (This refreshs GOOGLE MTP protocol stack, I guess)
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection, or something like that.
If it doesn't work try to toggle the Debug USB Mode in the Developers Options
And now file folders are shown up for N5X device in Nautilus.
Are these too much? There might be a bug in Android MTP implementation, and 4.2) & 4.3) are steps to WAKE Up Android MTP stack:-)
As a kind reminder, Windows and FTP are the last resorts for MTP.
Try executing :
sudo ./adb kill-server
sudo ./adb start-server
sudo ./adb devices
In my case:
The phone was connected as a media device.
Clicked on that message and got a menu. "USB computer connection"
In that menu chose to connect it as a camera (for devices that do not support MTP)
And then it worked.
Oh boy, I spent 3 hours for this simple thing and tried combination of above instructions.If it doesnt work for you, just try several combinations of above instructions and it will. I am on windows 7 and nexus 5. Issue I had was when I try to install driver from the google usb folder, windows 7 fails to install. Here are my steps:
-first uninstall all nexus drivers on windows 7. connect with USB cable, go to device manager and uninstall the driver; unplug the cable and repeat until no drivers are found and nexus shows up under "other devices" in device manager. I also configured nexus device as camera (PTP)
-follow #Dharani Kumar instructions. They make appropriate configuration changes for nexus device
-follow #Harshit Rathi instructions. They will ensure eclipse can show the device when windows detects the device
-unplug and replug the USB cable after a minute. Now you should see a pop up on nexus device. click it so that windows 7 will allow installing the driver from your local system. if you dont see this, restart your device or pc
-follow #Rick's instructions.you can download USB driver as listed by #jimbob
If you still have a problem, re read this entire thread and go from there (I spent hours on other web sites; those bits and pieces didnt help)
Go here and download and unzip to an easy location:
http://developer.android.com/sdk/win-usb.html#top
Download and install
I had the same problem, USB debugging enabled, device showing up in windows but I never got the question about RSA fingerprint when I connected my Nexus (6) device, nor did it show up in the Android Device Manager.
BUT
In the windows device manager I did have an entry saying it was an android device and Composite ADB interface etc. Still didn't work.
When I tried the previous tips about manually updating the drivers, Windows 8.1 just responded that "Windows has determined that the driver software for your device is up to date" this was not true. Looking at the driver details I saw that the driver was published by "ClockworkMod". I realized this must be because I had installed the Helium app sometime last year. So I uninstalled that, still had the same problem. Checked again, this time it was indeed google drivers, but version 7 published in 2012 (and not version 11 published 2014). I uninstalled these AS WELL and then tried the trick of reinstalling the driver from the SDK located in:
%localappdata%\Android\sdk\extras\google\usb_driver
Now when I replugged my device it finally works and can be debugged with Android Studio.
Indeed a driver problem.
Answer by Rick and MadX is the right way to do the steps (Thumbs Up for the answer)
In my case I am using
Akcess USB Type C Data Sync Cable For Nexus 5x, 5P - White
As Nexus 5x do not supply type C to usb cable I purchased it from some vendor.
Having the same issue. What I am doing stupidly is:-
I am connecting the cable in wrong way. After I reconnect it from upside down its working for me.
I might think that some of the Cables do not support debuggable. But its in my case.
This(Image) is my case the Type C should be as USB side symbol. A stupid solution, but work for me
With the new update to 4.2.2 to my Galaxy Nexus and Nexus 7, I can't find both my devices under adb.
These are the steps I took:
Updated to 4.2.2
Updated ADT and SDK through the SDK Manager
Checked ADB version, it's at 1.0.31
Restarted PC and Tablet and Phone numerous times
When I run adb devices, it's just blank. I have the same issue on Windows 8 and on Ubuntu 12.10, but on Ubuntu it shows my device and it says offline.
Are there any other steps I can take?
From the adb docs
When you connect a device running Android 4.2.2 or higher to your
computer, the system shows a dialog asking whether to accept an RSA
key that allows debugging through this computer. This security
mechanism protects user devices because it ensures that USB debugging
and other adb commands cannot be executed unless you're able to unlock
the device and acknowledge the dialog. This requires that you have adb
version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher)
in order to debug on a device running Android 4.2.2 or higher
So, unplug, wait, replug in the cable, and hit ok (on modal dialog that appears on your device)
If you hit cancel, the device will show up as offline via adb devices
Try pre-installing the drivers for your devices. Make sure, under Windows, that your device is recognized in the System control panel first.
I use Windows 7 and my Galaxy Nexus wouldn't be recognized by the system until I installed the device drivers before plugging them in. From the comments, this works on Windows 8 as well.
Galaxy Nexus drivers
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#
Goto Manual & Drivers > Software
Nexus 7
http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
Just though Id share my experience, I had -
Unplugged and re plugged in the device
Installed the correct platform tools
Installed the correct Android bridge Turned USB debugging on and off
and on and off an...
Tried WiFi but it said it was offline
etc. etc.
What fixed it for me was changing the device connection from Mass Storage to MTP. To do so, with the phone unplugged you go into -
"Settings" -> "Storage" -> Click the menu Button -> "USB computer
connection" -> "Media device (MTP)"
Hope this helps some one from going crazy!
Thanks,
Ash.
I tried everything mentioned here and in other posts. It wasn't the cable, the USB port, rebooting the PC or Nexus 7, killing and starting adb or enabling/disabling USB Debugging.
It was due to the 4.2.2 OTA update, I simply replaced the \platform-tools\ folder, as described here: Android ADB device offline, can't issue commands
Download the updated platform-tools: http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip
adb wait-for-device
works for me. Just unplug your usb device, run this command, and while it's waiting, plug your device in, then it will just work. :)
Here is what I did (Galaxy S4 4.2.2):
go to Settings => about this device => click several times on "Version number", that is to say something like "JDQ39.I9505XXBHYTGKDD" (not android version or anything else) ; here you will see that Google or Samsung have a lot of humour as you have to click until multiple times until having a toast displaying "You are at few clicks from being a developer" ; after something like 10 clicks, you have a toast "You are a developer"
Go "Development options" (in the "More" tab (rigjt tab of settings menu)) ; be sure that "USB debugging" is checked.
And it works ! Eclipse can see your S4(or any other device) 4.2.2 !
I had this problem today and fixed it by rebooting the Tab2 while leaving it plugged into the laptop/eclipse
Check if you have installed android-adb-tools in Ubuntu. If you do, the adb tool may be old. Uninstall and make an alias to the latest adb tool you download with the ADB plugin. To check the adb version do "adb version" if it's 1.0.29 is the old, the latest and working for Android 4.2.2 is 1.0.31.
I made a lot of stuff until i realized this.
going to Developer Options and checking USB Debugging solved it for me
My solution used on cm10.1 nightly build on droid bionic, was after updating the newest usb drivers, using the Mass storage option (instead of the MTP option for USB computer connection), then unchecking and rechecking in developer options, "ADB over network" option. Then it did the RSA pop up dialog.
For me the best solution was:
Update the Android SDK via the SDK-Manager. Removing the '.android' folder in my usr directory ( Windows 7 ) and re-plugging the device back in. Worked flawlessly due to the ADB RSA key issue. I had an older version of ADB that I stashed into c:\windows\system32\ due to not wanting to install an entire freakin SDK when all I wanted was a command prompt. Good ol' Google, the new Microsoft.
You may use an old version of adb.exe. Update platform-tools.
You may have to set a new path to adb.exe as well.
In case it helps someone else arriving here, I had this problem with a ZTE phone.
I tried installing the driver based on the offical list here but in Device Manager the driver was marked as not installed correctly.
In the end I found the way to make this work was:
Press Menu Button
Choose "Connect to PC"
Choose "Default connect type"
Choose "Install Driver"
Plug in phone and on PC select option to install the driver
Then change "Default connect type" to "PC software"
After doing this I was able to do:
adb kill-server
adb start-server
adb devices
and view my device.
It's working on windows 8 using Android 4.4.2
Reset your phone,
go to setting->about phone-> seven time click on build number.
go to back and go to developer options check USB debugging.
go to windows 8 start menu click on profile picture and click change profile picture.
Select devices and on Download over metered connections.
Connect your phone via cable your PC and wait.
I am not able to resolve this simple issue.
I am trying to connect my device to Eclipse via USB cable.
On my PC, I have installed Eclipse and the Android SDK and running the program on the emulator is working fine.
I have downloaded and installed Samsung Kies on my PC. It shows my device if connected via USB to the PC.
But I dont know how to connect the device with the emulator.
Connect means, I want to run the Eclipse code on my device instead of emulator. I am using Samsung Galaxy Ace GT-S5830i. Please help me out to resolve this issue.
Comment is lack of formatting so i add an answer.
Check if your computer had your phone driver. I assume that your use Windows. Open Device Manager
At a command prompt, in the Start Search box, or in the Run box, type the following command: mmc devmgmt.msc
. Other ways : check link
If you find your phone name or ADB Interface so you got driver. Try to restart DDMS or restart your Eclipse.
If you don't find your device or see something Other device with yellow question mark so try to install driver by browsing on your phone to Settings - Developer Options - Enable developer option - Enable USB debugging - Plug your phone to computer. Windows will ask you to install driver.
3, Update Google USB driver in Android SDK Manager (in Eclipse) or search Samsung Galaxy Ace GT-S5830i driver
4.Some weird case i got on some device.
Nexus S: disable Developer option. Restart phone. Enable again. Windows ask to install driver or you will see it in Eclipse.
HTC phone or Samsung : change Connectivity Option on phone to Charge only (Swipe status bar. Check notifications displayed). Some phone set it to some kind of Sync data so Windows can not recognize device.
I think your emulator is in Automatic. You can change that to Manual.
Try this,
Step 1
Go to Run Configuration
You can see three Columns Android,Target and Common.
Step2
Select the Target
Step 3
Choose Always prompt to pick device.Click Ok
Step 4
Now run your project you should see the emulator and your device. Select your device and click ok.
Hope it helps.
Source.
Troubleshooting
This all sounds very straightforward, but there are countless quirks and hard-to-diagnose problems that can make connecting a device much more difficult than it sounds. In this section, we'll run through a checklist of things to try when your device isn't registering.
Check that USB Debugging is enabled. This setting can inadvertently (and perhaps even automatically) change when you plug/unplug your device from your machine, or when you reboot your phone.
Check your device while it's connected to your machine. Is it asking you to choose between different modes? Some phones have a 'charge only' mode that can prevent Eclipse from recognizing the device.
Choose a connection type
Make sure you don't have an Android Virtual Device running in the background.
Could there be a problem with the USB cable? If you have a spare cable to hand, plug it in to rule out a fault with the cable itself.
Double-check you're running the correct driver. Even if you are, some devices have all the required software pre-installed (for example, HTC Sync) and downloading drivers from another location can muddy the waters. If this might be the case with your device, try uninstalling the driver from your machine and reinstalling the software from your device's memory.
Does the driver require supporting software? Samsung Kies on Windows requires .Net Framework 3.5 SP1 or above, for example. This is usually installed along with the driver, but there's no guarantee.
Running the Android Debug Monitor tool (monitor.bat) has been known to kickstart Eclipse into recognizing a new device. Connect your device, locate monitor.bat (android-sdks/tools/monitor.bat) and double-click to open. This will open the Android Debug Monitor, a stand-alone debugging tool that lists connected devices.
Android Debug Monitor
A running adb.exe process can interfere with the connection. Close Eclipse, and open the Task Manager by pressing CTRL, Shift and Esc. Find the adb.exe process and kill it. Launch Eclipse and try again.
Check that your 'Project Build Target' is compatible with the Android version on your device. You can check what version of Android your device is running by opening 'Settings' and selecting 'About Phone,' followed by the 'Software information' option if available. If you need a reminder of your project's build target, ensure the project is selected in Eclipse's 'Package Explorer,' open the 'Project' menu and select 'Properties.' If the 'Android' tab isn't selected by default, open it and the Build Target will be displayed.
Have you enabled USB debugging in your device?? You can find it in your device
Settings -> Developer Options -> USB Debugging.
The android app you have created will be a .apk file, generated by eclipse, during a successful Run. Find the .apk file from the eclipse project explorer or by tracing your workspace. Copy the .apk file to your memory card (via USB or a card reader) and install it.
You should also enable the "Unknown Sources" option under "Security" of your Android device.
If you have required options enabled on your phone (USB Debugging and Unknown Sources) you can try do this. On your computer open command console. Using cd navigate to your android sdk installation folder. Go to platform-tools. You should have there adb file. Run this
./adb kill-server
and then
./adb start-server
Then check plugged devices
./adb devices
First, you are not connecting device with emulator. What you want is eclipse to identify your device and use it for development.
Everything about using devices for android development is given in official documentation.
You have to put the phone in 'debug' mode - I don't have the instructions handy (but you can search here or on the android site for the info you need).
Also check for THIS.
Try right clicking the project -->Run As --> Run Configurations then select target and choose always prompt
On your device turn on debug mode
Now try running project
I am assuming you don't mean connecting the device with the emulator but connecting the device to your computer so you can debug it and run applications directly from Eclipse to the device. In which case KIES by Samsung will not help you at all. What you need is the Android USB Drivers provided in the Extras tab in SDK. Sometimes the installation will bug up because you didn't run SDK manager as an administrator so make sure you do that. When all of this is done make sure your device is unconnected to your computer and then reconnect it after the drivers are installed. You should be prompted with a new device installation wizard which you must accept. Additionally, you should have debugging enabled on your device, and as an extra step you can setup launching as a manual configuration but it is not needed.
To enable device debugging
Settings -> Developer Options -> USB Debugging.
For more information visit here
BTW : If the Google USB Drivers don't work you might need to install the specific Samsung drivers which are located here
Goto -> Setting -> Application -> Development -> USB Debugging
Enable it and try.
I know this is a little old, but I was having the same issue. I tried all the options of setting usb debugging (off), disconnecting, restarting phone, usb debugging (on), connecting the phone and it just wouldn't connect.
I ended up installing the latest version of Kies on my machine and added the Unified option at the end of the installer and I then the phone would connect. (Not sure i needed the unified option) but it worked for me.
I tried all the above but it didn't helped me. I did couple of things additionally
Since my mobile device is Android, I unchecked Unified option from Kies installer. This is the crucial thing that helped me solve my problem
I restarted my mobile phone.