Waiting for Target Device to Come Online

Question

I recently updated to Android Studio 2 3  and now when I try to run the application  the emulator does not come online  It times out after 300 seconds   Additionally  The app has been experiencing a FATAL EXCEPTION ERROR  OOM   and I am not sure how to fix that either  or if that is part of the emulator problem    Any help is much appreciated  Again  my knowledge in the program is very limited so if your answer can be kept simple  that would be great

User · Answer

I was having the same problem as you  android studio said I had Emulator 25 3 1 already installed  I deleted the Emulator folder  it s inside the SDK folder   And then reinstalled Emulator 25 3 1 Sdk manager--  SDKtools --  instal the emulator 25 3 1  This time it worked

User · Answer

Like urupvog s answer  make sure that you aren t running any other virtual machines like VirtualBox   When I restarted my computer  AVD worked until I started Vagrant for backend development  then it wouldn t launch    See Android emulator and virtualbox cannot run at same time for more info

User · Answer

Question is too old but may be helpful to someone in future  After search many things  most of them is not worked for me  SO  as per my try This solution is worked for me  In short uninstall and install  Android SDK Tools  in Android SDK   Few steps for that are below -   go to  SDK Manager  in Android Studio go to  SDK Tools  tab Uninstall  Android SDK Tools   means remove check uncheck  ahead of  Android SDK Tools  and Apply then OK  Close and Restart Android Studio Install  Android SDK Tools   means check ahead of  Android SDK Tools  and Apply then OK    Image of Uninstall and Install Android SDK Tools again

User · Answer

This solution works for me   Tools -  AVD Manager -  click drop down arrow -  select Cold Boot Now

User · Answer

Once again  please wait for a while  sometimes you missed that it actually worked but you are feeling really stressed and could not wait I was   Not sure why I fixed the same issue that happened on my Macbook  however  choose Nexus 5X API R would work somehow  OR below  Wipe Data  Tools- gt Open AVD Manager and click   the emu  quot Wipe Data quot   Cold Boots Now  Tools- gt Open AVD Manager and click   the emu  quot Cold Boots Now quot   Uninstall  amp  Reinstall Android Emulator from SDK  Tools- gt Open SDK Manager- gt Android SDK left-side menu - gt SDK tools middle in the main screen   then click  quot Android Emulator quot  and APPLY  then again click  quot Android Emulator quot  apply to reinstall  so finish

User · Answer

I ve had the same problem  AVD not coming online  in a Linux system  In my case  I have solved it setting this environment variable     export ANDROID EMULATOR USE SYSTEM LIBS   1   This case is documented here  https   developer android com studio command-line variables html studio jdk

User · Answer

Below steps work for me   Close running emulator Go to AVD Manager Choose available emulator In that action tab  last one   click on drop down arrow  amp  select COLD BOOT NOW Finally run your application

User · Answer

I had this issue twice and tried everything in this thread with no results  I finally fixed it closing  BlueStacks  emulator   If BlueStacks  and maybe others android emulators  are running when I run the app  by default Android Studio installs the app there  even when I never selected it as a device in AVD Manager  then Android Studio waits for an incorrect device  to come online      Closing BlueStacks  or any other Android emulator  solved the conflict between devices for me   I hope this info helps someone

User · Answer

None of solutions above worked for me  so I had to wipe content of   C  Users your name  android avd   and re-create emulated device

User · Answer

Probably if you haven t solved it yet     the class name uses accented letters

User · Answer

Go to terminal and type android avd  Select your AVD and select  Edit   Make sure you do not see No CPU ABI system image available for this target - it will show in red font at the bottom  Change the target to the one that is available or download the ABI image  Sometimes  if you create an AVD from inside Android Studio  it does not ensure this requirement

User · Answer

Following worked for me on Android Studio 3 x   Step 1   Open AVD Manager     Step 2  Right click and Wipe data for the virtual device you re testing on

User · Answer

Did not read all the answers  Anyway Accepted one didn t work for me  What did was upgrading the android studio to last stable version and then created a new virtual device  I guess my nexus 5p virtual device got out of sync with the android studio environment

User · Answer

I too had the same problem  then I went to AVD manager and right click on the emulator and stopped it and I RUN the application again and this time it worked  it may be a temporary solution but works for the time being      AVD manager-  right-click on the emulator you are using -  Stop   Now Run your application again   Note  Sometimes closing the emulator directly is not working for the above-mentioned problem but stopping it from the AVD manager as mentioned is working

User · Answer

After trying almost all the solutions listed above  what finally worked for me was to create a new virtual device using a  Google APIs  image instead of a  Google Play  image

User · Answer

Finally  I solve this problem by setting the right export path in bash file   export ANDROID HOME  Users  username  Library Android sdk

User · Answer

Go to the Sdk manager--   SDKtools  --  instal the emulator 25 3 1

User · Answer

Go to Run Debug configuration -  General tab  Select blank device in Prefer Android Virtual Device combo box  Now every time when you run the app  it will run on the device already open  If no Device is running  it will throw error

User · Answer

Three days on this  and I believe there s a race condition between adb and the emulator  On a request to run an app  with no emulator already running  you see the  Initializing ADB   then the emulator choice  it starts and you get  Waiting for target to come online   An adb kill-server  or a kill -9  or an  End Process  of adb with the task manager will cause adb to die  restart  your APK installs and you re good to go  It does seem funky to me that an  adb kill-server  causes adb to die and then restart here  but that s another mystery  maybe

