I'm having a serious problem, i am trying for 2 days to simply add a device to ADB Android Debug Bridge.(from android sdk) and i can't do that, i've tried many "solutions" but none worked.
I have a project application working fine, on my Eclipse. My Operational System is Windows 8 Pro 64 bits. When i simple connect a Mobile Phone (SAMSUNG Android GT-S5301B with Android 4.0.3) to my computer, eclipse cannot find it, adb devices cannot find it too, no one can find it.
I've tried to intall the drivers from android-sdk/extras/google/usb-drivers but it told me that was already installed.
I cant understand why my OS cant recognize the phone, i tried enabling the USB Debugging in phone configurations, tried disabling it too, tried with MTB mode and MTC mode too.
I dont know what to do, i did spent 2 days triying all the things that i found, i really need a help, a rescue.
What i do?
Download adb driver from samsung website or install samsung kies it will work.
Related
I am using the latest version of Android Studio(2.1.2) at the time of writing this post . The problem that I am experiencing is that the ADB instance used by Android Studio doesn't seem to be able to find my Galaxy Core Prime device (SM-G361F, stock Android version - 5.1.1). It can connect to an emulator just fine.
What I had tried (most of these multiple times):
enabling/disabling developer options
enabling/disabling USB debugging
revoking USB debugging authorization
changing MTP to PTP and vice versa (my device doesn't allow deselecting both options, one must be chosen)
reinstalling the drivers
powering on and off both the phone and the PC
installing Samsung's Smart Switch software
using different USB ports
trying out different Android Studio versions (x86 and x64 with the latest respective JDKs)
This is what it looks like in Android Studio:
I had installed the official Samsung's USB drivers from here.
This is what the Device Manager is showing (Windows 7 64-bit SP1):
Afterwards, I've also tried installing the Universal USB drivers from here.
This is what firing up its installation of ADB looks like:
It has obviously successfully found the device.
My device also politely prompted me to allow the PC to connect to it using a generated RSA key which never happened with Android Studio.
The only thing I've not tried is installing Samsung's Kies software.
I really don't know what is the problem here.
Maybe I should just give up and instead use the emulator but it is a damn shame not to be able to debug on an actual physical device, if you ask me.
Thank you in advance.
Android in general does not support all phones for a debug connection. I have a samsung s6 and for me that works. I don't know about the Core Prime though. However, in most cases(in my experience):
The phone does not support the connection
You did not install all the required files in terms of the android SDK you might have not gotten the latest update that supports more phones
The OS is not supported - Mainly caused because Samsung and a lot of other brands insist on having their own updates. And some times they - on purpose or by accident - forget to support USB debugging for developers.
My tablet did not support the USB debugging connection untill it reached android 6.
The cable is a charge-only cable (yes, those exist for some reason). Try with a different cable
You don't have the necessary drivers. Make sure they're installed
It might be circumstantial that your phone model does not support the connection for some reason, but it is really hard to tell. The only way to get proper help is to contact Samsung customer support, but in my experience it is just a waste of time. They don't know their own products. If you try with another device it might work.
After some continued tinkering I managed to get Android Studio to recognize my device. All I did was adding the path to the ClockworkMod's ADB .exe to the PATH environment variable. That seems to have done the trick as Android Studio now allows me to run the application on my device even though it is still running its own instance of ADB (located in the platform-tools folder).
It might be completely unrelated but I'm not considering undoing the modification made to the environment variable.
Here is the proof:
Eclipse isn't recognizing neither of my two Android phones.
I've tried updating all of the Android SDKs in eclipse as well as eclipse itself.
Both of my phones are being recognized by my Macbook and Android File Transfer works like a charm.
They are both in Developer mode with Debug turned on.
I've also tried connecting them in both MTP and PTP but eclipse still won't recognize my phones.
I get the RSA fingerprint pop-up and I press OK but nothing happens.
What could be the problem? I don't know what else to do.
Edit: Eclipse used to work the last time I used it to run Android apps (which was about three-four months ago). Now, it won't recognize my phones. Also, you can't install drivers on the Mac. According to Google, it is just supposed to work.
Edit: This is what I get for the adb devices.
Marcos-MBP:platform-tools Poloe$ ./adb devices
List of devices attached
Found out the problem.
Turned out it was this.
adb devices list empty -- Snow Leopard
My phones weren't being recognized because I had EasyTether installed on my phones and on my Macbook.
According to the EasyTether website:
ADB on Mac OS X stops recognizing the attached device after installing EasyTether driver
Do not follow this advice if you are not a software developer who uses the Android SDK on Mac. Otherwise run "sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext" to unload the EasyTether driver manually. Load it again with kextload when necessary.
I am using a Samsung Galaxy S2 (GT-I9100) and I am trying to debug web pages with Chromes included support for remote inspect.
I have installed drivers from the following link: http://www.mobileusbdriver.com/samsung-mobile-drivers/samsung-galaxy-s-ii-usb-driver
I have followed the steps on https://developer.chrome.com/devtools/docs/remote-debugging. But I am experiencing problems from step 3 and forward, my phone does not prompt me to allow USB debugging. The phone has been used for web inspection before with the old Chrome extension that was available before, but has been reset to factory default since.
The problem i am facing is that on chrome://inspect/#devices my device isn't showing up in the list. Chrome can't find my device at all.
When i look at the Device manager there are no errors, so i assume that my drivers work as they should.
I have made sure that USB debugging in Developer tools is checked, and Chrome on windows is discovering USB devices (the checkbox is checked in chrome://inspect#devices).
Anyone got any ideas what i might have to do to fix this?
Thank you.
Progress edit:
I still haven't found a fix for this. I've tried to install the android SDK, add the eclipse material to my eclipse IDE, updating drivers, updating kies, rerun the driver installation that was included in the eclipse install, and looking through my developer settings in my phone like 900 times.
Anyone still haven't got a clue of why this is happening?
Ok, the solution is very weird.
I talked to a colleague and he had an old nexus driver (for Samsung SCH-I515 which is a nexus phone distributed by Samsung) locally on his machine.
We transferred it to my computer and uninstalled all the drivers i had, manually installed this driver and voila! It worked.
Why this driver worked, i have no idea. I cant complain though.
Thank you all for the help.
I am new to Android programming and have been unable to connected my phone to eclipse for debugging and running applications on the go since many days. I have enabled the USB debug mode etc, installed the Google USB drivers and followed all the steps mentioned on the official Google site
http://developer.android.com/tools/device.html
As extra debugging steps for this problem, I tried the Android Debug Monitor tool (monitor.bat) but my phone didnt get recognised in that as well. Also I ensured the my project build SDK version was 19, which i believe is suitable for Android 4.4.4. I used a Moto G(4.4.2) and again I couldnt run apps on it from Eclipse.
But in five minutes by following the same steps I could get the debugging working with Samsung Galaxy duos(android 4.2.2, API 17)
Am I doing something wrong?
OS on PC - Windows 8
Download pda software from pdaorg.co this will surely help you. I was also running with same problem but after installing pda my problem has been sort out.
Try switching your phone's USB computer connection to Camera(PTP) mode. Worked on my side. Hope that helped.
I have been making a 2D game using Unity3D and have been debugging it using a Huawei G510-0200 and a Samsung Galaxy S3. Everything was going fine and dandy, I then took a break for a couple of weeks, come back and find that neither of my phones are being found when I try to build the game onto them.
They were building just fine before, so I have NO IDEA what's going on.
Things I have tried:
USB Debugging is on
Restarted both devices and my Mac (which is running the Unity3D)
Reinstalled the SDK
Retraced my steps and routing the SDK in Unity Preferences
Updated Drivers
Tried all the different USB ports.
Any ideas?
I solved this problem by uninstalling Bluestack's player, which was conflicting with my developer environment, somehow i don't understand what was the issue with blustack's emulator. but surely it was making trouble.
Solution: if you have bluestack installed or some other android emulation software then uninstall it.
RESTART your system
Play the scene in editor with connected to device remote running on it.
After reading the Android section of this: http://docs.unity3d.com/Manual/Profiler.html
I figured out that debugging via usb is only possible if the device has an IP. I could see the device via adb devices command but it wouldn't work in Unity, once it had an IP, everything was just fine.