I'm trying to get my phone to connect with Eclipse so I can run android apps without using an emulator. I've already gotten this to work and made an app, but I got a new hard drive since then. Every time I try to reinstall it on the new hard drive, it says that it doesn't install properly. I've tried using 2 different usb cords, rebooting every time I try it and installing/uninstalling the USB driver from the Motorola website to no avail, and I can't remember exactly how I did it before.
Can anyone help?
Make sure your usb debugging turned on and use this free software to install the driver :
http://adbdriver.com/
Android's development page doesn't explain this one in full detail. I had problems with it myself. Although my situation wasn't exactly like yours, installing the usb driver from the SDK made it work.
Follow this guide!
Related
I connect my phone Realme 6s (RMX2002) to my device and the USB debugging is enabled.
Android Studio recognized & connected but doesn't show the app project in flutter like in the photo
So, any suggestions to figure this out?
You need to check your USB cable. They are in two types, one of which only supports phone charging.
I can't quite understand what you're asking here, but according to your photo, no device is selected to debug on.
My advice is to (save) =) and restart Android Studio. Make sure that the RSA fingerprint for your computer is accepted on the phone. Try restarting your phone and reconnecting. Double check that USB debugging is enabled.
I cannot tell what is really going on, it may be an issue with the ADB. Check your Event Log to make sure the ADB debug bridge started successfully.
If you simply try to run your app on an emulator, issues of this kind will be promptly visible.
If you can ascertain that it is not an issue with ADB, Android Studio, or your phone, it is probably a driver issue with your computer, if you are on Windows.
Try this link: https://www.thecustomdroid.com/oppo-realme-usb-drivers/ to install the USB drivers for your computer.
Cheers!
I a had also problem with USB debugging and it was the cable's fault.
An alternative option is to use wireless debugging. A step-by-step guide for Android studio can be found here: https://link.medium.com/UQJWZrfFqob
I have just started android programming, and after watching many tutorials and reading many articles I learned that if I want to run my programs on my android phone, I will need to install the usb_driver. I have done that, but when I go to device manager, in other devices, my phone has a yellow exclamation error. This is normal, but it should go away after right click->update driver software->browse->C:\Users\myusername\AppData\Local\Android\sdk\extras\google\usb_driver->next. But, after doing this, I get the error:
Without downloading the usb_driver, my device just wouldn't get detected. I have already allowed usb debugging, and allow mock locations, so right now I just need the driver. I have read almost all the other articles and tutorials, but my device still doesn't show up?
There is also a great tool: adb driver installer, that allows you to install drivers for almost any phone, without need for the 'software suites' that often come along drivers.
I figured out that besides for installing the updates for the computer, I must also go into my computer and allow permission for these updates to run. After that, I followed these instructions.
Has anyone tried developing application using Lenovo K900, I am writing application for my phone (Android 4.2.2) but its not getting detected by eclipse.
Please help
I found a couple of drivers and the combination seems to do the trick.
I installed the drivers from this post to see the device as a CloverViewPlus device
https://forum.lowyat.net/topic/2918390/+940# (Post #943)
The IntelAndroidDrvSetup1.2.0.exe and iSocUSB-Driver-Setup-1.0.2.exe were needed.
Then I installed the drivers from this post to get Eclipse to recognize the device:
http://singledrivers.blogspot.com/2013/12/lenovo-k900-usb-driver-for-windows.html
It seems that you do not need the MTK driver.
You do seem to need the PDANet Driver.
The ADB driver did not seem to hurt either.
Now Eclipse can see my K900 and download code to it.
Only enabling USB Debugging will not help solve your issue.
You need to install certain drivers in order to make your cell phone visible while running the application.
For now, even I am searching the perfect drivers to install in my system. Will get back to you once I have them. Also, I request you to search as well and revert in case you find success in the same.
I have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
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.