Related
Android Studio no longer seems to be detecting when an app has installed on a target device and opened. It gets stuck on "Installing APK" and the progress bar is empty. There are no errors, the apk successfully installs and opens, it's just the IDE is still showing "Installing APK" and it does not automatically connect the debugger. I can manually connect the debugger using the "Attach debugger to Android process button", but this is not ideal.
Can anyone offer any suggestions for what's up and how to resolve it?
It turns out the problem wasn't with Android Studio, but with the device I was using for testing. I tried a different device and it behaved normally, progressing beyond "Installing APK" and stopping on breakpoints.
Somehow the "wait for debugger" setting in developer options on the problem device had switched to off. I switched this back on and now this device is behaving normally.
-Note that I had to choose an arbitrary debug app for the setting to become active. Once I'd set it on, I deselected the debug app and the setting remained on, as I left it. This was a HUAWEI P8 running android 6.0 API Level 23.
Recently, I was facing the same issue when I have updated My Device (MI A1) OS from Android Oreo(8.0) to Android Pie(9.0),
Solution: Go to the Settings > Developer options > Now click on > Revoke USB debugging authorisations.
It will disable/remove developer options from your device, Now restart your device once and then you just need to re-enable your developer options and that all you need to do, Enjoy Developing on Pie.
Hope this will help you as well.. :)
I found a solution that works for me. In Developer Options turn off "Monitor apps installed by ADB".
Just reboot your phone (:
It happens after update android version.
On my HTC One I unchecked “Verify apps over USB” in Settings -> Developer Options.
I had this same problem. I solved it by revoking USB Debugging Authorizations and then re-enabling USB Debugging on my chosen device(s).
Edit: Cleaning my project also helped with solving this problem.
for me it was something magic
I solve it by removing the USB from the Laptop and from mobile too(type-c cable) and
turning off the debugging mode and again turn it on
and then I connect it back to my Laptop and selected the same FILE TRANSFER MODE
then run the app and it get installed to my device and work as expected
Hope you will find Useful to
I have this problem recently on my Pixel 2 testing device, latest factory image with Android Studio 3.4, on windows 10.
I have tried all methods mentioned but none of them work. It cost me more than 6 hours to figure it out.
My problem is the USB driver, I am not using the "perfect" USB driver. My driver works in most scenarios and commands but not in every scenario.
You do not need Android Studio to dig into this problem, just using adb.
Please try if you can install apk from adb using following command:
adb install xxxx.apk
If it stuck at "performing streamed install" but never finish, this is the problem.
Please try push a big file(more than 5MB) to your device:
adb push xxxx.apk /storage/emulated/0
In my testing, it stuck at 13%, 16%, etc, but never go on. It seems cannot transfer large files. This is why the installation is pending in my case.
I update the driver to another one, and the problem is fixed. Hope it can solve your problem, too.
I had the exact same problem.
what's more, i can not adb shell and adb push files.
I am running an Ubuntu 18.04 VM and test on xiaomi phone 8,9.
The problem for me was the USB Compatibility setting for the VM was set to 2.0, it needs to be at least 3.0. To change the setting power down the VM and choose the "Edit virtual machine settings" in the VMPlayer startup menu. Then select the "USB Controller" device and change "USB Compatibility" to USB 3.0.
Hope this can help u!
It doesn't hurt to verify your USB port. In my case it was the faulty USB port which I had to switch to the mobo's one instead of the case port.
Restarting Android studio worked for me
I tried rebooting my phone and it worked.
When attach my mobile to my PC, the follow menu is showed. I Clicke on it.
In the next section, I had changed from "USB connection" to "Transfer files"
After that adb install works for me.
In my case, Second Space was created but not switched on. I had to delete the second space and everything worked just fine.
My settings are:
Usb debugging -> ON
Install via Usb -> ON
Verify over USB -> ON
Wait for debugger -> ON
Device: Redmi Note 5 Pro
I had this issue with an emulator on Linux. After trying pretty much every solution and suggestion on this page, what made it work for me was turning off Instant Run.
In my case i did not make sure that my android studio DSK manager was up to date with the android version that my device was operating on. So when running flutter doctor all seemed well, and i had the latest android version and all on android studio, but as mentioned it was not matching the version for my device i had connected.
Once i added the correct android version (in my case android 6.0) with SDK manager using android studio, it did not get stuck at installing apk.
My case was similar but for Android Version 10 required having the Verify bytecode of debuggable apps to off.
Final settings were:
USB debugging -> ON
Wait for debugger -> ON
Verify apps over USB -> ON
Verify bytecode of debuggable apps -> OFF
Device: Pixel XL
For me, the top answer "wait for debugger" was completely greyed out.
What worked for me was to look inside "Apps" and I noticed the app was uninstalled, but only for my current user. Clicking uninstall for all users unblocked the installation via Android Studio again.
Check following in your project
build-gradle plugin version in project level build.gradle file
gradle version in gradle-wrapper.properties file
buildToolsVersion
uninstalling the previous installed app worked for me
Turn off Verify apps over USB and Verify bytecode for debuggable apps (might not be available for all devices) in your Developer settings menu. The install time will decrease drastically.
I'm using Visual Studio Xamarin and the issue was caused by the missing CPU architecture. After checking them, the APK became installable via adb install ...
Just reboot your mobile . If not working try reboot your Android studio and mobile.
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.
Here is the problem. I want to run my Android Studio apps on my device (Samsung Galaxy Ace 2). But nothing works for me. Tell me what I've missed:
1) USB debugging is on
2) ADB driver is installed (in device manager i can see Android Composite ADB Interface)
3) ADB device list is still clear, even if i reset server(adb kill-server, adb start-server, adb devices - list of devices is clear)
4) in google usb driver directory, in android_winusb.inf file I added my device identificators
5) Android device manager still cannot connect to my device, showing this error when I reset it: "adb connection error an existing connection was forcibly closed by the remote host"
So I will be glad to hear any advices. Hope you'll help me
Did you try to configure the "Media Mode" in "Camera (PTP)" instead of "Media device (MTP)"? This is sometimes solving the issue. Its in the USB Computer Connection options of your Android device, you should see an "authorize" dialog then.
Update 04/2017: looks like it has been fixed in Android 7.1.2
I have done numerous ways of handling that issue. Finally it has worked! I am using LG Optimus II, but I believe the following steps are generic to other Android devices as well.
Step 1:
Make sure your device is enabled for development. If yes, go to Step 2, otherwise go to Settings > About phone and tap Build number seven times which is magic number :-).
Now Developer Options is available in the Settings.
Step 2:
Before you plug your device to PC, Go to Settings > Developer Options and select USB Connection method.
Step 3:
Plug the phone to the PC, you are given options for the USB Connection method, and please select Internet connection. Make sure you have connected to the Internet. By the way, I have changed MTP to PTP, it did not work for me. Therefore, I tried Internet connection mode, then it worked.
Step 4:
Run the app in the Android Studio, it will ask you to authorize the device for development, and select YES!.
Step 5:
Run the application via Android Studio and choose the device, not emulator, and BINGO! Welcome to Android development board.
Try swapping the USB port the cable is plugged into.
Sounds crazy but after 20 minutes of debugging this worked for me.
I also tried above solutions but got no luck. So here's what I did:
Download and install PdaNet+ to fix connection issues between my computer and android device
Enable USB debugging on my android device
Unplug the phone and plug it again after it's installed
Run my app and voila! My android device is now recognized by Android Studio
Although my computer could recognise my phone, I had to install the official drivers from the Samsung developer site to get adb/Android Studio to recognise it:
Samsung Android USB Driver for Windows
Click Revoke USB debugging authorization in Developer option and try it again.
Solution for those working with Huawei phones - You will get this error when ADB interface is not installed. Check if you have installed Huawei HiSuite. USB driver gets installed when you install HiSuite (I suppose this is true for most of the new phones that come with a Sync Software). If the ADB interface is installed on your computer you should see 'Android Composite ADB Interface' under Android Phone in your Device Manager as shown in this picture.
If you have Mi Device than you need to enable this two option after enabling Developer Mode.
USB Debugging (Enable = True)
Install via USB (Enable = True)
See this screenshot.
LG Optimus Zone 2 pp415 d\n connect in mtp, but does work in internet connection mode. Lost lots of time messing with it. There's no doc for this, but I'd suggest trying all 4 of the connection options. Only 1 that works for me is Internet Connection->Ethernet, then win 8 auto-detects a driver and installs it. In MTP mode despite all drivers being registered with device manager, adb doesn't pick it up.
I had the same problem. So here is what i did
reinstalled the device driver
changed the USB computer connection from MTP to Mass storage(UMS)
And it worked.
For me, I tried the above. Turns out my USB cable was bad. I changed the cable and then it worked.
I am sorry that i bothered you all. The problem was my device is cloned in different places in device manager. It was gone when I tried to update driver for my phone in "Other devices" list, and before i have been updating it in wrong sections. Thank you all.
In my case it was due to already running and hanged adb.exe on another user under my PC. I had two users on my PC, the second user had the adb.exe process hanged even when I tried to end the process. It worked with me after (End Process Tree) from the Task Manager.
Hope this will help someone with multiple users :)
Ahmad
In addition to the above configurations, I had to set deployment target to "Open Select Deployment Target Dialog", run once (choosing my device from the options listed), and from then on Android Studio was able to see my device even after changing the deployment setting back to "USB Device". My SWAG is that since Android Studio uses its own internal cache to find your device, it has to be initialized first.
I was on Samsung S8 and had same problem too. After I installed Samsung Kies, issues was resolved for me, as I believe it had updated the correct driver required for my Samsung S8.
On Windows 7 , the only thing that worked for me is this. Go to Device Manager -> Under Android Phone -> Right Click and select 'enable'
i had to install android studio in 2 machines and ive solved this problem intalling samnsung kies, i use 3 diferents samnsung devices (plus some other of my family and friends) and i dont have to strugle with the drivers, it works for me and i recomend it. hope it helps
For me, this ended up being because I had the wrong SDK level installed (new version of Android Studio installed the SDK for Android 10, whereas I have a device that runs only Android 8.1). While Android Studio would "recognize" the device and display a string in the "devices" menu instead of just saying that no device was connected, installing the right SDK level for my device ended up changing the string to something recognizable (my device's model name) and allowed me to actually run my app over ADB.
I had a big problem with my Samsung S10 Plus as it was not detecded by Android Studio on my Macbook even if I did all what is required to be detected, that is to say:
Enable developer mode (7 taps on Build version in Android settings)
Enable USB debugging
What I did is to start "Android File Transfer" on my Macbook and the magic happened. A popup appeared on my device asking if I want to authorize an USB access to it. I clicked "Yes, always" and now Android Studio can detect my device on my Mac :)
Change the connection method Build-In CD ROM it works for me
On HTC mini one 2, besides enabling the Developer Options, the following worked for me:
Go to More in Wireless & Networks
Mobile Network Sharing
In USB network setting
Select Internet pass-through
I am using the ADT eclipse for android development. I connected my phone then ran eclipse. Then when I run my android project, I get the window asking how you want to run it. I can see my phone listed there, but its not recognizing its target version.
As a result I am unable to run it on my phone. This is happening sometimes before, and now more often than usual.
Does anyone know how I can fix this?
Yes it's a weird one but you know how phones have "media" and "camera" mode and such, change that to "media" if I recall correctly, or "camera", it's something along those line! It was my old phone sorry, but this solved it!
Alec
Its the camera made that works. I tried it for google nexus 4 and turning it to camera mode worked for me.
Here is the path where you can find the setting for nexus mobiles:
Settings > Device > Storage > Menu > USB computer connection
For others still experiencing trouble having checked the connection mode, try these proposed solutions in the stated order till you get it working:
Check whether USB debugging is enabled. Try disabling it and enabling it again. Can't find this option? Settings > Developer options > USB debugging. Can't find Developer options? Settings > About (phone) > Tap 7 times on Build Number
Try a different cable (some users have experienced being able to charge, but not transfer data or charge and transfer data, but not get recognized by ADT)
Reboot phone
Reboot computer
Check your USB driver, especially if you're running Windows or Linux. On Windows, install Google USB driver from sdk-manager, then: Device Manager > Find and right-click phone (usually under 'Portable devices') > Update driver software > Browse my computer for driver software > adt-folder-location/sdk/extras/google/usb-driver. For further info, read up on http://developer.android.com/tools/device.html#setting-up. (The "Setting up a Device for Development"-part)
Download and use a separate ADT
Try using Android studio
Try finding and using an older ADT
Try using a different computer
Wait for next ADT update and quietly weep...
I have tried connecting the USB debugger on Samsung Galaxy S2 and Samsung Galaxy Nexus. It still manages to fail on both devices. At the moment I am using Windows XP and I am running out of ideas.
Here is what I tried:
Installed SAMSUNG_USB_DRIVER_FOR_MOBILE_PHONES_1.4.8.0.exe
Searched and tried to install the drivers on Google drives.
Has anyone have this similar problem and could share a solution?
EDIT* Both devices Samsung Galaxy S2 and Samsung Galaxy Nexus are able to connect to the PC but not to the debugger. Drivers installed with different variances even done installing Samsung Kias.
I am adding a bounty tomorrow for 50 reps. I really need to test what I am doing on an actual phone.
You need to download Samsung Kies I know that the software description doesn't mention that it is the correct drivers for developers, but it in fact is.
An old issue used to be:
Use the USB2.0 ports on the back of the PC not the 1.0 front facing port.
I feel you have not installed sdk properly. Reinstall the http://dl.google.com/android/installer_r18-windows.exe, the open the adb and update all the things for the particular sdk you want.
Then verify that you have given the exact location of sdk in eclipse>window>preferences>android
Then restart eclipse.
Even you cant open it then set environment variables. For that add following ;E:\android-sdk-window\platform-tools; in PATH. Then restart windows.
After that try adb devices, adb kill-server command in Command prompt.
You will be able to see your device.
Is there any "ADB interface" devices in your PC's Devices Manager?
If you are using DDMS,Maybe there is a console(cmd.exe) window behind DDMS,you can get some log there.
Did you enable the debug mode on your device? This is not listed in the steps you followed.
Go to Settings -> Applications -> Development -> and set USB debugging.
You can use PdaNet software to connect your device for debugging. I was have the same issue and resolve with using this software. Use the following link to download this software:
http://junefabrics.com/android/download.php
I also have samsung Galaxy SII and i face the Same Problem before some days. But now i am able to get debug the app in My SII.
Please follow the steps and make sure that you follow it completely then only you cna able to get debug in your phone.
First select the Option to Install App from Unknown Sources.
You will find that option in Setting -> Applicatios -> Unknown sources. Select it as yes.
then Select the Option like USB Debugging.
You will find that option in Setting -> Development -> USB debugging. Select it as yes.
Now, Install latest Samsung Kias In your PC. Reboot Your PC, Eclipse and may be Phone also
Now, Try with connecting the Device.
Hope you will get debugging your app in to your phone.
If not then let me know which trouble you get.
Enjoy. :)
My phone has this:
Settings -> SD card & phone storage -> Mass storage only (USB connection mode is mass storage only)
Make sure that this option is NOT checked. If it is u can enable USB debugging and unknown sources and it still wont work.
If you just need to connect to the device for install and debugging you can manually select the driver to use when you plug it in.
Don't let windows search for it, choose I will pick the driver from a list, then select android composite ADB interface. It may warn you that this driver doesn't match, but it works!
I also had many problems to get samsumg galaxy S2 work on my pc. If I remember correctly finally I ended up installing Samsung Kias and installed some drivers through there. Then restarted the computer and never launched kias from then on. My phone is still not visible form command line adb devices, but now I can develop in Eclipse and deploy on the device without any problems.
From time to time I lose connection to the device (E.g. if another device was plugged in). Then I need to restart Eclipse and my device becomes visible again.
Some friends of mine also shared that some other mobile device usb drivers were conflicting with the samsung drivers (it was ZTE if I am not wrong). They uninstalled the ZTE drivers and then got the Samsuung running ok too. Try consider uninstalling all other usb drivers before you try the Galaxy S2.
Have you installed exactly the right SDK version for the phone you're using?
Given that you can access the phone on the PC via KIES, I assume that you have all the correct USB drivers installed.
Ensure that debugging is enabled on your phone. This can be done from the Settings preferences.
Install the Android SDK. Add %ANDROID SDK_INSTALL_PATH%/platform-tools to your path.
If everything is working up to this point, plug in your phone and execute the following from the command line.
adb devices
and you should see your device listed.
Install the Android Developer Tools plugin in Eclipse.
Create/Import your project.
Right click your project and from the context menu, select Debug As --> Android Application
I have had exactly the same problem as you, I even gave up on developing for 2 months because of this. I have just started again and really needed to get this working.
I tried all of the above and pretty much every combination of the above and still failed.
I have just got it working by not doing anything different apart from when I uninstall the old USB driver (add remove progs), the next time I installed AGAIN, I used the SAMSUNG USB Driver for Mobile Phones V1.3.450.0 (an older version than ones suggested on other help forums, I just got it by accident somewhere and thought I'd try it). The next time I plugged the phone in, it did all the usual finding CDC etc. that it always did when it failed...but then.... it asked for the ADB Driver, WOW! I got excited. I just selected Install Automatically and away it went.
I still already had the PDANet thing running and that popped up saying a connection is available. I've not used it though because it wouldn't install on my phone anyway.
FYI, I have these settings on the phone:
USB debugging ON (obviously)
Allow Mock Locations OFF
Unknown Sources ON
I hope this helps.
Dan.
This may not help at all since you have probably tried it already but I had huge issues on two different windows 7 machines getting my s2 to connect for debugging.
I ended up getting one working by plugging in the s2 USB connection, un-installing the drivers for it in the device manager, unplugging the USB connection, un-installing Kies, downloading the most up to date version of Kies, installing that and plugging it back in.
The other one was even more painful, it was a while ago now but I did the same as the above but removed eclipse and the Android SDK as well, installed the latest version of Kies first, the eclipse, then the sdk and made sure all of that was done before I plugged the phone in.
I faced same issue which you faced..
I solved this by this way.
1) Right click on my computer and select Manage
2) Then select Device manager..
3) connect your phone (galaxy s2 in my case)
4) I found one device with named "unknown" in sub option I foung my phone name i9100
5) Then right click on that and select update driver software
6) you will see then this..
Tadaa....Done :)
Hope this will help you also..