Any ideas where I can begin to find out what's going wrong?
I have a T-Mobile Pulse Mini (Huawei) which I'd like to get working for developing and testing apps on. I can't get it to be seen by Android Debug Bridge despite restarting the adb server. (and emulators are seen by adb any way so that's unlikely to be the problem).
In the device manager the phone is displayed as a CD-ROM and when I select 'transfer files' from the auto 'PcOptions.exe' it is then displayed as a USB driver but in either case I can't see it in adb. I have enabled debugging on the phone. I remember it took me ages to get it to work on my previous Vista 32-bit. I can't figure out where to search from here. The drivers used to install the phone are on the phone itself.
Thanks very much.
Drivers. If you can't see the phone in ADB, it's almost always a driver issue and this is especially common on Windows. The regular user drivers are sometimes different from the ADB drivers. If you can find the OEM dev drivers directly that's ideal, otherwise there's a way to modify the INF file which you'll have to Google for unless someone else provides it, as I don't remember the details at the moment.
Related
I've been working on the HelloWorld app for a few weeks now, overcoming many little hurdles, and I think I've reached the last one. I'm working out of 'Learn Android Studio' by Adam Gerber (not an endorsement, just happens to be the book I'm using). I have an HTC One.
When I open the device manager, there is no device listed. In the terminal, I issue the command adb devices and I get the heading "List of attached devices" with nothing listed. If I click the green run arrow, I'm asked to choose my device, but my device isn't shown.
I used to get the error "Unable to obtain result of 'adb version'" when I opened the device manager, but I don't get that anymore, for some reason. But now, when I open Android Studio, I get a Windows Firewall window telling me that some aspects of Android Studio are blocked, including public networks. I don't know if this is the reason for my difficulty or not (I don't think connecting my phone to my laptop is like a public network, is it?).
I went to the developer.android site and followed the directions for connecting a device:
How to connect an Android device to Android Studio.
Step 1 is: "Verify that your application is "debuggable" in your manifest or build.gradle file." The details on how to do it are provided, and I made the appropriate addition to my build.gradle file.
Step 2 is: "Enable USB debugging on your device." This is the thing where you tap your phone at a certain place in the settings to enable development capabilities. I did that.
Step 3 is: "When plugged in over USB, you can verify that your device is connected by executing adb devices from your SDK platform-tools/ directory. If connected, you'll see the device name listed as a 'device.'" As I mentioned above, I get a heading for a list, and no items listed. My book says on page 23: "If your computer does not recognize your Android device when you connect to your computer via a USB cable, you probably require a USB driver. If your computer initially recognizes your Android device, you should probably forgo installing a different or newer version of the USB driver, as this could cause the USB connection to fail." Since I've transferred image and music files to and from my HTC One dozens of times, I followed this advice and did not install a driver (Actually, before I read this book, I had started looking for a driver, following the links on the developer.android site, but I wasn't able to locate one).
On another site where programmers congregate, someone gave me this list of 4 items to check:
- Have you reinstalled adb? (I'm not sure what this means.)
- Do you have the DeveloperOptions SubMenu enabled on your phone? (yes)
- Do you have USB debugging enabled on your phone? (yes)
- Do you have AllowMock Locations enabled on your phone? (I did not, and I enabled it.)
Regarding the first item, my adb is an exe. How do I 'reinstall' that? I responded to his message, and he has not responded to clarify what he means.
Regarding mock locations, that was not enabled, and I enabled it and tried again to connect my phone to Android Studio. That's when the Windows Firewall window showed up for the first time. I don't know if it's because I enabled mock locations or not.
I also tried rebooting after starting the adb, as suggested by my book, on page 25, but that didn't do anything. "If after restarting the ADB server you still don't see the device, it's possible, though unlikely, that the USB driver requires a system reboot to take effect." I've noticed that adb starts up when I boot up (I tend to keep the task manager open), so I know my problem is not that the adb is not running.
I looked at many similar questions on this forum, and the most common advice seems to be to install a driver. Since my book says a driver might not be necessary and could ruin my USB connecting ability, and also since some programmers stated that their Android Studio connection to their phone was failing in spite of installing drivers, I'm not rushing to install a driver, especially since I need USB connectivity on my phone for my job.
So this is where I am. So, what about this statement in my book that if my laptop can see my phone, I don't need a driver. Would that be true? What else could be the problem?
Any help/suggestions/comments gratefully appreciated.
The fact that your computer can see your phone does not mean that you don't need a driver.
What that means is that your computer has the appropriate drivers installed for recognizing your phone as a media device.
What you need is for your phone to be recognized as an ADB device. These are often different drivers from the phone drivers that are installed by default, as the vast majority of users do not need to use developer tools with their phone.
If you can find these drivers from HTC, then they are very safe to install and the risk to your computer is negligible. Google's USB drivers installed via the SDK manager work for many devices and are also safe, though I cannot speak as to whether they will work with the HTC One or not.
Unable to install the drivers for the usb debugging mode on android-system.
The device — Sony Xperia V with Android 4.3, on the PC — Windows 7 Home Premium.
Phone Information in Device Manager. There he defined as "portable device". Sorry for language. It is russian :(
I downloaded the latest ADB drivers from the sit Google, set them manually, and the picture is as follows:
ADB does not see the phone.
Update the Windows driver does not, on the grounds that the best of everything is already.
If remove them when you reconnect a Windows device starts again instantly put all the same his driver.
Disable automatic driver installation failed. In the Home version of Widnows is only possible to disable autostart them with auto-update service, which I did. Set gpedit.msc, where he was to be an item on the prohibition of automatic installation of the device, but it was not there.
You can connect your phone is turned off debug mode and then turn it on. In the Device Manager list is updated, but nothing new in it does not appear.
I faced with this problem for a long time ago when I try to install a custom recovery . Then the phone just was not detected, probably due to lack of drivers. Tried in vain to fix anything, but it was easier to use someone else's car, where the driver got up at once as it should. Now, the problem still want to overcome, for debugging applications on android-emulator inconvenient, it would be nice to do it several times on a real device.
Now I don't know what to do :( Help me please.
You have to install the PC Companion from Sony.
Are there any alternative ways to get it to work?
Even the adb command of android sdk doesn't detect my phone. Then some said I need to install the phone drivers first, I thought the phone automatically does it when plugged in while usb debugging is enabled, but it appears that it doesn't.
I searched for the driver, but was unlucky, it was not included in the memstick that came with the phone. Even the lenovo website doesn't provide it.
I need an android phone to test my apps with that will work with Eclipse. It has to be low cost, run Gingerbread with modest memory and CPU.
Thinking that any android phone would work I recently purchased a Virgin Mobil Chaser but as it turns out, it cannot be seen by either Eclipse or adb (but device manager does see the phone). Another developer has also had the same identical problem with the Chaser.
I could keep buying phones and see if they work but that could be long and frustrating. I hope to find a "no contract" phone.
Is there any list of phones that work with Eclipse. Does anyone know of any other Virgin Mobil phones that will work?
thanks, Gary
Any android phone should work. And it is not Eclipse you need it to be compatible with. You need ADB drivers for the device so ADT tools can communicate with device. So what you need is to install ADB drivers for your phone and then, once installed, you should be able to see your device once you enable USB debugging on the device. Then ADB should be able to see it (either in Eclipse plugin or via command line adb devices).
EDIT if you are on Windows, then enabling USB Debugging on the device and connecting it to the computer should result in Windows asking for ADB drivers. You may try if "stock" (these available with SDK in <SDK>\extras\google\usb_driver) are suitable. If not, check manufacturer website (for HTC you may need to install HTC Sync) and if this fail, just google for your device name along with "ADB drivers" and you should get something usable shortly.
One correct answer to my question is: the LG Optimus Elite works fine as a test phone. Drivers installed immediately. Also, it's less than $100 with no contract.
I still haven't found anyone who has gotten the PCD Chaser to work.
Gary
I have installed the latest Motorola USB drivers which include support for the Triumph.
When I plug in my phone, "adb devices" does not list my phone.
My device manager shows my device under Phone as well as Disk Drive. Both use the WPD FileSystem Volume Driver and refuse to let me update the driver by pointing the motorola drivers in Program Files. It continues to tell me that "Windows has determined the driver software for your device is up to date."
Any ideas?
I am currently in just about the exact same predicament =/
I have some possible avenues that we could both share:
Idk if you were able to find a phone number for Motorola (American that is) but i finally found one
Motorola Mobility, Inc.
600 North U.S. Highway 45
Libertyville, Illinois 60048 USA
Telephone: +1 847 523 5000
Here is a link to yet ANOTHER programmer having the same prob as us =/, but he got it figured out using the steps he posted there
Also there is live support chat here.
If you find a solution to this problem, please, please, please let me know =) And i will do the same for you if i get it figured out soon.
Edit:
Nevermind, i got mine to work just fine =)
Heres what i did:
Used USBDeview to uninstall all previously failed attempts at drivers lol
NOTE: You will have to run USBDeview as an Administrator(right click, select Run as administrator)
In the device manager, after uninstalling all the others, right click on what pops up for the device, click update driver, browse for your own, than from there it was a series of selecting from lists, but the key thing here is to remember that eclipse debugs programs on external devices using the adb interface, which should be a pre loaded option in said select lists =)
Hope this helps!!!
Have you enabled debug mode for your phone? This can be done via settings->application settings->development->USB debugging
Whenever I've had a problem with adb recognizing my devices I've managed to fix it by adding a reference to it in my .android/adb_usb.ini file.
I only run Linux/OS X at home and I don't want to try and blindly describe how to do it on Windows from memory, but they discuss it here http://android.modaco.com/topic/294799-adb-windows-7-and-the-pulse-tutorial/
And google gives the USB Vendor ID's here http://developer.android.com/guide/developing/device.html .
On my linux box I added:
0x0489
To my adb_usb.ini (using the Foxconn ID which on linux you can find directly via lsusb, I think you could use devcon on Windows to find it) and it shows up on my device list.
Just because this link hasn't been dropped in any answers (and I always find myself looking for it), here are the manufacturer's development drivers.
This is what worked for me. I have a Moto Triumph and Win7 x64...
Turn on Unknown Sources, USB Debugging
Install Motorola USB development driver. Unfortunately, Motorola broke the old driver URL, as well as many development forum URL's. Fortunately, Softpedia has copies of the installer. Grab the 32 bit or 64 bit version depending on your OS.
Plug in your phone by USB
Open Device Manager
View hidden devices
Uninstall default drivers (Disk Drives\Qualcomm USB, DVD\CD\Android SCSI CD-ROM, Portable Devices\F:)
Action > scan for hardware changes, or Disconnect/reconnect phone
Repeat till ADB appears (probably w/ a yellow icon indicating it's not fully installed)
Right-click ADB > update driver > browse my computer for driver > pick from a list > Motorola > Android Sooner ADB (the first entry)
Accept security warning
Done. If it worked properly, you can now view your device using adb devices.