User · Answer

I am working on notebook  Windows 8  I solved this issue change mode from battery saving mode to balanced mode  Before that  an emulator didn t work and I see  Target Device to Come Online   Also didn t work Genymotion

User · Answer

I discovered that having a running instance of Docker on my machine  OSX  prevented the Android Emulator from running  see Android Studio Unable to run AVD   Previously  my emulator would appear to start  then fail before any device window was shown   I also had to use  kill -9   as per  MarkDubya   to get Android Studio to connect to the virtual device

User · Answer

Make sure you have enabled USB debugging on your device  Depending on the version of Android you re using  proceed as follows   On Android 8 0 and higher  go to Settings  gt  System  gt  About phone and    tap Build number seven times  On Android 4 2 through 7 1 2  go to Settings  gt  About phone and tap Build number seven times   Return to the main Settings menu to find Developer options at the bottom  In the Developer options menu  scroll down and enable USB debugging

User · Answer

For Linux users using KVM and facing this problem try setting the Graphics option on the Android Virtual Device to Software instead of Automatic or Hardware   As previously mentioned in this answer   I can confirm that the method works for Arch Linux  Ubuntu 16 04  as well as windows with or without a proprietary graphics card using Android Studio version 2 3 1

User · Answer

After trying all these solutions without success the one that fixed my problem was simply changing the Graphics configuration for the virtual device from Auto to Software  tried hardware first without success

User · Answer

Seems that in my case the problem was in that the  Google APIs ARM EABI v7a System Image  wasn t automatically installed during installation of Android Studio   After installing the image  the emulator began to work   Screenshot of the SDK manager

User · Answer

In case you are on Mac  ensure that you exit Docker for Mac  This worked for me

User · Answer

Seems like Android Studio  using version 3 5 1  gets into a weird state after a while  This worked for me      File -  Invalidate Caches   Restart -  Invalidate and Restart

User · Answer

Go to AVD Manager in your Android Studio Right Click on your emulator and then select wipe data Then run your app again  The emulator will perform a clean boot and then install your apk then your app will finally run   Summary AVD Manager---Right Click Emulator----Wipe Data----Run App Again  If the problem presists then simply go back to your avd manager  uninstall emulator then add a new emulator Once the new emulator is added in your avd manager run the emulator   Then run your app  Its much simpler if you have an emulator already running from the onset before running your application for the first time

User · Answer

The problem is that there is no link between ide and the emulator   In our case - we lowered version of android for the app  that frustrated ide  in emulator linking   If we install Android 25 and bind project to it  and AVD Device on Android 25 as well - it links and apllies changes on the fly  If we downgrade to Android 14 and device on android 14 - it doesn t   Used Android Studio 2 3   To play with versions you can set in Gradle Scripts - build gradle  Module  app    android     compileSdkVersion 25   defaultConfig       minSdkVersion 15     targetSdkVersion 15         As a result app won t run on an Android 25 device with a message      Installation failed with message Failed to finalize session   -26    Package ru asv test new target SDK 15 doesn t support runtime   permissions but the old target SDK 25 does   It is possible that this   issue is resolved by uninstalling an existing version of the apk if it   is present  and then re-installing       WARNING  Uninstalling will remove the application data

User · Answer

I also ran into this problem and probably found the solution that may help  The key is launching the AVD in the emulator first then run your App   Following are the steps    In the Your Virtual Devices screen  select the device you just created and click Launch this AVD in the emulator Once the emulator is booted up  click the app module in the Project window and then select Run  rarr  Run In the Select Deployment Target window  select the emulator and click OK

User · Answer

Fix for this issue is simple     Go to SDK tools   SDK Tools Check Android Emulator and click Apply   and sometimes you might see there s an update available next to it  you just need to let it finish the update

User · Answer

I had a similar problem when updated my android studio  Somehow it changed my SDK path  I just changed it to my updated SDK path and it worked   Android Studio -  File -  Settings -  Appearance  amp  Behaviour -  System Settings -  Android SDK  Here you will find Android SDK location just click on edit link in front of that and browse and select the Android SDK from the file browser  Select and click on Apply   Select AVD manager and start Emulator  This solution worked for me

User · Answer

Check you don t have the deviced unauthorized  unauthorized devices reply the same error in the Android Studio  check the emulator once is on with the adb command     adb devices  List of devices attached  emulator-5554   unauthorized  If you have of this way the emulator the Android Studio is waiting for be authorized and maybe this can solve the problem   Authorized Devices  This is a error I have solved in Windows 10 with Android Studio 2 3 3

User · Answer

Tools - Android - Sdk manager - tab Sdk tools - install emulator 25 3 1

User · Answer

Another case is Android Emulator should be reinstalled  This can happen  when you install a higher version of Android Studio  then update SDK for it  and go back to previous one      Tools - Android - SDK Manager - SDK Tools - Android Emulator -   uncheck  apply  check  apply  Disable Docker app if you have it  Mac users   Restart emulator       Tools - Android - AVD Manager    or kill adb process in task manager

[android] Waiting for Target Device to Come Online

Examples related to android

Examples related to timeout

Examples related to emulation