I have installed the and adb driver on my android device which is yu-yuphoria
now in device manager my device is listed as android adb interface . But when i run any app on android studio that device is not listed . I have changed the usb mode from media to camera again installed the adb interface and restarted both system and device still the device is not listed in android studio.
i have spend hours in fixing the problem but cannot do.
few days earlier there was no such problem but now it came from no where
any possible solution
I had all those weird problems with Windows showing perfect configuration but devices not visible. With three different phones, I always fixed it with this free tool (from XDA I believe):
http://adbdriver.com/
Ofcourse this will not help if it is actually a problem with Android Studio.
Related
Today I downloaded Android Studio for my Debian Testing system. I wanted to run a HelloWorld application but weren't able to run it. With adb I can install it without having any problems.
However, if I try to do it with Android Studio, it gets stuck on 'Installing APKs'. The same happens when I try to start it in an emulator (gets stuck on 'Waiting for target device to come online').
My device is a Samsung Galaxy S3 with LineageOS (Android 7.1.2) and root permissions. Android Studio recognizes my phone properly.
What I've already done:
installed openjdk
set android_home
installed all the SDK-platforms since Android 4.3 and Android Emulator from SDK tools
enabled USB-debugging
tried with MTP and PTP
tried another emulated phone
installed lib32stdc++6
restarted my computer
and probably much more
I tried to do it the whole evening and couldn't find a solution. Is there something Debian-specific because I can only find instructions for Ubuntu? I have never experienced anything close to this on other systems.
Thank you in advance.
EDIT: I am now able to use my phone to run the android application by using USB 2.0 instead of USB 3.0! Is that a normal behavior since it works with native adb? I mean, if I buy a new PC after some years which has got only USB 3.0 ports, will I not be able to use phone debugging with Android Studio or is this just an issue? It is still known since 2014 (https://stackoverflow.com/a/9548311/8292104).
However, I still cannot get the app running on an AVD. I changed graphics to software, now it shows the phone but the screen remains black and the phone won't start. What can I do to fix it?
Try to completely delete and install Android Studio again, I think that it will solve the problem
Another possible solution that worked for me is to, in the application, go to
app - build - intermediates - split-apk - debug - slices
and then delete all of the contents within this folder. Then again, this only worked for me, so I would duplicate the document in case of corruption.
Problem:
My smartphone model (Lenovo Vibe B) doesn't have a official driver listed in the OEM USB Driver List (it has for Vibe C and other, I've tried the one for C, because phones are kind of similar but didn't work), so I can't use it in Android Studio to test my apps.
What I've tried
So my ADB is not recognized or, when I installed an ADB that was found on Device Manager, I got the error Code 10. Updated the drivers, reinstalled all USB drivers, ADB drivers, tried different software like LeTools, LenovoSmartAssistant, MagicPlus, something in chinese, an universal ADB from a developer named Koushik.
Tried different youtube tutorials... also read articles and tried them:android won't connect, installing adb driver - lenovo, how to fix code error 10
Also checked official documentation from Google,switched from MTP to PTP** and back to MTP,tried even MIDI
Still my device isn't visible in Android Studio and in Device Manacer is marked with an exclamation sign, or now it's not visible at all.
I mention that I also accept a solution in which I can install my app created on Android studio on the phone and test it without Android Studio. I need to do that because I'll work on an app that requires to be tested few month's, in order to have a database to predict a future behaviour.
Thank you in advance for your help provided!
For Android Development using the real device you need a tool called Wondershare MobileGo. Its a pcsuit app for Android and ios.
I am using it for 2 years and its the only final solution for all ADB related issues.It contains all type of ADB drivers of android devices currently on market.
You only have to use it once to get the ADB driver installed according to your device model and you can remove it from your pc after that.
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 having trouble running an app I am developing in Android Studio on my Nexus 7. I have successfully gotten this to work before using the same tablet and computer (running Windows 8), but since having my laptop repaired and everything wiped I'm convinced something with my dev environment is messed up.
When I go to run the project, there are no available devices, so it is not recognizing my Nexus 7 anymore.
Things I have tried
making sure my computer recognizes the device and that I have the Nexus 7 driver installed from ASUS
going to the SDK manager and ensuring I have the Google USB driver installed
closing Android Studio and re opening it, restarting my computer, restarting my Nexus 7
killing adb.exe from the task manager
ensuring I have USB debugging enabled and toggling that on and off
switching from MTP to PTP and back again (currently connected as MTP, not sure if that is correct)
Any help would be greatly appreciated. This is very frustrating and I would like to just get back to developing again.
Update- I just noticed that when I go to developer options, "Wait for debugger" (near where you toggle USB Debugging) is grayed out. I think this has something to do with it but I'm not sure how to enable it.
I got it!
This was at least the issue in my case, I hope maybe this will help someone someday, apparently I had not installed the adb driver properly:
Search for Device Manager from the search bar on the start screen
Open Device manager, click on your Android device
Select"Update Driver Software"
BOOM. Now Android Studio recognizes the device.
I know this may not be the solution for everyone, but its worth a shot if you are having trouble testing apps on your device.
Between upgrading my second-gen Nexus 7 to Android 5.0.x and Android Studio leaving beta I lost the ability to debug on my tablet.
To get this working again I used a combination of the above advice.
I grabbed a copy of the USB Driver from Asus, but updating the Device in Device Manager and pointing to the unzipped files wasn't enough.
The next step was to point Device Manager to the Android Studio sdk directory (on a 64-bit Windows 8 install that was C:\Program Files (x86)\Android\sdk - beta versions of Android Studio - or %localappdata%\Android\sdk - switched to in 1.x) and then things worked just fine again.
Another possible reason that you may not be able to connect is:
Don't forget to enable debugging mode in Android setting.
I have had the same problem, although just getting started with my Nexus 5 and windows 7. I installed google usb driver package using SDK manager first, computer recognized phone but studio could not find it. Went in to manually update driver for phone but update driver couldnt find it, downloaded driver separately and pointed it to directory path, driver installed then studio found it and ran fine.
I know there are a few threads regarding the the connectivity between Google Glasses and Eclipse on Windows 7> but I think mine it's a bit different unfortunately.
I followed this threads:
Eclipse & adb Not Recognizing Glass as Running Android Device
Unable to connect to Google Glass on Windows 7 (using ADT)
but unfortunately non helped me 100%.
The PROBLEM:
Even though I followed the steps from the threads, when I go to eclipse and try to run the sample Compass application it shows in the Android Device Chooser(Run configurations) in the target section as unknown.
I must mention that:
enabled debugging on the glasses (several times)
In the Device Manager(Windows 7) it appears as Android Composite ADV Interface, under SAMSUNG Android Phone(?? on the threads they say that should be Android Devices; anyways it appears as ADV Interface)
Reboot system
SDK: GoogleUSB Driver(version 10)
What am I missing here? Thanks a lot for every tip! ;)
Have you tried ./adb devices ? what do you see when you do that?
Did you confirm that your computer is a trusted device on Glass?