I am using HCL ME U1 for testing my android application. But when i am trying to run my app on my device, it show unknown device and failed to install on device.
I follow this question with accepted answer but didn't find any device in device manager.
First time, when i connect device to my computer it show "Device driver successfully installed".
I am using windows 7 32 bit OS.
I didn't find any android device in device manager.
When i use cmd to find out device then it show in list.
I also enable USB Debugging and Unknown source in my hcl tablet.
Please give me some hint or reference.
Thanks in Advance.
Instead of restarting the phone, go to task manager(windows) and kill the adb.exe process. After 10-15 secs, it will restart again by itself. It should detect your device then.
Once I encountered this issue and none of the matters could solve my question except a simple trick. I turned off the phone, ejected the SD card, cleaned it with sth and then put it back into the phone.
After turning on the phone, everything was alright. You have other options too:
Connecting your phone to pc while phone is connected to internet (to update its usb drive)
Updating your ADB driver from device manager (while phone is connected to pc)
Some USB cables don't have debug ability. Be sure of using a proper one.
I recently solved a similar problem in Ubuntu by updating my Android SDK. A year ago, I also remember I had great difficulty getting a different phone to connect to Windows. I remember that, despite receiving the "Device driver successfully installed" message, I had to manually install the usb driver from the SDK Tools Manager.
You might also try "adb devices" to see if your device shows up there. I would expect it to be in the Windows device manager of adb can see it. You mentioned there were no Android devices in Device Manager: check for other unkown devices it might show up as. I believe mine showed up as USB Mass Storage before updating the drivers. An alternate guide to doing so can be found here.
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.
I know this question has been asked numerous times, but none of the threads have had an answer to solve my problem. It seems no matter what i try Eclipse just wont detect my phone, I have set it to debug mode in the settings, i've installed "Kies 3" on my laptop and it says i have the latest drivers already installed on my phone when i try to update it.
I've installed the google USB driver package from the sdk manager and have downloaded and installed the samsung driver from the samsung website. Windows recognizes the device and in the device manager under android phone it appears as "SAMSUNG android ADB Inerface".
Im running windows 7 and have even tried deleting all the mounted dive drivers from regedit as i seen suggested in another thread but still no joy! Really starting to get frustrated with this at this stage i've been trying for two days now to figure this out!
This is such a pain! I need to be able to debug on my phone too as i'm using features that the emulator can't handle (i.e. audio recording). I'm all out of ideas here so any help would really be appreciated!
Thanks
The method I followed to install my GT-I9300 drivers was this:
Download samsung drivers from this link:
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Then just connect your phone and make sure you have a stable Internet connection: It will download required drivers automatically.
Also, make sure you have enabled Android developer options in your phone settings. Enable USB debugging in developer options.
I usually get it to work, when I switch the USB mode in my smartphone (e.g. MTP to PTP). This way, windows starts downloading more drivers.
1) Try disconnecting device from PC, revoke USB Debug authorization from settings menu, and then re-authorize the computer you are working on once you connect it again.
2) Check to see if you see the phone in DDMS perspective (left hand side) - if so, try clicking on it and it should work.
3) try removing all drivers (Google, Samsung etc.) + scan "leftover" registery entries using a reg cleaning program. Then install ONLY Kies Light version and try again.
4) It once worked for me - try changing the USB cable (preferably, to an original one)
Let us know if something worked!
1) enable USB debugging in your phone's settings.
2) ensure that you have the proper drivers installed.
3) open adb in command prompt and run "adb connect"
I just upgraded my phone to 4.2.2, but now i cannot use it in eclipse anymore.
I tried rebooting the device, reset my debug-settings but I cannot get it to work anymore.
I saw it is already a registered issue. There are some new security enhancements, so there should be a dialog (see here at bottom) but this dialog doesn't appear. I don't have several accounts on the phone, which is pointed out in the issue..
Anyone any suggestions?
EDIT: Look at accepted answer below, this should cover all cases. In my case, there were some packages missing, which weren't shown in the Android SDK Manager. I just found the Packages -> Reload in the Android SDK Manager... And I thought this happens automatically
You need three things in order to make sure this update goes smoothly:
Make sure your device is actually running 4.2.2 and the problem is not something else
Your SDK is updated to the latest tools. The adb binary in all but the latest version does not support the 4.2.2 security enhancements.
You are on the main account of your device in case of multiple user accounts.
Connect your Device to your computer and execute adb devices (make sure USB debugging is enabled). You should see something like this:
3tiu52839ry082j3 offline
Right about now, there should be a dialog on your device that looks something like:
Check the Always allow from this computer box if you want and click OK.
That's about it.
Some other things to check:
Make sure your USB cable isn't broken. Sometimes, the smaller cables break inside the main one, and your device may charge but have no data connection. Try with a different cable, or try accessing files on the device over USB (this will go fine if your cable is fine)
Make sure you're using the newest version of adb. Even after I updated my SDK tools, I couldn't get my device authorized when using adb. I eventually figured out that the Nvidia install of the NDK and SDK tools had updated my PATH variable to use the adb from that install, which wasn't the latest update. By using the adb in my newly updated install, I was able to get it all working.
For me it was solved by changing Nexus 7 tablet to "Camera(PTP)" mode.
Check out this blog post on how to do it.
After USB connection of Nexus 7 and confirming digest on Nexus 7, also connecting through TCP/IP with ADB worked.
Wierdly, unchecking and rechecking the "Allow USB Debugging" option popped me the window and selecting "ok" solved my problem.
If none of the solutions worked for you then Reset ADB.
Go to Devices ---Click the right most down arrow----Select Reset ADB from the list.
I had tried everything suggested here and suggested in every log/blog that I could find in google, but still no go. The USB cable is known to be good. ADB is version 1.0.31 (as shown with , USB Debugging is enabled in the Nexus 7 tablet, the SDK was updated to the very latest tools as available on 1-mar-2013 for 4.2.2/API 17. I had tried both Media and Camera modes for USB, rebooted windows, rebooted device over and over again, re-installed latest google USB driver, etc. etc. but ADB Devices still showed nothing.
I hard reset the Nexus 7 tablet thinking that maybe the screen to allow usb debugging had appeared but got hit with cancel. But that didn't work either.
What finally worked was:
going into windows control panel | Device Manager,
selecting NEXUS under Portable devices,
then in the Driver tab clicking on update and manually selecting the Google USB driver (the check feature said it was up to date). Previously, the date shown was in 2006, afterwards a date in 2012 (but more on this in a moment).
That didn't fix anything though.
So then I switched USB from MEDIA device to Camera device - THEN it wanted to install driver software, so I let it do that. Afterwards, I noticed that the driver for the Nexus was back with the 2006 version, BUT then ADB DEVICES FINALLY SHOWED OFFLINE!!!! HALLELUJAH AND the Nexus was displaying the Dialog to allow USB debugging, and it now all works.
What I am not sure of is what step actually solved the problem. I don't think it was necessary to hard reset the Tablet, but the fiddling with the device driver wasn't a very convincing solution either - I don't think the driver was corrupt - but maybe it had to be changed to get the right driver associated with the tablet when connected as a Camera Device. In any event, it is necessary to connect the tablet as a Camera device for ADB to work...
Restarting device or enabling USB debugging did not solve my problem.
However I changed USB PC Connection to "Camera(PTP)" mode and adb devices showed the device id of the phone.
After reading a lot post talking about this particular problem, I actually solved it by resetting user permissions on files (that were owned by root): ${HOME}/.android/adbkey and ${HOME}/.android/adbkey.pub
Go to Device Manager and uninstall your device and remove from USB
HAve you CMD opend and make sure you are at least in ADB Help.
Connect device to USB and continue with steps provided by Raghav Sood - few answers ahead of me.
Worked for me just fine
I tried with this custom build and it works for me. Now I can see my logcat in Eclipse again.
https://github.com/khaledev/ADT/releases
Download the zip file then in Eclipse menu Help > Install New Software... > Add > Archive... Just pick the downloaded zip and do the rest of the install process.
As title, I can't able to find my phone device into Eclipse.
I activated on the my phone, either Application/Unknown Source and Application/Development/Debug USB.
But into Eclipse not appear any device phone, why?
Thanks'
Go to the cmd prompt, and then take it to the platform-tools.
Then type the commands
adb kill-server
and then
adb start-server
Then to list the connected devices,
adb devices
you will see the list of active devices including the emulator. If the device is not present, continue the steps for some time..
After you get the device listed among the active ones, you can run it in debug mode.
Think, this will help you..! :)
I just had the same problem on 2 of my phones (Nexus 1 and Amaze 4G). After some research I found that people try to overcome this by restarting Eclipse and ADB (only Eclipse won't do) but it took me rebooting the system and phone to make it work again. If you can go to Eclipse->Window->Open Perspective->DDMS and see if your phone shows there with red bug icon next to your app. If so then try what I described above. If you don't see your device in DDMS perspective then it's your USB driver that is not working and needs to be reinstalled
Had a similar problem with my LG P520. In my case, the problem was as a result of me setting the minimum Android level to Android 2.3(9) while the phone was a Froyo/Android 2.2(8) phone. Hence, it was not a compatible device and would hence not be shown in list of compatible devices.
connect your PC with internet may be it will install some software to connect it with the phone debugger and make sure you enable the usb debugging on your phone.