i think this was because the option for usb debugging wasn't checked on the device
for micromax devices :
you need to download third party pc-suite like moborobo or mobogenie because micormax don't have official pc-suite & after installaion (without restarting) your mobile will be detected. :)
my device had disappeared from the adb devices list after connecting it to adb on another laptop.
i selected "charge only" on the phone and then re-enabled usb debugging.
that resolved the problem for me.
i'm on a mac and for some reason when i connected my device via usb there was a weird mount called usb-drivers which when i unmounted from finder, the androide device chooser instantly recognized my device.
use usbdeview, from here, http://www.nirsoft.net/utils/usb_devices_view.html
run as administrator.
disconnect your phone.
delete all the drivers associated with your phone. some will say android as well as the name and model of the phone.
plug your phone back in so that windows re-installs the drivers.
this worked for me, when the other solutions didn't.
i have an htc g2 with win 8 and it took me hours to get eclipse to recognize the device. i followed all of the advice above to no avail when i found this on http://forum.xda-developers.com/showthread.php?t=1964372:
now click with the right mouse button on computer, click manage. go to device manager. right click acer a700, click update driver software. choose "browe my computer for driver software". choose "let me pick from a list". click all devices or/and have disk.. go to c:\program files (x86)\android\android-sdk\extras\google\usb_driver\ and click the file under the 2 folders (android_winusb.inf) click on the first one and install.
substitute "android phone" under "other devices" for "acer a700" and use the android_winusb file under adt-bundle-windows-x86_64\sdk\extras\google\usb_driver. click "ok" when you get the scary prompt about windows becoming unstable and presto!
i had the same problem and solved this way: my phone is a sonyericsson xperia x8 and wasn't recognized by windows 7 (but it was by ubuntu). hence i figured out it was a driver problem.
0) pluged in my smartphone 1) right clicked on computer->manage->device manager 2) there was a yellow exclamation mark on one item named something like "semc husb"... double clicked on that item (that was actually related to the smarphone) and updated the drivers (previously downloaded from this page http://developer.sonymobile.com/downloads/drivers/sony-ericsson-x8-drivers/ and now everything works). i guess that you can find your proper dirvers via google if you have a different phone.
and , if your device is a sony ericsson xperia x8 with the original rom (2.1) or similar, then use:
<uses-sdk android:minsdkversion="7" android:targetsdkversion="17" />
in androidmanifest.xml file
i had to goto "settings->developer options->usb debugging". make sure usb debugging is turned on.
samsung galaxy s ii skyrocket
i had the same issue with sony experia z, that is because i'm running on windows 8 and apparently i need to download a driver for it.
as mentioned by stkhou, i check my device manager and saw the eclamation mark. which it was the model of my phone, to double check so i remove the usb and it dissapeard. so i plug it in again and the icon appears again.
so it's pretty sure the driver issue, so i have download it and install. after installation, run the android device chooser on eclipse again and it works for me.
i hope same for you.
here below i saved the links that might intrests someone who has sony issue. ;)
here are the list of available driver for sony devices:
one possible reason is to check android sdk manager and install google usb driver in extras folder if you have not installed it.
if none of the options work, i change the port and then enable usb debugging and it works fine.
i had problem seeing my android device, so when adb reported that none were present, i cycled power on my usb hub and voilà, it came back in adb and in eclipse ddms.
here is my checklist when my device is not shown:
- make sure "usb debugging is turned in setting>developer options.
- check status bar on your device. it tells you if your phone is connected as media device (mtp) or send images (ptp). my device is only listed when ptp is selected.
- turn of windows firewall.
- turn of any proxy programs ran on whole windows ports.
- and final solution to stop adb.exe from windows task manager and wait some seconds to restart automatically.
one thing to do is swap cables. i was using one that was only capable of charging!
okay... so i could never get my pendo pad to show up.. until i encountered this..
process android.process.acore has stopped..
yeah.. nothing to do with this issue right? ah ah but it lead me to mobilego. it's a desk application that lets you admin your device.. guess how.. by connecting via usb. yep and it does.. it installed everything on my windows box, and now eclipse has no problem seeing my pendo.
another alternative: on modern apple imac's, the usb port closest to the outside edge of the machine never works with adb, whereas all others work fine. i've seen this on two different imacs, possibly those are usb 1.0 ports (or something equally stupid) - or it's a general manufacturing defect.
plugging usb cables (new, old, high quality or cheap) into all other usb ports works fine, but plugging into that one fails adb
nb: plugging into that port works for file-transfer, etc - it's only adb that breaks.
in galaxy note 3 you need to enable the developer option. access the "about device" and click on the build number multiple time until a message appear which telling you that the developer option has been enabled. go back to general and there your go..the developer option has been enabled and select usb debugging option. this is for galaxy note 3 n9005 andriod 4.3.
my problem was with an old zte phone, i was ignoring the autorun.exe that kept popping up when i plugged in the phone. i finally ran the autorun software it installed zte drivers and the phone started showing up in adb devices.
the device was not showing up because of the following line in android manifest file---
i changed it to---
now it worked.
disable debugging mode and developer options in your phone.
start android device monitor.
now enable developer options and debugging mode in your phone.
you should be able to see your device listed after this in android device monitor. there after you should be able to see it under android device chooser.
i'm very late here, but if it helps someone... be sure you don´t have a conflict with your usb mode when attaching the cable. i pick "only charge" (sorry if it's not exact, i have an spanish terminal) but sometimes it changes to share net and the device dissapears from the list when running an app.
i was facing the android device not showing in "device chooser" so i try my best but no avail, at least i found that adb drivers should update, for this i did following steps 1. download driver from"http://forum.xda-developers.com/showthread.php?t=1161769" 2. device manager->> right click on adb ->> update driver ->>browse path of downloaded drivers then ok update successful. and i found my android device in "device chooser" try and getting relax
if you have a samsung device you need to install a special driver for development:
if you select android application in the debug as dialog, you should be able to attach the debugger to the device directly. make sure you run adb devices on your shell and see your device listed. if not, you will need to re-install the driver for the device. you can uninstall the drivers you have using usbdeview and then download and re-install the drivers until you see the serial number for the device listed when you run adb devices. - arunabh das
none of the other answers worked for me. for me the device registered with eclipse after i rebooted the phone. process for that is going to vary by phone model.
to install the android usb driver on windows 7 for the first time:
connect your android-powered device to your computer's usb port. right-click on computer from your desktop or windows explorer, and select manage. select devices in the left pane. locate and expand other device in the right pane. right-click the device name (such as nexus s) and select update driver software. this will launch the hardware update wizard. select browse my computer for driver software and click next. click browse and locate the usb driver folder. (the google usb driver is located in \extras\google\usb_driver.) click next to install the driver.
i had a similar problem...and my issue was related to using too high of an sdk....
uses-sdk android:minsdkversion="17" android:targetsdkversion="17"/
uses-sdk android:minsdkversion="8" android:targetsdkversion="17"
and my problem was solved.
using the android sdk manager may or may not actually install the google usb driver.
following the steps here: http://developer.android.com/sdk/oem-usb.html#installingdriver allowed eclipse to display the device.
this note from the android developer site is what worked for me:
enable usb debugging on your device. on most devices running android 3.2 or older, you can find the option under settings > applications > development. on android 4.0 and newer, it's in settings > developer options. note: on android 4.2 and newer, developer options is hidden by default. to make it available, go to settings > about phone and tap build number seven times. return to the previous screen to find developer options.
after following some of the steps in other answers here, as well as what is found here: adb driver for htc incredible, i had to issue two commands before my phone would show up.
finally, after those two commands would my device show up when i ran
from time to time, the adb process may get stuck (technical term there). when that happens, the above commands will not work. i have found that killing the adb process (look in for
adb.exe in the processes tab in task manager on windows, or kill the pid for adb under linux), and then use
generally fixes that problem.
also remember to set the 'deployment target selection mode' to manual (debug configurations -> target tab)
first, make sure that the android adb can "talk to" your device.
- open a windows command prompt (cmd.exe)/mac terminal.
- go to the folder (via
cd) where adb.exe is in, e.g, c:\android\android-sdk\platform-tools.
if your device is listed (serial number is displayed), go to the second check. otherwise, this means adb currently can't talk to your device. there're many reasons which can cause the problem, try:
- in your device, turn on "usb debugging mode" in settings -> application -> development.
- in your device, turn on "allow installation of non-market applications" in settings -> application -> development.
- restart your windows/mac.
- restart the android device.
- in windows/mac, reinstall device drivers.
second, make sure you set the "deployment target selection mode" to manual:
- in eclipse package explorer view, right click your project, select run as -> run configurations...
- in run configurations dialog, under android application. if your app doesn't exist, double click android application to create a new configuration, give it a suitable name (e.g. your app). make sure this configuration is selected.
- on the right area, for android tab, make sure your project displayed under project; for target tab, select "always prompt to select device" or "manual".
- click "apply" and close the run configurations dialog.
the next time when you run your app, you should see your list of devices.
your device still can't display? ok. third, make sure your "project build target" android version is supported in your device.
- check your device's android version. in your device, select settings->about device.
- check android version of your project. right click your project->properties->android->projectbuildtarget.
- make sure that it's not newer than your device's version.
- Android Device Chooser -- device not showing up
- Why is Eclipse's Android Device Chooser not showing my Android device?
- Just upgraded my OS X to Yosemite, Android Device Chooser not showing device - what to do?
- Android Device Chooser not showing my device but adb and Eclipse do
- Android device not showing up in ADB, tried all other solutions on stack overflow
- Android device not showing up in eclipse
- Android device not showing on adb anymore
- Android mobile device not showing in my eclipse browser
- Eclipse/Android Studio Device not showing up in Chooser Dialog
- Why is Eclipse's Android Device Chooser showing a fake emulator?
- Android Device Chooser not show my device in one device
- LogCat for Android Device in Eclipse not showing
- Android Device Window Chooser not working after updating device
- New Android device not showing on Eclipse's Debugger (Android Device Chooser)
- Online Device Not visible on Eclipse Android Device Chooser
- Eclipse Android Device not showing up | Can't find RNDIS driver
- My android virtual device is not showing contents
- Android Background is showing in the graphical layout but not on the device
- Physical device not showing up for Android Phonegap project created with Applaud plugin
- Android app in Eclipse: Edit text not showing on Graphical layout
- eclipse not showing Avd manager window and android project
- Eclipse - Target "unknown" in Android device chooser
- Android AVD not showing anything. only "ANDROID" in the middle of the screen
- What does the orange triangle in the target column of Android Device Chooser window mean?
- Error "AdbCommandRejectedException: device not found" in Eclipse using Android emulator
- DDMS Not Showing Threads From Device
- Android emulator not showing the app- it only shows the skin
- Android Device Monitor not opening
- Android How to create Intent Filter for custom file extension that does NOT make it part of a chooser for everything on the phone
- Android Device Monitor is not starting in Android Studio on MAC
More Query from same tag
- How do I create a text box on eclipse just for viewing in a scroll type menu?
- Scala: Eclipse access to environment variables in Ubuntu
- how to export war file with sql database table in eclipse
- Loop: This method must return a result of type boolean
- How to get the properties values those that are defined in the shell (bash) script file using Scala 2.11 code?
- how do I create templates for eclipse
- Importing Netbeans keymap to Eclipse
- How to force gradle to add dependencies to the module path instead of the class path in eclipse?
- Autocomplete in Aptana
- Update and Install problems with Eclipse
- How to retrieve programming language of current file in Eclipse plugins?
- How do I disable Tomcat request logging in Eclipse?
- Why wicket maven archetype isn't web?
- How to grant write permissions to all files in eclipse work space
- How do I parse a pseudo float number in Xtext grammar?
- Read Database Android SQLite
- Inserting block/braces in If-else statements using JDT
- How to stubb a private method call of my tested class
- Using a class inside an Interface file from another package
- How do I lock Run Configuration in Eclipse?
- Maven is suddenly throwing error, Truncated class file
- eclipse An internal error occurred during: "JSP Index Manager: Processing Resource Events". java.lang.NullPointerException
- Trying to change my font from my assets folder but i am getting error saying "The method setTypeface(Typeface) is undefined for the type Object"
- Is there a way to get eclipse code completion to filter options on text typed anywhere in a word rather than just the start?
- Android application stopped unexpectedly
- WCF service on localhost that works in browser not working in PhoneGap
- How do I retain git history and project location in eclipse on windows when moving from 2 drives to 1?
- Eclipse and Background Compile like Resharper in Visual Studio
- Egit Eclipse best practises (play framework 2,.0) project
- Length Cannot be resolved or is not a field