I am new to mac and trying to use various Android devices for development. Everything was working fine till today when Android devices simply wont show up in DDMS view in eclipse. I have tried to use Terminal to look up connected Android devices using:
~adb devices
Device list comes up empty. Emulator shows up fine in the DDMS view as well as in the device list from command line.
I have tried the following:
Disconnected the device from the computer.
Restart the computer.
Restart the device.
Connected the device.
adb kill-server, adb start-server
Nothing seems to work. Any advice will be much appreciated.
Firstly ensure that your device is connected in "Charge Only" mode, so that the sd-card is not mounted on your local system while testing.
Next, if you're on Ubunutu, as mentioned on the Android Dev website here, you need to set up the device for development to see it in the list.
If you're developing on Ubuntu Linux, you need to add a udev rules
file that contains a USB configuration for each type of device you
want to use for development. In the rules file, each device
manufacturer is identified by a unique vendor ID, as specified by the
ATTR{idVendor} property.
EDIT: So you're on a mac, then a little lookup throws this SO question up. According to the post, this was the work-around:
ADB on Mac OS X stops recognizing the attached device after installing
EasyTether driver. Use kextload/kextunload to unload from memory the
EasyTetherUSBEthernet.kext kernel extension manually. It is in
/System/Library/Extensions/
Start USB debugging(in settings>applications>developer options) on device first.
And still there is problem, try following link.
http://developer.android.com/tools/device.html
It helped me to detect my Micromax Canvas Hd
Run any project in Emulator.While running the Project you can see the device in DDMS.
Related
I am just getting started in Android development, and am trying to get Eclipse (running on Windows 7) to recognise my phone so that I can use it for debugging. However, my phone does not seem to be recongised by Eclipse or by running "adb devices" from a command line.
Here's what I've tried:
I've tried both MTP (media device) and PTP (camera) transfer modes (similar questions on Stack Overflow have been resolved by using PTP).
I've ensured that USB debugging is turned on in my phone's settings.
I've manually installed a driver in Device Manager, by choosing "Update Driver Software" and selecting the .inf file in sdk\extras\google\usb_driver (which I had to modify by hand to include my device).
I've tried a Nexus 4 phone, a Nexus 7 tablet, and a Motorola Moto G phone. Behaviour is identical for all three devices.
I've tried the "Universal ADB driver", in case it behaves differently to the Google driver, but it doesn't behave any differently.
I've rebooted, I've reinstalled drivers, I've tried adb kill-server followed by adb start-server, etc.
No matter what combinations of the above I try, "adb devices" lists nothing. When I look in the Windows Device Manager, I can see "Android Composite ADB Interface" listed under the "Android Device" node, so I believe I have installed the driver correctly. I am logged in as an Administrator, so it's not a permissions thing either. I've tried every answer to every single similar question on Stack Overflow, but nothing works. I've been pulling my hair out all day and am close to running out of hair... any ideas appreciated.
EDIT: It just occurred to me what could be causing this. I am running 64-bit Windows 7, but 32-bit Java. Because I have 32-bit Java installed on my PC, I installed the 32-bit SDK. Would that explain this behaviour? Should I be running 64-bit Java? The only reason why I didn't is because 32-bit Java is installed by my company's group policy...
EDIT2: I have now noticed that when I plug an Android device in, and look at its Device ID in Device Manager, the device ID does not end in "&MI_01". When I plug the device into another Windows 7 PC, the device ID does end in "&MI_01". I believe this is why "adb devices" is not able to detect the device. Any idea why one PC would see a different device ID to another, with the only difference being the "&MI_01"?
Did you install your phone USB-driver?
and can you check it on device manager is installed or not? you can download your usb driver from yur phone company website.
After you install your phone usb driver , I think the problem is solved
I think the main reason is because the computer does not recognize your phone as below 1 device used to debug code, even usb device.
You can try to do the following:
- Turn up the window update
- Uninstall driver for usb connection from your phone to your computer
- Go to the homepage of the mobile device, download driver for usb connection to the computer and then reinstall the driver
Try Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Download
After downloading extract .rar file into a folder.
Go to Device Manager, right click on Android phone and click to update driver. On next screen , give path of extracted folder and install it.
You can install with msi file also. Download .msi
Finally found the answer. I was missing a file called usb.inf from C:\Windows\inf. Not sure how on earth files just go missing from yours Windows directory...
Before asking my question, I have looked through a few threads that share the same problem as me and have tried all the given solution with no success. I am from Malaysia.
I cannot get my device to be detected to test my app on my phone. I have checked both the "Unknown sources" and "USB debugging" settings in my phone. I am using eclipse. But if I create a random virtual device, my app is able to run there.
Okay so I am using a Motorola Atrix 2. And I'm using Windows 8 Pro 64 bit
I have downloaded android SDK bundle from here : http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
I have also tried downloading the latest driver with no success. I have also added this line in the manifest android:debuggable="true"
I have tried both as a mass storage device and a media transferring device.
I would appreciate any help a lot because as of now, I cannot progress further into developing an android app and that saddens me. :(
I have attached a picture of which my android phone should be detected in the window, but as you can see, none.
https://pbs.twimg.com/media/BJu1XSgCYAEGCUd.jpg:large
go to /your-android-sdk-directory/platform-tools using command prompt.
type
adb kill-server
adb start-server
adb devices
n see whether ur device is detected now or not...
Note: if you're using a Linux machine then put ./ before adb
Install proper drivers for your adb devices, from Android-SDK archive or Motorola site.
If you are on Windows machine, go to the device manager find your device, and select folder with drivers for it.
Open you windows os's explorer, have a look at the process, if there two or more process hold your adb, try to exits the process
Check that the android:minSdkVersion is lower or equal to the Version running on the phone. If it is higher it wont show on "Android Device Chooser"
Install and run programs/drivers with admin rights.
Have you installed Motorola Device Manager?
When debugging Samsung and HTC devices I got it to work by installing that kind of software (for syncing the devices to the computer).
Download from the following: ABD Universal Driver
and install it. Make sure you have your device plugged in before installing and make sure you are on USB debug mode on the phone settings.
I am new to Android. I can't get the application to run on real device. I'm using Eclipse.
I followed as is said in the android developer forum but eclipse AVD is not finding any usb connected device. I enabled usb debuging in my mobile and set android:debuggable="true" in manifest file but Eclipse is not getting the device connected.
Did your PC recognize you phone device?In other words,did you install driver correctly?
Probably there is only one point you're missing. According to http://developer.android.com/tools/device.html you have to install usb driver for adb (if you are developing on windows) or you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development (if you are developing on Ubuntu Linux)
Before testing your application on real device please check your device is visible in Running Devices or not.If it is not visible simply do one thing install PdaNet on your desktop computer it will detect driver for the respective phone and install it.You can get it here
see this url: http://creandroid.blogspot.com/2013/10/del-eclipse-un-dispositivo-android.html
OR
http://developer.android.com/tools/device.html
IN thoses link is how to run aplications direct in real device
My problem is that adb devices does not detect my galaxy ace (s5830) using Ubuntu 12.04,
I tried everything but still not working.
Can help me where fault.
I have installed oracle sdk 1.7, last android sdk and I have created the rule 51-android.rules with permissions a+r
I had the same problem. Despite the rules file my device was not getting detected.
I did the following:
Restarted my device
Connected as "Charge only" (an HTC device).
The device was detected and I was able to install the app.
Do the following things
Download Kies for Samsung Smart Phone
Restart eclipse
In DDMS section, go windows->Show View->Devices, then click small down arrow(View Menu) and click on Reset ADB. Then it should work properly...
Android uses Java 1.6, so upgrading to 1.7 wasn't necessary.
Did you really use the Samsung vendor id 04e8 for your udev rules? And did you set debugging "on" on your actual device? Do you have any tethering app on your device (that makes use of adb)? Some do.
Also you need to restart your terminal window (or restart Eclipse) for your udev rules to be loaded for the first time, but I assume you did that already.
Also for good measure, you should restart your device as well.
If you're really desperate to get this working, you could always root your phone and use a free app like adbwireless (which only works on rooted devices and local wifi which does not have wifi isolation turned on). That's what I had to do with my Samsung Tab 10.1 (until I sent it back for repair).
Adb wasn't finding my Tab from my Ubuntu 12.04 laptop either, nor was it finding it from the Mac and the Windows PC of my developer friends, but when I tried to connect the Samsung Tab 10.1 that belonged to a friend of mine, adb was seeing it just fine on it, so this is what pinpointed the problem for me.
Try restarting adb
adb kill-server
adb devices
Make yourself a shortcut to this.
I am running Android SDK 2.2 and am trying to get the adb to connect to the Google Nexus One phone. Its a new phone, shipped straight from Google - haven't installed any apps on it yet.
(I have Windows XP)
Here is what I have done so far:
Followed the instructions on setting up the device for development as given on the Android Developer's site:
http://developer.android.com/guide/developing/device.html
added android:debuggable="true" to my application manifest
USB debuggable is checked on the phone
downloaded the Device Drivers For Windows Revision 3 (this supports Nexus One phones)
Went through the Hardware Installation wizard to install the device - the device shows up as "Android Composite ADB Interface".
When I run adb devices on the shell, the device appears for a moment, then disappears.
On the Eclipse console, I get the following message:
[2010-11-13 11:54:42 - DeviceMonitor]Failed to start monitoring
I have rebooted the pc several times, uninstalled and reinstalled the drivers several times, but I get the same error each time. As I was researching this problem, someone had recommended rebooting the phone. I am a bit confused by that - is that a soft or hard reboot? Do I just power the phone off/on and is there something more complex involved? Do I have to hard reboot it to reset to factory version - even though its brand new?
Has anyone run into a similar problem? Any help on this would be great.
I can't test my application on the device if the adb cannot view the device. Thanks so much in advance.
I had this same problem. To get it working, do the following:
Close Eclipse
Open Task Manager and kill the adb.exe program.
Re-open Eclipse (Eclipse will automatically restart the adb.exe service)
Run adb devices from a command prompt and you should see something like the following:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
Of course, I'm assuming you have your phone plugged into your computer.
It sounds like something is killing the service as soon as it starts. Try disabling any anti-virus and running adb devices again. You can also check your system logs for errors - run compmgmt.msc and check the Event Viewer's logs.
When I run adb devices on the shell, the device appears for a moment, then disappears
Do you mean Windows' command shell cmd.exe? The output of 'adb devices' doesn't update itself, it should just print out what's currently connected then terminate.
Nothing here worked for me. And you know what? I plugged it to my USB 3.0 port.
Just plug it to regular USB 2.0 and it'll work.
Hi you jst need upgrade your usb driver, follow this ref link, after upgrading you need to uncheck USB debugging, disconnect cable from device and then check USB debugging and connect cable to device again. this'll solve your problem..
link text
I had this same problem. Do the following:
Plug your phone into your computer and:
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
Turn off COMODO Firewall and Defense+ module
I got my Nexus One on Windows 7 64 bit going by following these instructions:
http://developer.android.com/sdk/win-usb.html
Note that the directory has changed to /extras/google/usb_driver.
You know that you need to do this if you go to control panel->devices and printers and show properties on the device, and there's no driver shown.
Open the task manager by Ctrl+Shift+Esc
In the Processes select adb.exe and Click the End process Button.
Now close the eclipse and restart it again.
This worked for me. Hope this would work for you as well.