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.
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:
I'm trying to deploy an Apache Cordova app to an android device that's plugged into the machine. However when attempting to deploy, I receive the following error:
Unable to deploy to Android device, no attached device was found. If you recently attached a device, you may need to wait a few seconds before it is recognized.
As far as I'm aware, I've enabled all of the developer settings I need in order to deploy to the device. I've tried unplugging and plugging it back in, waiting a few seconds but to no avail.
I've tried changing the connection modes (HTC Sync, Disk Drive ect) however that hasn't made a difference.
The android device I'm trying to deploy to is pretty old (v3.35.61.3), so I've even tried to deploying to a different android device running the latest version of android however the same issue occurs.
This leads me to believe that it's an issue with Visual Studio not picking up any connected android devices. Perhaps I'm missing an install package?
After smashing my head against a wall for a couple of hours, I managed to get this fixed.
I followed these instructions to install the SDKs for the target device.
There was still an issue where the abd devices command was still not showing up with any devices, I installed the Universal ABD driver which I found in this question and that worked for me.
EDIT
Some of you have found that the following can also fix the issue:
Turn on the Developer Options on the device.
Enable USB Debugging.
It might be worth trying this first, and if that doesn't work, try what I did.
I ran in to this problem and I was sure I had everything installed. After some thought I tried to deploy again, and in the developer options on the device I turned usb debugging off and then back on, this got me a prompt to remember my computer's fingerprint. After that everything worked.
I had this issue too (can't reply to the answer because my rep is too low) and I found out that when my phone updates, it turns USB Debugging off. It's worth the time to check.
I had the same issue on my S4. When I turned on the developer options the Enable USB Debugging was turned off. Once I turned that back on the issue was fixed.
First option : Enable USB DEBUGGING
Second option : Change your phone cable.
When I try to run or debug my app this appears in "debug" of Android Studio:
Waiting for device.
USB device not found
My phone is a: Motorola RAZR D1 TV. It connects to the PC (even if in debug mode).
I'm working on Windows 8.1 64 bits (running in no certificate detection for USB mode).
I have Java 1.8.0_25.
I tried to set the 'android_winusb.inf' file as said in this answer: https://stackoverflow.com/a/22887262/3124150. I have to say that none of my USB connectors appear abnormal.
I had been having this issue with a device of mine as well.
First, check that the device is in debug mode. If it isn't, try everything again.
If it still isn't showing up, even when in debug mode, then your issue is probably a lack of drivers.
Open up your SDK Manager (it'll be a button at the top of your IDE, or you can find it in the Android SDK download folder), scroll down to the bottom, and download the USB drivers. This fixed the issue for me.
Wow Ok I have wasted more or less 3 hours dealing with this same issue after much thinkering what worked for me is downloading this Unified Android Toolkit
And using it to download the correct driver for my Samsung phone but there are also drivers for other brands.
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.
I am having trouble debugging my android app on my phone. My Phone is an LG Optimus G running on android version 4.0.4. Everywhere says to update the driver, but when I do that, my computer doesn't recognize it. I have android ADT installed with SDK versions 4.2, 4.0.3, 2.3.3, and 2.2. I think it might be the fact that my phone is a 4.0.4 and not 4.0.3. And I have USB debugging enabled on my phone. The emulator is just to choppy and laggy to debug on. And one more thing, I have tried debugging already and it has not found the device, although i can find all of the files and pictures on File Explorer. Please help.
If you are on Windows I suggest you try downloading PdaNet http://pdanet.co/, this app is used to share Internet from your android phone to your PC, BUT ALSO helps you install the correct drivers for your Android.
I've found that using this program is the most simple way to get most Android phones working on Windows, plus if you don't want the software you can just uninstall it and the drivers will be kept.