I've built an android app through Eclipse, and now I want to test it on my real device (a Motorola Razr). I tried to follow the directions given here: http://developer.android.com/tools/device.html

For step 1, I declared the application as debuggable in my manifest. For step 2, I told my phone to be debuggable.

Now, for step 3, since I'm developing on Windows 7, I followed along to this link: http://developer.android.com/tools/e...-usb.html#Win7

Step 1, I connect my phone via USB. Step 2, I right click on computer and go to Manage. Step 3, I fail I don't see the word "Devices" there on the left. There is "Device Manager" (which I clicked in the image below), but I'm only supposed to click that in step 3 if I want to upgrade my Android USB driver, not install it for the first time.



So I'm lost. I tried googling around for help, but nothing seems to be helping. Anyone have any ideas for me? Or need more info from me? Thanks.

When you connect your phone to your PC what scrolls across the notification bar?

Actually a quick search on the internet reveals you probably need to use the Motorola drivers for this device instead of the google ones.

Nothing. It just starts charging the battery.

My computer does react, though:


("USB Device Not Recognized. One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it. For assistance in solving this problem, click this message."

Someone told me the same thing in PM. I actually started on this like a month or 2 ago and then took a break, so I forgot to include this in my OP. I already did that, installing from here: https://motorola-global-portal.custh...81/action/auth

It installs fine. I've rebooted computer and phone since then but it doesn't help.

I have seen that happen before when the usb cord was bad, if you haven't already, try using a different usb cord, also try using a different usb port on that computer or another computer

When I connect my device to the PC for debugging, I get something in the notification bar about "USB debugging enabled" on Android 4.4

For some reason none of that came to mind. Since it charged the phone, I assumed the hardware was good.

But still, that is the right approach -- switch out all the pieces to localize the problem. So I started with trying a different phone -- my old HTC Incredible -- while keeping the computer and cord the same. And it worked perfectly!

So I have no idea what's up with my Motorola, but it seems to make things harder for no good reason.

Thanks!

Does adb work at all with your phone? (from command line)

The android drivers are always a PITA -- have you uninstalled the google drivers first? I had a problem with my Samsung and had to install the Samsung drivers, but had to do a bunch of uninstall/installing to get the right combination.

I think I'm going to buy a Nexus 5 next.

On a PC, I had various driver problems, but recently I moved to OSX and now everything works with the SDK driver. Even those cheap crap chinese unbranded tablets work with the Mac driver.

I have not been able to get adb to work from the command line independent of the phone situation. I tried a few times to find if the command was hiding somewhere out of my path or was just missing somehow but eventually gave up.

I dual boot Win8 and Ubuntu and I often have problems with Eclipse/Android Studio/Genymotion on Windows, but everything pretty much works out of box on Ubuntu. Like yesterday when the Samsung drivers were not working on Win I just booted to Ubuntu and voila - installing app to Samsung S3 worked without drivers.

The only thing I can guess, is that device manufacturers build in generic driver support for the Linux/OSX crowd and thats all android developers need. But when it comes to windows they want to do their own thing and maybe build some fancy software, but it comes at the expense of Eclipse working smoothly.

It's usually in the tools directory of your bundle directory.

Yeah this seems like a Motorola issue. The only things I can think of is to make sure that firmware is up to date on phone and with the phone off get into device manager, start scanning for new hardware after turning on device.

Btw I'm pretty involved with Android phones and from what I've seen earlier versions of Android on many phones don't play all that well with bluetooth and/or USB. If I was developing apps for Android devices that I wanted to mass market I'd start with an S4 and a solid tablet. I realize that cost is an issue and mass marketing may not be a goal.

Another Option for an Adb Connection

I was thinking another might be a TCP/IP connection. Here is stackoverflow thread on that.