I'm on a mac and I updated Android Studio to the latest available version (3.6.1) and now it can't seem to connect to any emulator. I started a new Hello World project and tried building and running it. It opens the emulator but the app never runs. Logcat displays "no connected devices".
I re-installed SDK platform tools and made sure adb was running. Killed and restarted the adb service several times. Tried a different AVD. Tried uninstalling and reinstalling Android Studio. I even tried rolling back to Android Studio 3.5. Logcat continues to show "no connected devices" and emulator opens but does nothing.
Not getting any helpful error messages so I don't know what else to do?
The last update has relocated adb and other tools from ~/Library/Android/sdk/platform-tools/ to ~/Library/Android/sdk/platform-tools/platform-tools/.
Move (or copy) files from .../platform-tools/platform-tools/ to .../platform-tools.
Related
I am using windows in Mac Pro. In Windows Parallel Desktop I am keep on getting error message in Android Emulator like:
Google has stooped working
Settings has stopped working.
Pixel Launcher has stopped working.
Getting error message in freshly installed Xamarin tools in Visual Studio.
Googling suggested to clear the cache or force stop it, but nothing is working
For now I installed Android Studio on Mac and running project on Windows. By Following below link I ran few commands and Windows able to communicate with MAC
https://learn.microsoft.com/en-us/xamarin/android/troubleshooting/questions/connect-android-emulator-mac-windows
Not sure if this is right way. But running virtual device inside virtual machine is giving some problem.
Above thing is working fine. Let me know if there is any other best solution for this.
I installed Microsoft's Android Emulator from here which can now work without disabling Hyper-V on Windows 10. I was following the instructions in this post and everything was working smooth until yesterday. I was successfully able to debug my app in MS android emulator.
Today morning I closed the emulator and started it again. Now, When I start running the app to test it then the MS Android emulator is not showing up in Select Deployment Target window of Android Studio as below. Nexus 5X API 28 emulator visible under Available Virtual Devices is Google's Android emulator which doesn't work with Hyper-V enabled due to reasons mentioned here.
I've already launched the MS Android simulator and it is up and running:
I can see it running in Hyper-V as well as shown below:
Not sure what happened suddenly and it stopped working altogether. Can anyone suggest me the reason behind it or I'm missing something?
If it didn't detected by IDE, try to rerun the emulator and check if it is detecting again or not.
Also, you can try this too:
Tools -> Android -> Enable ADB Integration
If it is already enabled, try to disable and re enable it, seems like this works most of the times.
EDIT: You may want to check:
https://stackoverflow.com/a/38788436/4409113
Changing the value Path then running following commands:
adb kill-server
adb start-server
Might help.
I happened to resolve it by chance. Sharing my experience in case it helps someone in future.
Initially what I was doing is as below:
Start Visual Studio Emulator for Android application which contains the list all the device profiles.
Choose an appropriate device profile and install it.
Run the installed profile and launch the emulator.
Start Android studio, open the project and launch the app.
I simply reversed the above steps to resolve my issue. First close everything including Android Studio, emulators, device profile window etc.:
At first, start Android studio, open the project and hit Run app button to show Select Deployment Target window.
Now, start Visual Studio Emulator for Android application which contains the list of all the device profiles.
Choose an appropriate device profile and install it.
Run the installed profile and launch the emulator. Wait for the Android operating system to get started fully.
The Connected Devices section in Select Deployment Target window would refresh on its own to start showing Microsoft's Android Emulator.
The adb.exe can be seen as an infected file by antivirius software. So need to exclude once reinstated.
For a while I was able to run my app in the android emulator that was installed with Android Studio.
I have since updated SDKs and installed some x86 emulators with SDK manager and now none of the emulators will run properly no matter what I do..
They won't run if I select the run button in android Studio and they won't run if I select the run button I AVD manager.
If I view windows task manager I can see the emulator starting up but they just crash before the emulator window appears.
So what do I do here? Uninstall bloody Android Studio and start over???? Because nothing else that I have googled on this problem works.
All the solutions others have proposed appear to be very vague and a result of random trial and error rather than inside knowledge.
I have tried deleting my emulators and creating new ones.
I have tried wiping data in AVD manager.
I have tried changing the SDK versions in the emulators.
I have tried switching between ARM and X86 system images.
I have tried switching between 'Software GLES' and 'Automatic'
None of them fixes the problem.
The emulators start up in task manager but crash before anything becomes visible while android studio waits in vane for the device to start up.
I am just beginning to use Eclipse for Android applications. After updating my Android SDK i can't run my projects on device anymore. It says "Installing app.apk..." but nothing happens. Installing my app with adb without eclipse works, where could be an Issue? I reinstalled SDK and Eclipse twice.
Try unistalling the application from the phone before re-installing it. Also make sure you have the option to allow non-market apps checked in your phone settings --> applications.
Is it getting stuck at a particular percentage? If that is the case, the solution was to keep the virtual device running before you attempt to run the project.
I had the same problem on my computer. Android sdk on eclipse doesn't work well with windows x64.
So to launch the application you have to kill the adb process. Wait that adb restart and launch one more time.
A serious problem working with android dev with eclipse (with the plugin and sdk installed)
when trying to run an application to the emulator - the progress bar shows:
Launching: Performing pre-launch check..
and stucks there- doesn't continue even after a couple of hours.
I tried killing the adb process, running the emulator before the app and with 'wipe user info'
but nothing helps - just stuck at this stage
I also tried the answers at this thread but didn't help (mostly the same suggestion I already tried)
edit: sometimes(I'm not sure all the times) I'm getting this in the logs:
[2011-11-26 11:28:14 - hierarchyviewer]Unable to get view server
version from device emulator-5554 [2011-11-26 11:28:14 -
hierarchyviewer]Unable to get view server protocol version from device
emulator-5554 [2011-11-26 11:28:16 - hierarchyviewer]Unable to debug
device emulator-5554
any ideas?
solved this myself, seems to be a problem with updgrading the andoid sdk before the adt plugin or vice versa or what ever. anyway to solve had to:
remove all the android plugin
uninstall eclipse (if relevent and delete the whole folder)
also delete the .metadata folder in the eclipse workspace and restart the computer(always a good suggestion/
reinstall/update the android sdk
= reinstall/unzip eclipse
reinstall the ADT plugin
have fun
That's curious... I have the same problem however when I deployed my android's app that's launched in my device and for my surprise I can read the LogCat
Try seen on system device administrator if your device it's recognized by the system.