I have been running Android Studio on my Macbook for over a year perfectly fine. Recently I decided to upgrade to MacOS Catalina. The upgrade went successfully, but when I ran Android Studio again, I've been receiving this error constantly when I try to start a virtual device. Tried cold boot, wiping virtual device data, cloning virtual device, creating a fresh new device,
Even tried this as a solution (found it on the internet).
sudo launchctl remove com.cylance.agent_service
But nothing seems to works. Here's a screenshot of the error
So I found the answer to the weird problem. So apparently Android Studio Emulator works in a weird way. I have a dual monitor setup, so I had opened the emulator on monitor 1 and closed it on monitor 2 and then was trying to reopen on monitor 2. What the emulator does is it leaves some files behind from monitor 1 behind that interfere when it is restarted on monitor 2. So I re-opened it on monitor 1 and it worked. Saw this on some youtube video, didn't believe it'd work, but it did and I forgot I had asked it here as no one replied and I got busy. Now that I know I would like to leave it here, in case someone else has the same issue.
Related
I am using Android Studio emulator, but it keeps crashing upon opening. I get failed to sync vcpu reg error multiple times in the output and nothing else.
I have tried the solutions to similar questions posted on here to no avail. I tried: reinstalling HAXM, I don't have the docker application, I used BIOS to check that VT-x and VT-d are both enabled. I don't get any logcat from Android Studio.
Attached is picture of the output from running the emulator from cmd
This question is different from apparent duplicates because my emulator worked the day before. I don't have any virtual machines running. The only difference is that my laptop auto updated last night.
I solved this problem on my HP laptop by uninstalling HP SureClick.
I am using Windows 10 and tried almost everything the internet had to offer to fix this issue (the Virtual Machine in Android Studio loaded but then closed almost immediately)
The fix I found was to enable "Virtual Machine Platform" on Windows features.
Instructions:
Right click on the Windows button and select 'Apps and Features'
Select Programs and Features on the right under related settings
Select the checkbox below
CHECKBOX TO CLICK
You then get prompted to restart - after that, everything worked for me ! ...hope it does for you !
I had this same problem and all the solutions here did not appear to fix it. Strangely enough I managed to fix it by turning windows virtual machine platform ON, even though it very specifically says here that this is something that should be turned OFF.
I tried what paulsm4 said and the emulator works now. I was looking around in my anti virus settings and found something that uses virtualization. I just turned it on rebooted and then back off and rebooted. The emulator runs!
When I start an emulator from Android studio, it closes immediately and it shows these messages in the Android studio event log
Previously, I had Genymotion installed, but the problem still occurs after I have successfully removed it (along with Virtual Box) from my computer.
I have VMware on my computer, but this was never a problem for successfully running an Android Emulator.
I have tried all of the proposed solutions on the internet (including reinstall of Android studio, update HAXM...), but nothing works.
Maybe it is due to the fact that your pc doesn't have much memory or disk space to run android emulator.Please check this if it helps.
Check what 'adb devices' shows you.
Seems like you still have some parallel instance running
May be it depends on your computer features.After you open a place where android studio is set up,everything might be okey
I have a macbook pro (Retina, 15 inch, late 2013) that is running High Sierra GM (17A365) and a fresh install and blank project in Android Studio always results in a crash (emulator64-crash-service quit unexpectedly.) when trying to run any android emulator. I have tried every suggestion I can find on the internet, NONE of them work. Here is what I have tried so far:
Since I have an external monitor connected to my mac, I tried both creating emulator-user.ini file with window.x values (Android VM crashes on Launch Mac) AND just tried disconnecting second monitor and running just on the macbook. Still crashes
Tried completely (including all prefs and hidden folders) uninstalling Android Studio, rebooting and reinstalling and setting up brand new default environment. Still crashes
Verified that HAXM is installed correctly and running loaded (kextstat | grep intel returns expected info), but have also tried without HAXM. Still crashes
Tried launching emulator from Terminal. Still crashes
Tried creating new avd from avd manager. All of them crash.
Tried changing settings in avd configs to use (or not use) Hardware/Software graphics, as well as fiddling with more or less memory than defaults. Still crashes.
Does anyone have anything left to try? I am pulling my hair out here. I would like to try my cordova app in Android, but it seems impossible from my mac.
I still don't know what caused it, but as a workaround creating a fresh account on my Mac and launching studio and emulator inside of that allows it to run. So it is something in my original account settings that is causing this crash, and I still don't have a clue what (although there are no active startup items, launch daemons, caches, saved app state, etc that I can find, I have cleared them all).
this is more of a benign bug in android studio. Whenever I wake my computer from sleep or hibernate the connection between the emulator and android studio is not proper and I have to restart the emulator and try again, so as a result of that (I think) all the dead emulators are always shown in the listing when trying to run the app.
And FYI I don't usually restart/shutdown my computer (once in 10 days or so). I was just wondering if there was a way to fix this bug without having to restart the computer.
Screenshot of problem
Thanks in advance!
I am having the same issue using Windows 10 hibernate.
Try terminating the adb.exe process in the task manager. Sometimes you will find two or more adb.exe processes, kill them all. Then close all running emulators (if any) and disconnect all physical devices.
You don't have to restart android studio or eclipse.
After dong this, all unknown/null emulators should be gone (at least in my case).
Did you open multiple android studio and use the terminal in android studio?
you can close all android studio, and restart them. the unknown emulator will be gone
[2012-02-14 11:57:59 - HarshaBoston] Android Launch!
[2012-02-14 11:57:59 - HarshaBoston] adb is running normally.
[2012-02-14 11:57:59 - HarshaBoston] Performing com.boston.harsha.startPoint activity launch
[2012-02-14 11:57:59 - HarshaBoston] Automatic Target Mode: launching new emulator with compatible AVD 'Droid8'
[2012-02-14 11:57:59 - HarshaBoston] Launching a new emulator with Virtual Device 'Droid8'
[2012-02-14 11:58:05 - Emulator] emulator: WARNING: Unable to create sensors port: Unknown error
Ok so this is what the console is showing. My emulator was working fine until a couple of days ago, then my projects were not updating the changes made to the main.xml file even though the changes were saved.
Now, I wanted to see if a new project would work, but no dice. The emulator runs fine, but my app is not loaded, I have no idea what to do to rectify this.
I'm using API Level 8, with ADT plugin Android SDK on eclipse on Windows XP.
Android beginner here. I was making a Hello World program, which ran fine a couple of days ago, but now nothing runs, and existing projects don't show the changes made to them. Please help!
Now when I run the emulator, the emulator runs fine but my app isn't even loaded!
I've already tried reinstalling the ADT, reinstalled the Android SDK,etc. nothing happpened
Also, the emulator doesn't seem to be showing up on the DDMS.
FIXED IT!! SOLUTION FOR ANYONE FACING THIS PROBLEM
Apparently a lot of people in here seem to have this problem and only one of the threads had a good solution.
Firstly if this is happening to you, check the DDMS to see if the emulator is shown. This is the a red flag. Apparently the adb server does not refresh or restart every time you restart eclipse.
Run the emulator. Chances are your app may not run on the emulator. Now, while the emulator is still running go the DDMS tab and next to the Screen Capture icon there is a dropdown menu with 'Reset ADB', click on it. Now your emulated device should be shown in the DDMS devices.
Run your app now. hopefully this solved your problem. Mine did!
FIXED IT!! SOLUTION FOR ANYONE FACING THIS PROBLEM Apparently a lot of people in here seem to have this problem and only one of the threads had a good solution.
Firstly if this is happening to you, check the DDMS to see if the emulator is shown. This is the a red flag. Apparently the adb server does not refresh or restart every time you restart eclipse.
Run the emulator. Chances are your app may not run on the emulator. Now, while the emulator is still running go the DDMS tab and next to the Screen Capture icon there is a dropdown menu with 'Reset ADB', click on it. Now your emulated device should be shown in the DDMS devices.
Run your app now. hopefully this solved your problem. Mine did!
I had the same problem with developing my android app on an emulator. I would rebuild and install my application and it would keep installing an older version of my app (reinstalling app, and the answer above didn't help). Turns out running ant clean and rebuilding the project fixed it!