First of all I must say that I have been working around this issue for two whole days and I can not solve it. I googled it, I read this article from Donandroid, this thread from SO and many other reviews.
I have installed Samsung Kies3, Android sdk for windows, google_usb_driver on my windows 7 64-bit system. I also check the USB Debugging option in my Galaxy S5 and restart my phone. I also have restarted the ADT
Now when I check the attached devices in adb, I get:
$adb devices
$List of devices attached
4d0005444cc34139 unauthorized
I have tried to run my application on this device, but I have got this in ADT:
I have no idea what to do now. I am totally frustrated. Any help would be greatly appreciated guys.
Ok, solve the problem. I have unplugged/plunged the usb cable for 3 times and suddenly the popup authorization message showed up on my phone. I allowed that and now everything is fine. I can not believe I spent two days in this issue. Hope this thread will help someone.
Related
I'm not really sure how to word this.For some reason when I install an app that I'm working on from Android Studio it runs very slow (when an option is pressed it takes 10-20 seconds to register). But if I install the app from either my coworkers Android studio or adb from my own machine it works fine.
My specs are:
OS: Windows 10
Android Studio Version: 3.0.1
Phone OS: Android API 24
It was working fine this morning, but during the course of the day, something has happened. Has anyone run into this sort of problem before?
I'm using a Samsung Galaxy S8 physical device. I have tried a factory reset on the phone which worked for one install after I changed some things I'm back where I started. I have also restarted both the machine and phone multiple times. I'm at a loss as to what is going on. If you guys need any more info let me know. Also INSTANT RUN IS NOT ON.
EDIT: I'm at a total loss as to why this is happening. I've tried everything from restoring the phone, reinstalling Android Studio, changing wires, changing settings, but nothing is working. If anyone has a suggestion I will gladly try anything.
I've finally found a solid solution to my problem. I'm positive now that something went wrong with m usb drivers for windows 10. I went to this page https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-slow-usb-30-transfer-speeds/a5e1eebb-74bb-4777-8902-5131f3e8ec3e and I completed the steps in method 1 and that did the trick for me. it took a while to find this out, but hopefully, someone else will find this helpful.
Have you compared your yesterday build and today build which is making your app slow. Any Significant change in code?
Have you set up breakpoints or similar? Some debugging options can significantly slow the app down at runtime. When this happens, if you disconnect the phone from ADB - e.g. pull out the cable - and it speeds up again, then it's likely related to your debug connection to that particular instance of Android Studio.
A while back I started playing around with Android developing on my PC and used my Samsung Galaxy s4 as the test device and it worked fine. Once school started I mainly used my laptop and was also able to use my phone on it as well, and still am able to do so.
For some reason, my PC will no longer sees my phone as a running Android device and I cannot figure out why. I even tried reinstalling the driver to no avail. Does anyone have any idea as to why this is or any suggestions that I can do to make it be seen again?
Thanks to anyone looking at this!
Well it looks like USB debugging was unchecked. Go figure it was something simple.
SOLVED, se my own answer below.
While happily developing on my physical phone, Eclipse inexplicably doesn't find it next time I choose run. The Devices view is empty and grayed out. Rebooting doesn't help. Reinstalling googles' USB drivers doesn't help. Reinstalling Kies doesn't help.
Kies and Windows 7 have no problem finding the physical device immediately when I connect it.
What can I do?
Unplugging and reconnecting the device, and restarting Eclipse can solve this problem. Eclipse is quite a random piece of software and likes to misbehave in so many devious ways.
Heureka!
Somehow, the "USB debugging" option on the phone had been disabled. Probably by my own fat fingers. Sorry for having disturbed you. Thanks for your suggestions.
I know this is a rather common question, but I tried all the solutions I found on other post and they didn't do the trick for me.
Basically, I have a Samsung Galaxy S, that worked fine with eclipse, so I was able to debug applications directly on my smartphone.
I tried 2 days ago since a lot of time, and the device is not recognized by the system, even lsusb can't find it.
I tried with a friend's smartphone, from a different brand, and it worked fine, so i guess it's something related to my smartphone, but I can't figure it out.
Debug is enabled on the phone, any other idea? My OS is Ubuntu.
You have to deleate the data where the debugs and the runs are stored
I don't know where it was because i had this problem last year.
But whene i deleted the data it works fine again
Edit :
Found it
C:\Users\UserName\.android
delete
debug.keystore
I guess Samsung Galaxy S drivers are not installed properly. Install pdanet software in your workstation while installing it will ask connect your mobile with usb then it will install drivers automatically. I think it will work for you. try this..From this link you can find the software
I have been using my Galaxy S2 for testing my applications with Eclipse for a while now. All of a sudden when I try to run my applications my device does not show in the Device List of Eclipse.
I have looked everywhere on the internet for a solution, I have made sure my phone is in Debugging mode, Re-installed the SDK, restarted my computer and phone but nothing seems to be working.
I would really appreciate any suggestions!
So after a few days of fustration and going crazy I finally worked out the problem... the usb cable. I used a different one and it worked with no problems!
I just thought I would post this in case anyone else has the same problem.