After upgrading to Android Studio 2.2, adb will disconnect from my devices after a few minutes (~ 15 mins). I have to either re plug the device or disable ADB and renable every time. It happens with all devices. This is on MacOS Sierra. Is there a timeout setting they have added?
I ran into this error as well, and it turned out that the problem for
me was that a Stetho tab was open in Chrome (i.e. a tab at URL
chrome://inspect/#devices ), which I guess was causing the device to
be in use. Closing that tab, then running adb kill-server, made adb
devices work again.
original answer https://stackoverflow.com/a/36662403/3290623
The issue is with ADB and it is reported in the bug tracker: Issue 219085: adb does not work reliably on MacOS Sierra.
Answer from the thread:
The fix has been released in the Beta Preview Channel, we apologize
for the inconvenience.or more information on how to use the Beta Preview Channel, please consult http://tools.android.com/download/studio
Edit-1:
Upgrading 2.2 to 2.2.1 or uninstalling the Android Studio-2.2 and installing the 2.2.1 won't work. Try to do clean uninstall by following the thread How to completely uninstall Android Studio? and check.
Try to install the drivers again and restart the Mac, it works for me on AS 2.2
if you do not want to upgrade your Android studio to preview version , just open the sdk manager and upgrade the sdk build-tools, then restart android studio . it works for me !
Related
i'm using android studio in windows server 2016 and have next problem: for work task i need to start android device emulation. On windows 10 emulator works fine, but same steps on windows server cause problem -"the emulator process for AVD_Pixel3A was killed". What should i do?
p.s: hyper-V components not installed, virtualization is accessable.
You will need to to have the H-visuals turned on.. Also check to see that you have HAX installed. Also be sure to turn on developer mode within the computer... I would also run the program on a physical android device to see if you get the same issue.
Also if none of these work you might have to check to see if the server runs the minimum requirements. If it does you may have to reinstall Android Studio. I had this happened to me the other day. I uninstalled and reinstalled Android Studio and it fixed the issue.
I am trying to connect with android emulator using ADB. I can connect with device but every time after a while ( about 10 seconds) connection breaks.
I used to work with adb some time ago and everything was correct.
I tried to restart adb, reinstall adb, I checked settings of emulator and still there is problem.
Check your Android Studio version is the latest, I had this problem on Mac when Nougat was just released. You can try the dev channel if the stable channel doesn't work
Switching Android Studio build channle: http://tools.android.com/preview-channel
I am facing this problem when i am starting my emulator from android studio avd manager. it shows the list of my virtual devices. now when i start the emulator. it shows progress to opens and disappeared in a second without throwing/showing any error.
i am using latest android studio version.
system config : Intel core 2 duo
ram : 6 GB
is this problem cause of system config? Please write your answer and feel free to ask.
I had similar issues (the simulator progress would open then disappear) on my Mac El Capital. Downloading the latest HAXM and RE-INSTALLING it fixed.
Download link: https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
I have updated the video drivers and solved :
1. emulator problem
2. genymotion "player.exe stopped working" problem.
You should use Genymotion replace for default Android Emulator.
There are some various ways to solve this kind of problems:
-> after restarting android studio, if u are facing same problem then try below ones.
kill the adb server through adb shell and then start adb and then launch your emulator.
2.First uncheck Enable ADB Integration and launch emulator and then check Enable ADB Integration.
3.launch your adb and emulator by Debug app from run .
4.maintain the targetSdkVersion corresponding to your emulator
5.uninstall existing emulators and create new one.
delete your adb application and and download new one.
I had this problem because I had many (20) devices saved in my AVD with lots of memory allocated to each (1GB) and my laptop was lower than normal on memory itself.
I cleared out the devices in AVD and started over and it began to work normally again.
I am using a MACbook. For one specific emulator its always showing offline. The emulator has a nexus 5 skin and is a api 24 build. When i try another emulator its fine and works. i tried re-creating the emulator. when i run adb devices it says the "unauthorized".
I tried the following:
I went into the developer settings of the emulator and allowed usb debugging if to see if that would help but it did not. this happened after i updated android studio to 2.3. i also tried to wipe user data from emulator. What is going on here ?
UPDATE: THIS IS OCCURRing for my other emualtors above api 22 also . i had to switch to genymotion for now which seems to work fine and shows as online. it has something to do with updating android studio. after i re-installed studio and did not take the 2.3 update, the problem was resolved.
Don't know the exact issue but it appears there are some bugs/issues with the latest updates.
Personally I am seeing my tests fail when run by ./gradlew commands, but not when run via Android Studio IDE.
I experienced your offline issue as well, I found I could at least rectify this by running:
adb kill-server
adb devices
More info on this in another post:
https://stackoverflow.com/a/21330228/5096103
-- UPDATE --
After investigating this one a little more, I found there to be compatibility issues between Qt version 5.7.0 which the new emulator uses, and Ubuntu 14.04 and it's version of Qt. Whatever system you will be using, you will have some version of Qt installed.
I'm guessing this may be the cause/related to the issues you are experiencing.
I was successfully able to fix my system by downgrading the SDK tools from version 25.3.1 to 25.2.3. I don't get the speed improvements of the new emulator, but at least I can run my tests reliably.
Going to try resolve the issues between Qt versions, and will update this if I can get the new emulator to work correctly again.
I had the same problem. I solved it by turning on USB debugging after unlocking developer options of the emulator by clicking 7x on the build number.
I am not able to start genimotion emulator after upgrading my windows to 8.1. It shows black screen saying dialog "Starting an emulator".
Can anyone know some work around for this?
I've managed to get mine to work by:
Uninstall Genymotion
Uninstall Virtualbox
Install latest Virtualbox
Install Genymotion (the version without Virtualbox)
Caveats: Runs slower than mollases :( I'll post back here if I find a fix for that.
I have uninstalled every thing and install new version 2.0.1 and working fine in windows 8.1 64-bit.
Had the same issue. For me it was enough to update VirtualBox to the latest available release which is version 4.18 at the time of this writing. No need to uninstall anything or to touch Genymotion itself.